Update changelog #549
Merged
Update changelog #549
Conversation
This file contains 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
Bumps [actions/configure-pages](https://github.com/actions/configure-pages) from 4 to 5. - [Release notes](https://github.com/actions/configure-pages/releases) - [Commits](actions/configure-pages@v4...v5) --- updated-dependencies: - dependency-name: actions/configure-pages dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
ahouseholder
requested review from
sei-vsarvepalli,
cgyarbrough and
j---
as code owners
ahouseholder
added
bug
sei-vsarvepalli
approved these changes
Apr 12, 2024
|
Noting for future reference that I did not, in fact, move the existing |
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.
We didn't update the changelog file to match the release notes for version 2024.3 last month. This PR fixes that in
main.Once this is merged into
main, I'll do a second PR to mergemain→publishso the web site will update.I also plan to move the 2024.3 release tag to point to the updated commit on
main. Room for debate whether the right thing to do is to (a) move the tag or (b) add a new tag like 2024.3.1 since there have been a few dependency updates.I'm ok with either, and neither one needs to be a binding precedent. If you'd prefer option B, please comment as much on this PR, otherwise I'll plan to execute option A.