Skip to content

[Backport 2.19] Update the maven snapshot publish endpoint and credential #3892

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

Open
wants to merge 1 commit into
base: 2.19
Choose a base branch
from

Conversation

RyanL1997
Copy link
Contributor

Description

Update the maven snapshot publish endpoint and credential

Related Issues

Check List

  • New functionality includes testing.
  • New functionality has been documented.
  • New functionality has javadoc added.
  • New functionality has a user manual doc added.
  • API changes companion pull request created.
  • Commits are signed per the DCO using --signoff.
  • Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@RyanL1997
Copy link
Contributor Author

seems like the security plugin didnt have snapshot for 2.19.3 yet: https://central.sonatype.com/artifact/org.opensearch.plugin/opensearch-security/2.19.2.0/dependents

@LantaoJin
Copy link
Member

why do we backport it to 2.19 rather than 2.x?

@RyanL1997
Copy link
Contributor Author

RyanL1997 commented Jul 22, 2025

why do we backport it to 2.19 rather than 2.x?

Since we have already moved to 3.x era for major version release, I think the 2.19 should be the last minor version we support for future 2.x patch releases. Similar thing was also applied to 1.3 branch when we first released 2.0 - when we do the backport of 1.x changes we directly backport it to 1.3. cc @LantaoJin

@LantaoJin
Copy link
Member

LantaoJin commented Jul 23, 2025

why do we backport it to 2.19 rather than 2.x?

Since we have already moved to 3.x era for major version release, I think the 2.19 should be the last minor version we support for future 2.x patch releases. Similar thing was also applied to 1.3 branch when we first released 2.0 - when we do the backport of 1.x changes we directly backport it to 1.3. cc @LantaoJin

Oh, sounds we had many 2.x backportings which should be backported to 2.19 instead. For example, 2.19...2.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants