Skip to content

ci(release): Bump craft to 2.34.1 - #331

Merged
joshuarli merged 1 commit into
mainfrom
ci/bump-craft-2.34.1
Oct 14, 2026
Merged

joshuarli merged 1 commit into
mainfrom
ci/bump-craft-2.34.1

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

The release workflow pinned getsentry/craft@c6e2f04 (2.19.0). That action version never actually resolved its own pin: it expands ${{ github.action_ref }} inside a composite run: step, where it is always empty (actions/runner#2473). So every release fell back to an unauthenticated curl https://api.github.com/repos/getsentry/craft/releases/latest and installed whatever the latest Craft was, not 2.19.0. When the shared runner IP runs out of anonymous API quota, that call 403s. That's how this release run failed (curl: (22) The requested URL returned error: 403).

From 2.34.x onward (getsentry/craft#891), the action passes the ref through env, resolves a SHA pin to the matching release, and downloads github.com/getsentry/craft/releases/download/<version>/craft directly, with no anonymous API call. watto's release, on the same pin, logs Downloading Craft 2.34.1 from: https://github.com/getsentry/craft/releases/download/2.34.1/craft.

The action inputs this workflow uses (version, force) are unchanged in 2.34.1.

cc @joshuarli

via @joshuarli.

--

View Junior Session [Sentry]

The c6e2f04 (2.19.0) pin expands github.action_ref inside a composite
run step, where it is always empty (actions/runner#2473). The action
then falls back to an unauthenticated releases/latest API call, which
403s when the shared runner IP is rate limited. 2.34.1 passes the ref
via env and resolves the SHA pin to its own release download.

Co-Authored-By: Joshua Li <14209781+joshuarli@users.noreply.github.com>
@joshuarli
joshuarli merged commit f7a0a1c into main Oct 14, 2026
17 of 18 checks passed
@joshuarli
joshuarli deleted the ci/bump-craft-2.34.1 branch October 14, 2026 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant