-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(beta/new_java_build): release 1.14.1-beta #1322
chore(beta/new_java_build): release 1.14.1-beta #1322
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
blocked do not merge
80a4dbf
to
bbe0a64
Compare
386fe00
to
d17de13
Compare
bbe0a64
to
f9d2e23
Compare
d17de13
to
a88d8fc
Compare
f9d2e23
to
15ca167
Compare
a88d8fc
to
fd77f1d
Compare
15ca167
to
ea2ebfe
Compare
fd77f1d
to
67173c7
Compare
ea2ebfe
to
9cd20db
Compare
67173c7
to
4396ea8
Compare
@open-feature/sdk-java-maintainers i think we could use this, to generate a beta release, with an artifact build with a newer version of java - which allows our users to test, if they have any kind of problem with this release, and also with our current contrib sdks. so we can be sure to not break anything for anybody by building with a newer jdk |
4396ea8
to
a64470e
Compare
Signed-off-by: Simon Schrottner <[email protected]>
a64470e
to
a3665c0
Compare
|
632948c
to
2159941
Compare
🤖 I have created a release beep boop
1.14.1-beta (2025-02-12)
🐛 Bug Fixes
🧹 Chore
This PR was generated with Release Please. See documentation.