* Initial Releases:
- [x] Update CHANGELOGs documentation
- [x] Move deploy@3.1.0 to deploy@3.0.1
- [x] Merge PRs
- [x] Publish a test build of an image
- [x] Confirm `docker compose up` pulls most recent image for tagNow that we are embracing a single WBS release track based upon the every 6 months MediaWiki major releases, if not make ammendments
- [x] Prepare [[ https://docs.google.com/document/d/1qjybkd4zAOvjVF6LCjJNEFhHn2otvHEFtTlNMcUshgI/edit?usp=drive_link | release announcement ]]
- [x] release announcement reviewed
- [x] release announcement sent
- [x] Publish releases by tagging the initial release commit with versions
* [x] Merge PRs for next series of releases for team demo
* [x] Add notes to ./README.md about running release locally https://github.com/wmde/wikibase-release-pipeline/pull/825
[] {T373877}we can review and clarify our release process and related code accordingly. This task is for a Spike to consider any process and code-level changes which we can or should make given this new understanding.
Some orienting objectives to this Spike are as follow:
[] Align as eng team on how process works / onboard all eng team into parts which are clear
[] Summarising and demoing what needs to be done on next set of transitional releases
[x] Changelogs- Remove any unnecessary complexity in our build and release related code and user documentation
[x] NX- Analyze and report any remaining barriers to automating WBS Wikibase Image patch releases triggered by MediaWiki security patch releases in between every 6 month major releases
[x] Release Process from start to end (dry run)- Analyze what is required to automate WBS Image releases based upon patch and minor updates to underlying dependencies (e.g. PHP, Node, etc), and create (or update if exists) a Phabricator task with results of this analysis
[x] Release Process from start to end
→ we published the Patch Releases + Latest MW version
[x] Up to publishing image on dockerhub
***- Depending on the scope of needed changes identified in the above analysis, implement some or all of the recommended changes in PRs
* [ ] ~~Create LTS and Last branches for wikibase and deploy:~~ Single branch**This ticket is considered complete when all of the above analysis, LTS products https://github.com/wmde/wikibase-release-pipeline/pull/815planning and/or implementation (depending on scope) is completed.**
- [x] {T374211} Consider removing `deploy-3` branch in favor of `main` branch in docs...
- [x] Update docs for new branch names (including main vs deploy-3 IF we do away with) https://github.com/wmde/wikibase-release-pipeline/pull/824
- [] ~~Our branches are (Deploy and Wikibase)?~~
- [] ~~LTS: MediaWiki-1.39~~
- [] ~~Last: MediaWiki-1.4x~~
- [] ~~Latest: main~~
- [x] Merge mediawiki patch PRs for 1.39.10 and 1.41.4 {T376243}
- [x] Prepare new version of wikibase and deploy {T378504}
- [ ] {T377426}
* [x] Prep and plan for team time:
- [x] Schedule team time
- [x] Document Conventional Commits types for our project,
- [x] including note about where they show-up in the CHANGELOGs: [https://github.com/nrwl/nx/blob/db10812da789cd48d3a722628a00feda9d0e3810/packages/nx/src/command-line/release/config/conventional-commits.ts](https://github.com/nrwl/nx/blob/db10812da789cd48d3a722628a00feda9d0e3810/packages/nx/src/command-line/release/config/conventional-commits.ts)
***
**Follow-up:**
* [x] Make Phab ticket: Try rulesets and apply SSH Deploy Key for Release workflow T378935
* [x] Make Phab ticket: For publish workflow for Deploy add "latest" (or?) git tag. Put this tag in the documentation for checking out Deploy T378938
* [ ] Make Phab ticket (spike): How does the user know which version of the images they are on and how to get to the current documentation for them. T378943
* [x] Make Phab ticket: Ensure successful tests before release / publish T378941
**Action items**
[x] Create a ticket for fixing mergeability of docs only PRs T378935
[] Issue comes from these 2 opposed rules: (1) run no CI tests when PR contains only doc changes,//This ticket has a long history and has attached to it significant previous work. (2) merging a PR for a release requires running the CI tests
[x] Create a ticket to check format and linting on the docs T378948
[x] Create a ticket to add the PR links to the changelogs ([[ https://19.nx.dev/recipes/nx-release/configure-changelog-format | link ]]) T378950
[x] BUG: Create_release.yml should push to the branch specified in the workflow invocation [FIXED](https://github.com/wmde/wikibase-release-pipeline/commit/fe7f8918caf016d663a65827bd4efb7deda768f8)
[x] Consider the purpose and the audience of the DOCS folderPlease reference the history of this description to see the record of earlier completed work. Then change it accordingly - part of T378943
[x] Deploy docs still ask the user to checkout deploy-3 while the release notes mention deploy@3.0.2 as the tag to checkout - should be covered in T378938//---