Open gnunicorn opened 2 years ago
the unleash-check-CI job is currently disabled (I don't know why) but must run the release job, at least on the PR that intends to bump versions, to ensure things aren't breaking (ideally on every PR to make sure we've catch bugs early and not only when we intend to release it)
Digging into the history of this, it seems it was temporarily deactivated to wait for an external fix that has been merged already Sept 15th – just no one re-activated the jobs properly. Gonna give it a try and see if this is a quick one to sort out.
Right now, the CI job is releasing creates when it finds a
ci-release
-tag on the commit. However, we want the job to run on every merge into master and release all crates where versions have been changed compared to what is released on crates.io at the moment. From a technical perspective this only requires switching the unleash job to run onmaster
, but before we can do that we have to consider a few aspects:unreleased
-section are moved properly? Maybe through a helper job and a flag oncargo unleash
that checks the title isn't present upon release?Cargo.toml
as well. Can we help with dependabot-setups to make sure everyone is on latest? How do we deal with the problem that some downstream tooling might needs a while to upgrade to latest MAJOR while others does and the user that wants to combine both ends up in an unrecoverable situation (cargo doesn't knowsemver version ranges
)?