docs(changelog): update for v1.29.0 stable release#4697
docs(changelog): update for v1.29.0 stable release#4697rami3l wants to merge 2 commits intorust-lang:mainfrom
Conversation
| * chore(deps): lock file maintenance by @renovate[bot] in https://github.com/rust-lang/rustup/pull/4630 | ||
| * feat: Added xonsh shell support by @anki-code in https://github.com/rust-lang/rustup/pull/4626 | ||
| * download: statically bundle relevant trust anchors by @djc in https://github.com/rust-lang/rustup/pull/4631 | ||
| * test(static-roots): refine `store_static_roots()` by @rami3l in https://github.com/rust-lang/rustup/pull/4634 |
There was a problem hiding this comment.
Kind of pre-existing, but maybe drop a bunch of the chore and test PRs from this list, since they don't affect the published product?
There was a problem hiding this comment.
@djc I see what you mean and I can grep them away immediately, but there hasn't been a very effective way of filtering out all those lines unless we stick to semantic commit PR titles: there has been a lot of them actually up to this point, and it's not very practical to open each of them and see what it does 🤔
There was a problem hiding this comment.
Speaking of which, I would like to enforce semantic commit PR titles in the future so that we can do something like https://github.com/googleapis/release-please.
There was a problem hiding this comment.
IMO it's fine to make a first pass based on the obvious suspects (all of the PRs authored by dependabot), anything that did use the a test or ci prefix...
|
We should try to land before release |
3 participants
Warning
This PR is waiting on #4696.
This is the 1st PR for the
1.29.0stable release according to our release process.This PR will also close #4652 via a
dev-guideupdate.Checklist
Bump version in the manifest.(Not required, already done in dist: bumprustupversion to v1.29.0 #4513.)