[sentry-junior]

Bumps the pinned getsentry/craft action from 2.33.3 (4e164274) to 3.9.0 (2e29b081).

Craft's "Check release blockers" step used to call the async run-cancel API and then exit 0, so the job kept going and could still open a getsentry/publish issue while release-blocker issues were open (example in getsentry/symbolic). getsentry/craft#956 fixed that, and the fix shipped in craft 3.9.0. This is the same change as getsentry/symbolic#1134.

minVersion is 0.23.1, so craft keeps using scripts/bump-version.sh and the 3.0 automatic version bumping change doesn't apply. There's no top-level changelog.includePaths/unownedPaths and no nuget target. I ran craft 3.9.0's craft prepare 99.0.0 --dry-run --no-input --no-push on the default branch before this change. It passed and bumped the crate Cargo.toml versions as expected.

There are no open release-blocker issues here, so nothing stops the next release. From now on, any open release-blocker issue will stop the release.

Config changes: minVersion 0.23.1 → 3.9.0. To keep releases the same, this adds preReleaseCommand: bash scripts/bump-version.sh, which was craft's default below 2.21.0, and versioning.policy: manual, which was the default below 2.14.0. The deprecated changelogPolicy: auto is now changelog.policy: auto. craft 3.9.0's prepare 99.0.0 --dry-run gave the same result before and after this change: the same 18 files were bumped (the crate Cargo.toml files, Cargo.lock and CHANGELOG.md). The deprecation warning is gone.

via @BYK.

--

View Session in Sentry