[sentry-junior]

This bumps the release workflow's pinned getsentry/craft action from 2.19.0 (c6e2f049, labeled # v2) 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 the action kept going and could still prepare a release and open a getsentry/publish issue while a release-blocker issue was open (seen in getsentry/symbolic). getsentry/craft#956 fixed this in 3.9.0: the step now fails right away, and it also fails if the blocker lookup errors.

Compatibility with craft 3.x:

• The workflow's action inputs (version, force, merge_target, craft_config_from_merge_target) all still exist in 3.9.0; releases between only added optional inputs.
• None of the 3.0 breaking changes apply: .craft.yml doesn't set changelog.includePaths/unownedPaths, there's no nuget target, and it defines preReleaseCommand, so the new "fail when auto-bump finds nothing" check doesn't run.
• I ran the craft 3.9.0 binary with prepare 99.0.0 --dry-run --no-push on current master. It ran scripts/craft-pre-release.sh, bumped package.json and src/version.ts, and finished without errors.

There are no open release-blocker issues in this repo right now. Once this lands, any open one stops releases until it's closed or force is set.

No changelog entry, since this is CI-only.

Config changes (follow-up commit, so .craft.yml matches craft 3.9.0):

Sets minVersion from 2.17.0 to 3.9.0. Nothing else needs to change, since preReleaseCommand and changelog.policy are already explicit and the auto versioning default stays the same.

I ran craft 3.9.0 prepare 99.0.0 --dry-run --no-push before and after this change on a full clone. Both runs bumped package.json and src/version.ts with no new warnings or errors.

via @BYK.

--

View Session in Sentry