[sentry-junior]

📜 Description

This bumps the release workflow's pinned getsentry/craft action from 2.23.2 (d6302019, labeled # v2) to 3.9.0 (2e29b081).

💡 Motivation and Context

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.

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.

💚 How did you test it?

Checked the craft 3.0 breaking changes against this repo:

• The workflow's action inputs (version, force) are unchanged in 3.9.0; releases between only added optional inputs.
• .craft.yml doesn't set changelog.includePaths/unownedPaths, and there's no nuget target.
• minVersion is 1.2.1, so craft keeps running the default scripts/bump-version.sh instead of the new automatic bumping.

I also ran the craft 3.9.0 binary with prepare 99.0.0 --dry-run --no-push on current main. It ran scripts/bump-version.sh, bumped both gradle.properties files, and finished without errors. It does warn that changelogPolicy is deprecated in favor of changelog.policy, but it still accepts it.

No changelog entry, since this is CI-only.

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

Sets minVersion from 1.2.1 to 3.9.0. Under the old minVersion, craft defaulted to running scripts/bump-version.sh and to the manual versioning policy. At 3.9.0 those defaults become automatic target bumping and auto, so this also adds preReleaseCommand: bash scripts/bump-version.sh and versioning.policy: manual to keep releases working the same way. This also replaces the deprecated top-level changelogPolicy: auto with changelog.policy: auto.

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 the same gradle.properties files, and the changelogPolicy deprecation warning is gone.

via @BYK.

--

View Session in Sentry