[sentry-junior]

This bumps the release workflow's pinned getsentry/craft action from 2.18.3 (1c58bfd5, labeled # v2) to 3.9.0 (2e29b081), and updates .craft.yml to match.

Why: craft's "Check release blockers" step used to ask GitHub to cancel the run and then exit 0, so the later steps kept going until the cancellation landed. That's how getsentry/symbolic run 41665569364 still prepared a release and opened a getsentry/publish issue while a release-blocker issue was open. getsentry/craft#956 fixed this in 3.9.0: the step now fails right away, and also fails if the blocker lookup errors.

Config changes (.craft.yml):

• minVersion 2.19.0 → 3.9.0.
• Replaces the deprecated changelogPolicy: auto with changelog.policy: auto.
• preReleaseCommand and versioning.policy were already set explicitly, so the new minVersion changes no defaults.
• getsentry/publish runs getsentry/craft:latest, which is 3.9.0 right now, so publishing meets the new minVersion.

Compatibility: I compared the action inputs at 2.18.3 and 3.9.0. Every input this workflow uses (version, force, merge_target, craft_config_from_merge_target) still exists; 3.9.0 only adds optional ones. The config sets no changelog.includePaths or unownedPaths, and there's no nuget target.

Dry run: I ran craft 3.9.0 prepare 99.0.0 --dry-run --no-push before and after the config change. Both times it ran scripts/craft-pre-release.sh and changed the same files (package.json and CHANGELOG.md) with no errors. After the change, the changelogPolicy deprecation warning is gone.

No open release-blocker issues in this repo right now. Once this lands, any open release-blocker issue will stop releases until it's closed or force is set.

via @BYK.

--

View Session in Sentry