RELEASE: Add step to update libdnf's deps
In the latest release, we should've bumped librepo's requirement. It doesn't use symbol versioning, so we don't automatically get this. At release time at least, we should just peek at the spec we're baking in and pick up from that. Clearly the updated deps are in the buildroot if CI is green, so this should mostly be a matter of bumping to versions which are already shipped in Fedora. See: https://github.com/rpm-software-management/libdnf/pull/1128 See: https://github.com/coreos/rpm-ostree/pull/2644 See: https://bugzilla.redhat.com/show_bug.cgi?id=1943773
This commit is contained in:
parent
b2c68b3309
commit
8e22075721
@ -6,7 +6,9 @@ nav_order: 8
|
||||
|
||||
1. Increment the `year_version` and `release_version` macros in `configure.ac`.
|
||||
2. Increment the `Version` field in `rpm-ostree.spec.in`.
|
||||
3. Submit as a PR and wait until reviewed *and* CI is green.
|
||||
3. Verify the libdnf deps in `rpm-ostree.spec.in` are up to date by comparing to
|
||||
the spec of the bundled version (`libdnf/libdnf.spec`).
|
||||
4. Submit as a PR and wait until reviewed *and* CI is green.
|
||||
5. Once merged, do `git pull $upstream && git reset --hard $upstream/master` on
|
||||
your local `master` branch to make sure you're on the right commit.
|
||||
6. Draft release notes by seeding a HackMD.io with `git shortlog $last_tag..`
|
||||
|
Loading…
Reference in New Issue
Block a user