Prepare for a bug fix release. - #650
Merged
Merged
Conversation
Collaborator
Author
|
What are the remaining steps? Create the tag and a github release, etc? |
adamdempsey90
approved these changes
Aug 10, 2026
Collaborator
Yes if you click on the release thingy on the right bar, you can create a release after this is merged. I typically use the changelog for the release notes. You can create a tag inline when you make the release. Then we need to submit an MR to xcap-spackages and to spack upstream each. If you're interested in doing that stuff, it's appreciated, if not I can do it. |
Collaborator
Author
|
Yes, I'll do it. I have an MR in to xcap-spackages to patch 1.12.0. I'll add 1.12.1 in that MR unless there are objections to combining them. |
Collaborator
|
Combining them sounds good to me. Thanks! |
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.
PR Summary
Release at 1.12.1 to include the registration of missing headers.
PR Checklist
make formatcommand after configuring withcmake.plan_historiesfolder, with a filename the same as the MR number.If preparing for a new release, in addition please check the following: