Update to v6.2.3. No code changes needed. #32
Merged
Conversation
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
Instead, I added an easy way to add meaningless commits, which can be helpful to avoid issues with having multiple git tags and releases point to the same git hash.
|
Sorry for the version number churn in SS:GrB. I normally don't tag a version with tiny changes just in the documentation or comments, like v6.2.3 has. However, I'm about to release an update SuiteSparse meta-package and I wanted to include this minor change. So I called this SS:GrB v6.2.3 to give it a name for when it goes in SuiteSparse v5.11.0 (to appear soon), here: https://github.com/DrTimothyAldenDavis/SuiteSparse/tree/dev . |
|
No worries! Release as often as you wish :) I actually hadn't gotten around to building 6.2.2 yet, so no additional bother on our end to go straight to 6.2.3. |
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.
Instead, I added an easy way to add meaningless commits, which can be helpful to avoid issues with having multiple git tags and releases point to the same git hash.