-
Notifications
You must be signed in to change notification settings - Fork 360
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
Auto-release all clients when publishing with Maven #8378
Conversation
Nice! |
pkg/config/config.go
Outdated
@@ -388,6 +388,11 @@ type Config struct { | |||
Enabled bool `mapstructure:"enabled"` | |||
FlushInterval time.Duration `mapstructure:"flush_interval"` | |||
} `mapstructure:"usage_report"` | |||
Plugins map[string]struct { |
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.
What this change for?
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.
OMG!!?!
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.
Sorry @Isan-Rivkin , PTAL...
This property is covered in [the docs](https://central.sonatype.org/publish/publish-maven/#nexus-staging-maven-plugin-for-deployment-and-release). It also allows for a manual review opportunity... but given that we don't do that, and that we test first, let's not go there.
8e00fbb
to
ce834ec
Compare
Also worth noting the beautiful XML inheritance model for pom.xml. This affects all 3 Java clients. |
Thanks! |
Look what I found! This property is covered in the
docs. It also allows for a manual review opportunity... but given that we don't do that, and that we test first, let's not go there.
Fixes #7974.
Tested by manually triggering a release on this branch. It finished and I see no staging repository on https://s01.oss.sonatype.org/#stagingRepositories. Naturally we will need to wait to see whether a release
test-auto-release
actually made it to Maven central.But it's worth pulling even now, in the worst case we still need to do something extra.