BaselineJavaVersions handles the lazy 'nebula.maven-publish' plugin #1986
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
carterkozak
added
no changelog
autorelease
merge when ready
and removed
no changelog
labels
Generate changelog in
|
fawind
approved these changes
Nov 23, 2021
|
Released 4.43.0 |
This was referenced Nov 23, 2021
Merged
bulldozer-bot bot
pushed a commit
to palantir/witchcraft-api
that referenced
this pull request
Nov 23, 2021
###### _excavator_ is a bot for automating changes across repositories. Changes produced by the roomba/latest-baseline-oss check. # Release Notes ## 4.43.0 | Type | Description | Link | | ---- | ----------- | ---- | | Fix | BaselineJavaVersions handles the lazy 'nebula.maven-publish' plugin | palantir/gradle-baseline#1986 | To enable or disable this check, please contact the maintainers of Excavator.
This was referenced Nov 23, 2021
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.
Before this PR
Whether a component is considered a library or distribution could change part-way through evaluation when the lazy
nebula.maven-publishplugin was applied.After this PR
==COMMIT_MSG==
BaselineJavaVersions handles the lazy 'nebula.maven-publish' plugin
==COMMIT_MSG==
Possible downsides?
This pattern could appear elsewhere and require similar remediation. Ideally we would have addressed the root cause.