Topgrade Rs Topgrade Versions Save

Upgrade all the things

v14.0.1

3 months ago

v14.0.1

Why such a quick release after v14.0.0

In Topgrade v14.0.0, we have enforced that a breaking changes notification has to be confirmed by the user when:

  1. This Topgrade is a major release
  2. The execution is the first run

This feature is good, but it won't work in the CI environment as it requires a terminal. To remedy this, I made it optional through the environment variable TOPGRADE_SKIP_BRKC_NOTIFY, with this variable set to true, the notification will be skipped.

What's Changed

New Contributors

Full Changelog: https://github.com/topgrade-rs/topgrade/compare/v14.0.0...v14.0.1

v14.0.0

3 months ago

v14.0.0

Breaking changes

After this release, breaking changes will be printed when:

  1. This release is a major release
  2. You run it for the first time

Topgrade won't continue until you confirm these breaking changes.

$ topgrade --version
Topgrade 14.0.0

$ topgrade

── 11:16:41 - Topgrade 14.0.0 Breaking Changes ─────────────────────────────────
1. In 13.0.0, we introduced a new feature, pushing git repos, now this feature
   has been removed as some users are not satisfied with it.

   For configuration entries, the following ones are gone:

  
   [git]
   pull_only_repos = []
   push_only_repos = []
   pull_arguments = ""
   push_arguments = ""
  


Confirmed? (y)es/(N)o

What's Changed

New Contributors

Full Changelog: https://github.com/topgrade-rs/topgrade/compare/v13.0.0...v14.0.0

v13.0.0

6 months ago

Breaking Changes

  1. In this release, Topgrade implements a new feature: pushing git repos

    [git]
repos = []

    so the repos specified in git.repos will be pulled AND pushed, if you only want to pull repos, set them in git.pull_only_repos, for more information, see config.example.toml.

  2. There are some configuration entries that were put under the misc section, then they were moved to their own section, for example:

    [misc]
git_repos = []

    [git]
repos = []

    Before this release, it was still allowed to specify these entries in the misc section as we were maintianing a compatiable layer to make it work.

    Now, this layer has been removed, our users should use the new configuration format.

    You won't encounter this issue unless you are using a really old configuration file, so technically this is not a breaking change IMHO.

What's Changed

New Contributors

Full Changelog: https://github.com/topgrade-rs/topgrade/compare/v12.0.2...v13.0.0

v12.0.2

9 months ago

v12.0.2

This release is mainly a bug fix for the --yes option of the System steps on:

  • DragonFlyBSD
  • SUSE
  • openSUSE Tumbleweed
  • openSUSE MicroOS
  • PCLinuxOS
  • Solus
  • pacdef Linux users
  • Clear Linux

If you are suffering from this issue, please update to this version.

What's Changed

New Contributors

Full Changelog: https://github.com/topgrade-rs/topgrade/compare/v12.0.1...v12.0.2

v12.0.1

9 months ago

What's Changed

New Contributors

Full Changelog: https://github.com/topgrade-rs/topgrade/compare/v12.0.0...v12.0.1

v12.0.0

10 months ago

Warning: Config Files may have to be edited for this release to work

display_preamble = true has to be disabled

What's Changed

New Contributors

Full Changelog: https://github.com/topgrade-rs/topgrade/compare/v11.0.2...v12.0.0

v11.0.2

1 year ago

Version bump was forgotten to be done in the Cargo.toml file when updating to v11.0.1, so here is v11.0.2.

What's Changed

Full Changelog: https://github.com/topgrade-rs/topgrade/compare/v11.0.0...v11.0.2

v11.0.1

1 year ago

What's Changed

v11.0.0

1 year ago

What's Changed

New Contributors

Full Changelog: https://github.com/topgrade-rs/topgrade/compare/v10.3.3...v11.0.0

v10.3.3

1 year ago

What's Changed

New Contributors

Full Changelog: https://github.com/topgrade-rs/topgrade/compare/v10.3.2...v10.3.3