Age | Commit message (Collapse) | Author |
|
Otherwise, if we start doing crate releases from the local checkout
(with git tags) and it turns out that origin/master has newer commits,
rebasing local master will then invalidate those tags.
|
|
I do run --aggressive, although I've been ignoring the clap 3 update for
what seems like forever since it's still in beta.
|
|
This tightens up the wording in ripgrep's opening description. It's used
in several places, so we update all of them.
Closes #1881
|
|
And update the release checklist to mention this process.
|
|
In particular, explicitly note when to update the CHANGELOG.
Also, tweak the ripgrep introductory message.
|
|
|
|
Getting the crate order right is important, so document it.
|
|
It's just good sense to make sure everything is updated if possible.
|
|
The steps are numerous, subtle and complex enough that it's worth
writing them down. In particular, getting the order correct is
important. (i.e., If we released to crates.io first and the GitHub
release infrastructure failed, then we'd be in a pickle.)
|