[sentry-junior]

This bumps the release workflow's pinned getsentry/craft action from 2.26.14 (cdb657d4) 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 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 also fails if the blocker lookup errors. Older pins don't get the fix.

Compatibility with craft 3.x:

• None of the 3.0 breaking changes apply:
  • .craft.yml doesn't set changelog.includePaths or unownedPaths.
  • minVersion is 2.21.1, but preReleaseCommand is set, so the new "fail when auto-bump finds nothing" check doesn't run.
  • There's no nuget target.
• Action inputs only gained new optional ones between 2.x and 3.9.0, so the existing with: inputs stay valid.
• I ran craft 3.9.0 prepare 99.0.0 --dry-run --no-push against current master. With Ruby installed, it ran .scripts/batch_release.rb and finished without errors. (The first try failed only because Ruby was missing from my environment.)

There are no open release-blocker issues in this repo right now, so releases aren't affected today.

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

• minVersion: 2.21.1 → 3.9.0. preReleaseCommand and changelog.policy are already set, so nothing else changes.
• craft 3.9.0 prepare 99.0.0 --dry-run --no-push, before and after: both runs bump the same files (CHANGELOG.md plus the gems' version.rb and gemspec files) and finish without errors.

via @BYK.

--

View Session in Sentry