@W-21307215 Remove sonatype visibility logic#163
Merged
douglasdew merged 1 commit intosalesforce:mainfrom Feb 18, 2026
Merged
Conversation
douglasdew
requested review from
bairenlong-sfdc and
sahil-here
and removed request for
sahil-here
sahil-here
approved these changes
Feb 18, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR removes a bit of logic from maven-release.yml that had been added to ensure visibility in the Sonatype portal.
Although this logic was called for by the Sonatype documentation, we are experiencing artifact duplication in Sonatype. So, as a troubleshooting measure, we are removing this logic and then checking to see if the artifact duplication has been eliminated.