-
Notifications
You must be signed in to change notification settings - Fork 183
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
[RELEASE] Release v. Next #1093
Comments
Tagging @Xtansia for a release, or I can take care of it early next week. @jordanpadams want to try and help with the fix for the SNAPSHOT workflow? |
@dblock the 403 forbidden indicates an issue with the login information, which I do not have access to. It needs to be updated either with the correct username/password, or it may need to be a generated set of tokens generated through Sonatype: https://central.sonatype.org/publish/generate-token/ |
Hi @dblock , Something does not seem right with the release. The bug #1068 we wanted to fix is not fixed in the release (according to my tests). And, randomly, I also noticed that the following commit 3738026 is not in the release. It was in the main branch when I tested the bug fix. Do you have an idea why that is ? Thanks |
@tloubrieu-jpl I can confirm from decompiling the 2.12.0 jar from Maven that it does contain the changes from PR #1072. Can you please confirm your POM/Gradle/etc. configuration and which version of the dependency you are taking? It will not contain commit 3738026 as that is only going in the next major release (3.0.0) as it is a breaking change. The |
Thanks @Xtansia , I captured the maven dependencies of my project there:
I could retest by building from branch |
@tloubrieu-jpl You'll need an AOSS collection and authenticated creditionals.
Note that if you're using SSO based auth you'll also need to include that jar into the build. |
I opened #1101 to run integration tests against a real instance. This is a common problem in all clients, parent being opensearch-project/opensearch-clients#47. |
Thanks @workmanw , I am getting this error when I run the integration test as you proposed:
I am completelly new to |
Can we get a new tagged release of the library per bug fix #1068? This is a blocker for our AOSS migration efforts.
If this is a lot of effort, fixing this bug with publishing this SNAPSHOT would at least allow us to get out an interim build. Thanks!
The text was updated successfully, but these errors were encountered: