-
Notifications
You must be signed in to change notification settings - Fork 162
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
Perform a dry run #254
Comments
That's a badly needed feature 👍 |
As a workaround until this is implemented, you can specify the |
I've been setting these to publish locally to test out my changes:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Many times I published a version, only to find out there is something wrong with it (typically cross-publishing not doing what I was expected).
When that happen I have to keep publishing until it does what I want, and I end up burning version numbers with bad versions.
Maybe sbt-release could provide a way to do a "dry run" so we see what artifacts would be published, but without any impact on the source repository or the artifact repository?
The text was updated successfully, but these errors were encountered: