[sentry-junior]

This bumps the release workflow's pinned getsentry/craft action from 3.0.0 (924b450e) to 3.9.0 (2e29b081).

Why: craft's "Check release blockers" step used to ask GitHub to cancel the run and then exit 0, so later steps kept going and could open a getsentry/publish issue even with a release-blocker issue open (seen in getsentry/symbolic run 41665569364). getsentry/craft#956 fixed this in 3.9.0: the step now fails right away, and it also fails if the blocker lookup errors. Older pins don't get the fix.

Compatibility with craft 3.x:

• Action inputs only gained new optional ones between the old pin and 3.9.0, so the existing with: inputs stay valid.
• None of the 3.0 breaking changes apply here:
  • The repo is already on 3.x, so the 3.0 breaking changes are already in effect. I checked them anyway: .craft.yml doesn't set changelog.includePaths or unownedPaths.
  • It defines preReleaseCommand, so the auto-bump check doesn't run.
  • There's no nuget target.
• I ran craft 3.9.0 prepare 99.0.0 --dry-run --no-push against current main. It ran scripts/bump-version.sh (uv version + uv lock) and finished without errors. The first attempt failed only because uv wasn't installed locally.

There are no open release-blocker issues here right now. Once this lands, an open one will stop releases until it's closed or force is set.

Config changes (.craft.yml, for craft 3.9.0):

• Sets minVersion to 3.9.0 (was 2.21.1).
• The other defaults craft picks from minVersion (auto-bump from 2.21.0, auto versioning from 2.14.0) already apply at 2.21.1, so release behavior doesn't change.
• craft 3.9.0 prepare 99.0.0 --dry-run --no-push, run before and after this change, bumps the same files (CHANGELOG.md, pyproject.toml, uv.lock) with no new errors or warnings.

via @BYK.

--

View Session in Sentry