Refactor release task to use releases.yml
What does this MR do and why?
- Refactors release.rake to use releases.yml instead of release_dates.json.
- Removes release_dates.json.
Why: releases.yml is now the SSoT for GitLab release information. We no longer need to maintain our own JSON file for this.
Related: !4302 (merged)
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
-
Configure a local GitLab Docs environment: https://gitlab.com/gitlab-org/gitlab-docs/-/blob/main/doc/setup.md. -
Try running the release rake task: DRY_RUN=true bundle exec rake release:single
You should see output like this, with the expected version (16.5):
INFO: (gitlab-docs): DRY RUN: Not stashing local changes.
INFO: (gitlab-docs): DRY RUN: Not checking out main branch and pulling updates.
INFO: (gitlab-docs): DRY RUN: Not creating branch 16.5.
INFO: (gitlab-docs): DRY RUN: Not creating file 16.5.Dockerfile.
INFO: (gitlab-docs): DRY RUN: Not adding file 16.5.Dockerfile to branch 16.5 or committing changes.
INFO: (gitlab-docs): DRY RUN: Not pushing branch 16.5.
Merge request acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this merge request.
Closes #1716 (closed)
Edited by Sarah German