Release v1.49.0

Request

I'd like to ask that we perform a release of GitLab Pages. We've brought in a new version of the labkit which contains a supposed fix for the current situation where Profiling is not currently being gathered properly since the migration of this service into Kubernetes. Reference: gitlab-com/gl-infra/production#6011 (closed)

We may want to consider getting an issue opened such that GitLab Pages is upgraded via auto-deploy similar to that of Gitaly. I'll let the Pages team decide if this is a route that is desired.

---

• Set the milestone on this issue
• Decide on the version number by reference to the Versioning
  • Typically if you want to release code from current master branch you will update MINOR version, e.g. 1.12.0 -> 1.13.0. In that case you don't need to create stable branch
  • If you want to backport some bug fix or security fix you will need to update stable branch X-Y-stable
• Create an MR for gitlab-pages project. You can use this MR as an example.
  • Update VERSION, and push your branch
  • Update CHANGELOG by running GITLAB_PRIVATE_TOKEN= make changelog, note that you need to create a personal access token
  • Assign to reviewer
• Once gitlab-pages is merged create a signed+annotated tag pointing to the merge commit on the stable branch In case of master branch:

  git fetch origin master
  git fetch dev master
  git tag -a -s -m "Release v1.49.0" v1.49.0 origin/master

• Verify that you created tag properly:

  git show v1.49.0

  it should include something like:
  • (tag: v1.40.0, origin/master, dev/master, master) for master
• Push this tag to origin(Skip this for security release!)

  git push origin v1.49.0

• Wait for tag to be mirrored to dev or push it:

  git push dev v1.49.0

• Create an MR for gitlab project. You can use this MR as an example.
  • Update GITLAB_PAGES_VERSION
  • Added Changelog: added footer to your commit
  • Assign to a reviewer