Skip to content
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

fix(config)!: Disable dev-version by default #340

Merged
merged 5 commits into from Oct 8, 2021
Merged

Conversation

epage
Copy link
Collaborator

@epage epage commented Oct 8, 2021

Having a post-release version bump can help communicate that someone is
using main but has the problems of

  • It isn't actually the next version because the next version is unknown
  • It hurts users of the crate being released because they can't as
    easily [patch] the depedency with main to test out the new release

As part of implementing this, I decided to switch from negative config values to positive ones

  • Keeping all default values as false can be nice
  • However, it causes churn when changing defaults
  • Having double negatives is annoying

I still kept the negatives in the CLI but also added positive versions, though hidden. This also allows overriding the config file.

Instead of just allowing overriding of defaults, this also allows
overriding of the config.

BREAKING CHANGE: This did cause a change in precedence between `--sign`
and `--sign-commit` / `--sign-tag`.
Having a post-release version bump can help communicate that someone is
using `main` but has the problems of
- It isn't actually the next version because the next version is unknown
- It hurts users of the crate being released because they can't as
  easily `[patch]` the depedency with `main` to test out the new release

Fixes crate-ci#82

BREAKING CHANGE: We've changed the default `dev-version = false` to
`dev-version = true`.
@epage epage merged commit a6b1efa into crate-ci:master Oct 8, 2021
@epage epage deleted the default branch October 8, 2021 16:18
bors bot added a commit to nix-rust/nix that referenced this pull request Dec 18, 2021
1609: Fix warning when running cargo release r=rtzoeller a=rtzoeller

`cargo release` is returning the following warning: `WARN  cargo_release::config] Negative config values are deprecated ('no_', 'disable_')`.

The root cause is `cargo-release` changing its behavior to default to not bumping the version: crate-ci/cargo-release#340. Remove the `no-dev-version flag` from release.toml to match.


Co-authored-by: Ryan Zoeller <rtzoeller@rtzoeller.com>
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.

None yet

1 participant