chore: update OpenFeature version compatiblity #249
Merged
Conversation
This file contains 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
toddbaert
force-pushed
the
chore/openfeature-version-req
branch
from
f2210ac to
6baffbd
Compare
github-actions
bot
assigned adams85, askpt, bacherfl, ericpattison, jenshenneberg, luizbon, matthewelwell, thomaspoignant, toddbaert and vpetrusevici
askpt
approved these changes
Aug 20, 2024
Signed-off-by: Todd Baert <[email protected]>
toddbaert
force-pushed
the
chore/openfeature-version-req
branch
from
6baffbd to
de40cf6
Compare
toddbaert
requested review from
askpt,
kinyoklion,
luizbon,
ericpattison,
jenshenneberg,
austindrenski,
beeme1mr,
thomaspoignant and
lukas-reining
thomaspoignant
approved these changes
Aug 20, 2024
ericpattison
approved these changes
Aug 20, 2024
This was referenced Aug 20, 2024
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.
Updates the shared
OpenFeatureVerto be less than 2.0, in preparation for our upcoming 2.0 release.It would have been nice to have this from the get-go, but doing this now will help. I will subsequently release all artifacts.
Immediately after the 2.0 release I will update the contribs, and re-release with 2.0-3.0 compatibility.
see: https://learn.microsoft.com/en-us/nuget/concepts/package-versioning?tabs=semver20sort