feat: WIP provider versioning and releases #63
Closed
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
fabriziodemaria
force-pushed
the
providers-releases
branch
5 times, most recently
from
30ff632 to
97ca749
Compare
fabriziodemaria
force-pushed
the
providers-releases
branch
from
97ca749 to
355d0c8
Compare
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.
Automates and standardizes releases for the OpenFeature providers (Java and JS) via release-please and build tooling updates. Streamlines versioning, tagging, and publish steps; aligns dependency/version propagation across packages.
When a change in the confidence-resolver is detected, release please will create a small file in the providers' path to ensure that a new version will be created for them (even if there is no code change in the providers' source code itself).
After the release PR is merged, the confidence-resolver version is pinned in the Java and JS providers, so that when the final JAR and tarball will be built they will embed the wasm with the pinned version in them.
Example release PR: fabriziodemaria#2