Repository navigation
docs: publish v2.4.1 release notes and update latest-release pointers - #769
Merged
Merged
Conversation
Add docs/site/release-notes/v2.4.1.md (mirrors the CHANGELOG, with a self-hosted DB-naming upgrade note), point the landing page and release-notes index at v2.4.1, and demote v2.3.7 to Previous Releases. Deploys via docs.yml on merge to master — independent of the release workflow, so it does not touch the published 2.4.1 image or the IronBank MR. (In-app docs baked into the image still lag until the next image build — tracked separately.) Signed-off-by: Will <will@dower.dev>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add docs/site/release-notes/v2.4.1.md (mirrors the CHANGELOG, with a self-hosted DB-naming upgrade note), point the landing page and release-notes index at v2.4.1, and demote v2.3.7 to Previous Releases. Deploys via docs.yml on merge to master — independent of the release workflow, so it does not touch the published 2.4.1 image or the IronBank MR. (In-app docs baked into the image still lag until the next image build — tracked separately.)