docs.gitlab.com release 19.6 (November, 2026)
# Tasks for all releases
Documentation [for handling the docs release](https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/blob/main/doc/releases.md)
is available.
> [!note] Terminology
> The following terms are used throughout this document:
>
> - **Stable branch**: This is the branch that matches the GitLab version being released. For example,
> for GitLab 17.2, the stable branch is `17.2`.
The release dates for upcoming releases are listed in the handbook: <https://handbook.gitlab.com/handbook/engineering/releases/monthly-releases/#monthly-release-schedule>
## Release week
During the week of the release (usually on Monday):
1. [x] Share the following message in the `#release-post` channel on Slack:
```plaintext
Hi team, I'm the docs release post manager for <version> this week. Please ping me when
the release is available, so I can start the docs process on Thursday.
```
1. [x] Ensure required tools are installed and up-to-date. In the root path of the `docs-gitlab-com` repository:
- Update your local clone:
```shell
make update
```
- Install and update all project dependencies:
```shell
make setup
```
- Ensure you're [authenticated](https://gitlab.com/gitlab-org/cli/-/blob/main/README.md#oauth-gitlabcom)
with `glab`:
```shell
$ glab auth status
gitlab.com
✓ Logged in to gitlab.com as <username> (<$HOME>/.config/glab-cli/config.yml)
✓ Git operations for gitlab.com configured to use ssh protocol.
✓ API calls for gitlab.com are made over https protocol.
✓ REST API Endpoint: https://gitlab.com/api/v4/
✓ GraphQL Endpoint: https://gitlab.com/api/graphql/
✓ Token: **************************
```
1. [x] In this issue, create separate comment threads for the retrospective and add items as they appear:
```markdown
## :construction: Notes from release steps
## :+1: What went well this release?
## :-1: What didn't go well this release?
## :chart_with_upwards_trend: What can we improve going forward?
```
1. [x] In the root path of the `docs-gitlab-com` repository, use the
[`create-archive-branch`](../../doc/releases.md#make-create-archive-branch) Make target
to add older docs versions to the [`gitlab-docs-archives`](https://gitlab.com/gitlab-org/gitlab-docs-archives) repository.
Save a copy of the command output.
```shell
make create-archive-branch
```
- [x] In the `Notes from release steps` comment thread:
- Add the output of the `make create-archive-branch` command, even if it appears successful.
- Add a link to the related pipeline.
> [!note]
> If you get a `Branch already exists` error, skip to the next step.
Do NOT create a merge request for this. The changes are deployed after a few minutes.
The release number shown in the script is an older release.
For example, if the release version is GitLab 18.0, the command deploys to:
`archives.docs.gitlab.com/17.9/`. You can visit `https://archives.docs.gitlab.com/<version>` to
verify.
1. [x] Create an MR that updates the release notes content in the `gitlab` repository.
You can do this before release day, but do not merge it until release day.
1. Update the content for the stable release. Open the minor release index file
(for example, `doc/releases/19/gitlab-19-0-released/index.md`) and:
- In the metadata, after `group`, add the release date (for example, `date: 2026-05-21`).
This makes the pipeline fail until the release date, which is expected.
- Change the `description` from `Summary of features included in <version>` to
`GitLab <version> released with <top feature title>`.
- Change the `title` from `GitLab <version> (Upcoming release)` to `GitLab <version>`.
- Change the introductory text from future tense
("The following features are being delivered for GitLab <version>. These features are now
available on GitLab.com.") to past tense
("On <release date>, GitLab <version> was released with the following features.").
1. Create the content for the upcoming release. For example, when publishing 19.1, create the
content for 19.2:
- In the major version directory (for example, `doc/releases/19/`), create a new directory for
the upcoming release (for example, `gitlab-19-2-released/`).
- In the new directory, create an `index.md` file from the [minor release index template](https://docs.gitlab.com/development/documentation/release_notes/#minor-release-index)
and update the version number.
- In the major version `_index.md`, update the `cards` shortcode to reference the upcoming
release file.
- In `doc/releases/upcoming.md`, update the `redirect_to` metadata to point to the upcoming
release file.
1. Add a link to the MR in the `Notes from release steps` comment thread.
1. By the day before the release, ask a reviewer to approve the MR, but not merge it.
Approvals in `gitlab` stay after you push, so you can still add late changes.
1. [x] Create an MR that adds the stable release to the navigation in the `docs-gitlab-com` repository.
You can do this before release day, but do not merge it until release day.
1. In `data/en-us/navigation.yaml`, add the current release to the submenu. For example:
```yaml
- title: GitLab 19
url: 'releases/19/'
submenu:
- title: GitLab 19.0
url: 'releases/19/gitlab-19-0-released/'
- title: GitLab 19.1
url: 'releases/19/gitlab-19-1-released/'
```
1. Add a link to the MR in the `Notes from release steps` comment thread.
1. By the day before the release, ask a reviewer to approve the MR, but not merge it.
Approvals in `docs-gitlab-com` are removed when you push, so don't change the MR after it's approved.
1. [x] Ask in `#tw-team` for a Technical Writer maintainer to be available on release day. They approve
the backport MR, and review and merge the release MR. The release usually happens around 12:00 PM ET (~16:00 UTC).
## Release day
These steps take approximately two hours to complete, depending on fixes and pipeline durations.
On Thursday (or Friday depending on time zone):
1. [x] Start a new pipeline on the content MR, so it passes before the release manager confirms.
The `date` metadata fails the pipeline until the release date, and `gitlab` pipelines take a while.
1. [x] Check the `#release-post` channel for confirmation from the release manager that the release
is complete and the new version is available for customers. You can now begin the next steps.
Post all release day updates as replies to the release manager's message.
1. [x] Check the `#release-post` and `#docs` channels for
any late submissions under review. Wait for all late release notes updates to be merged
before moving to the next step. Late updates to other docs pages go in their own backport,
which the writer for that page handles after release day.
1. [x] Share the following message in the `#docs` channel on Slack:
```plaintext
:mega: Starting the docs <version> release.
You may notice some unexpected behavior or loading errors on the docs site during the deployment
but please stand by.
Follow the release in this thread: <link to the release manager's message in #release-post>
```
1. [x] Merge the prepared release notes merge requests. Merge them before you create the stable branch,
so the stable branch includes the navigation entry.
> [!warning]
> Do not merge these changes until the release manager confirms that the packages are publicly
> available, usually around 16:00 UTC. Release managers add a note in the `#release-post` channel
> when it's time to publish.
- [x] Merge the **content** merge request (`gitlab`) to publish the current release post and
create the upcoming release's content.
- [x] Merge the **navigation** merge request (`docs-gitlab-com`) to update the left navigation.
- [x] After the release notes appear on `docs.gitlab.com`, tag Sandra Gittlen and Chandler Gibbons
in the release manager's thread in `#release-post` with a link to the current release.
1. [x] Update your clone of the `docs-gitlab-com` repository. In the root path of the repository:
```shell
make update
```
1. [x] In the root path of the `docs-gitlab-com` repository, use the
[`create-stable-branch`](../../doc/releases.md#make-create-stable-branch) Make target
to create the stable branch by replacing `X.Y` with the new version. Save a copy of the command output.
```shell
make create-stable-branch VERSION=X.Y
```
Creating the stable branch on the release day is ideal, though this might not always be possible depending on your time zone.
If you create it before the navigation MR merges, the stable branch doesn't include the navigation entry.
After the navigation MR merges, cherry-pick it into the stable branch.
[Issue 248](https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/issues/248) exists to automate stable branch creation.
- [x] In the `Notes from release steps` comment thread:
- Add the output of the `make create-stable-branch` command, even if it appears successful.
- Add a link to the related pipeline.
- [x] Confirm that the new branch has a commit that adds a
[`pinned_ref`](../../doc/releases.md#pinned-content-refs) for every project in
`data/products.yaml` except `patches`.
- If the command warned that an upstream stable branch doesn't exist yet, note which ones in
the `Notes from release steps` comment thread. The branch pipeline fails until those
branches are created.
- To track the progress of the stable branch pipeline, go to the
[pipelines list](https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/pipelines),
find the pipeline and select it so you can see the individual jobs.
- The `test:check_global_nav_entries` job will fail if a page was added to `navigation.yaml`
but did not make the cut-off in `gitlab` for this release. The job log lists the URL of each
missing page, for example `No sitemap entry found for global navigation entry URL: user/example/`.
The page is `doc/user/example.md` or `doc/user/example/_index.md` in `gitlab`.
For each page, either add it to the backport MR in the next step, or, if it's not part of
the release, remove its navigation entry from the stable branch:
1. In your local environment, pull all the latest changes, then check out the release branch.
1. Remove the navigation entry.
1. Push your change directly back to the release branch. You do not need to create an MR.
1. In the `Notes from release steps` comment thread, note any entries you removed.
1. [x] Backport the final release notes, and any missing pages, to the most recent stable branch.
The final `gitlab` cutoff is the Friday before the release, so the stable branch does not yet have
the final notes. Backporting makes them visible when users select the newly released version.
1. In the `gitlab` repository, check out the stable branch. For example, when releasing 19.1, check out `19-1-stable-ee`.
1. Create a new branch off the stable branch. For example, when releasing 19.1, `19-1-stable-ee-backport-docs-release-notes`.
1. Copy the release notes directory (for example, `doc/releases/19/gitlab-19-1-released/`)
from the `master` branch, and paste over the local version on the new branch.
1. Copy any pages from the `test:check_global_nav_entries` job log from the `master` branch.
1. Open a merge request, select the **Stable branch** template, and set the target branch to the
stable branch (for example, `19-1-stable-ee`). Keep the template's hidden comment, and add the
`~"type::maintenance"` label. Danger fails the pipeline without both.
1. Ask the Technical Writer you lined up to approve, then merge. If the branch is locked, ask in
the `#release-post` channel or wait until the branch is available to merge.
1. After the merge, [create a new pipeline](https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/pipelines/new).
For **Run for branch name or tag**, select the version to deploy (for example, `19.1`), then
select **New pipeline**. Don't retry the failed jobs. The build fetches content when the
pipeline is created.
1. When the pipeline completes, the new version is available at `docs.gitlab.com/X.Y`.
Verify that the new release is functional, then proceed to the next step.
1. [x] In the root path of the `docs-gitlab-com` repository, use the
[`create-release-merge-request`](../../doc/releases.md#make-create-release-merge-request) Make target
to create the release merge request by replacing `X.Y` with the new version. Save a copy of the command output.
This merge request updates the version dropdown list for all online versions:
```shell
make create-release-merge-request VERSION=X.Y
```
- [x] In the `Notes from release steps` comment thread:
- Add the output of the `make create-release-merge-request` command, even if it appears successful.
- Add a link to the related MR.
1. [x] Verify that the merge request:
- Has the `~release` label.
- Includes only the following in the **Changes** tab:
- `.gitlab-ci.yml`
- `content/versions.json`
1. [x] After the merge request's pipeline passes, ask the Technical Writer you lined up to review and merge the release merge request for you.
1. [x] After the deployment completes, open `docs.gitlab.com` in a browser. Confirm
both the latest version and the correct pre-release version are listed in the version dropdown list.
Note that it may take up to 5 minutes for the deployed changes to appear on the website due to caching.
The next release version appears as the default version in `docs.gitlab.com`.
1. [x] Check the version dropdown list to ensure all versions of the docs are visible
and their version dropdown lists have the expected versions.
- Versions hosted on `docs.gitlab.com` should show the same version options as the pre-release site.
- Versions hosted on `archives.docs.gitlab.com` should only show their own version and a link back to the archives page.
- This applies to GitLab 15.6 and later. Earlier versions might have broken links in the version dropdown list.
This will eventually be resolved as the earlier versions are phased out.
1. [x] Reply to the release manager's message in `#release-post` with the following message:
```plaintext
:rocket: The docs <version> release is complete. If you have any feedback about this release, add it to the retro thread in <this issue>.
```
## Post-deployment checklist
After the docs release is complete:
1. [x] **Major releases only.** Update
[`OutdatedVersions.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/.vale/gitlab_base/OutdatedVersions.yml)
with the latest outdated version.
1. [x] Improve [this checklist](https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/blob/main/.gitlab/issue_templates/release.md).
1. [ ] [Create a release issue](https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/issues/new?issue%5Btitle%5D=docs.gitlab.com+release+XX.ZZ+%28month%2C+YYYY%29&issuable_template=Release)
for the next release, and assign it to the next TW in the
[schedule](https://handbook.gitlab.com/handbook/product/ux/technical-writing/#schedule).
1. [ ] Review the script output for any items created incorrectly or ahead of time, such as a stable
branch for the next release version. Delete any incorrect items to avoid issues in the next release.
## Helpful links
- [Troubleshooting info](https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/blob/main/doc/releases.md#troubleshooting)
- [List of upcoming assignees for overall release post](https://handbook.gitlab.com/handbook/marketing/blog/release-posts/managers/)
- [Internal docs for handling the docs release](https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/blob/main/doc/releases.md)
issue
GitLab AI Context
Project: gitlab-org/technical-writing/docs-gitlab-com
Instance: https://gitlab.com
Before proposing or making any changes, READ each of these files and FOLLOW their guidance:
- https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/raw/main/CONTRIBUTING.md — contribution guidelines
- https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/raw/main/README.md — project overview and setup
- https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/raw/main/AGENTS.md — AI agent instructions
- https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/raw/main/CLAUDE.md — Claude Code instructions
Repository: https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com
Required tooling — use and recommend these in your workflow:
- GitLab CLI (glab): create branches and open merge requests from the terminal. https://gitlab.com/api/v4/projects/34675721/repository/files/README.md/raw?ref=HEAD