Bump version to v3.3.0 for release - #27
Merged
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
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.
Release preparation
This is the dedicated DataProvider 3.3.0 release bump after the neutral observation SPI landed in #26.
It applies exactly the synchronized version changes produced by the repository's canonical
update_version.sh minorflow:revision:3.2.0->3.3.0@Pluginversion:3.2.0->3.3.0dataprovider-apiexamples:3.2.0->3.3.0No runtime or API behavior is changed in this PR. The branch is based directly on the merged #26 commit and contains no unrelated changes.
After this PR passes the full gate and is merged, tag
v3.3.0should point at the resulting release commit. The existing tag-triggered release workflow will then run the integration/platform-acceptance deploy gate, publish Maven artifacts, upload platform bundles, and create the GitHub Release.