update the release version in the package.xml#114
Merged
christian-rauch merged 1 commit intomainfrom Oct 31, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Pump the version in the
package.xml. This is required for new bloom releases, as bloom will match the version in thepackage.xmlwith the git tags, and hence will only release4.0.0for now, even if4.1.1is tagged.Also, since 4.1.1 there are a couple of update to the API and fixes. So let's release a new 4.2.0.
@AndrejOrsula The version in the
package.xmlshould be synced with the tag.