cloudflare / cloudflare/wrangler-action
Correct SHA for v4 ?
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Description
Hi! I'm from the `fastapi` team, and we're using this action in our production repos. I encountered an issue when updating to v4.
On the [release page](https://github.com/cloudflare/wrangler-action/releases), v4.0.0 points to commit [`ebbaa1584979971c8614a24965b4405ff95890e0`](https://github.com/cloudflare/wrangler-action/commit/ebbaa1584979971c8614a24965b4405ff95890e0) (`ebbaa15`). Similarly, our dependabot wants to update to
> `cloudflare/wrangler-action@ebbaa1584979971c8614a24965b4405ff95890e0 # v4.0.0`
However, this [commit ID](https://github.com/cloudflare/wrangler-action/commit/ebbaa1584979971c8614a24965b4405ff95890e0) gives a 404. Can anyone explain why this is, and what the correct SHA is for v4?
Contributor guide
Research direction
Start with the v4.0.0 release page and verify whether commit ebbaa1584979971c8614a24965b4405ff95890e0 is reachable. Compare the release tag with the SHA referenced by Dependabot, then document the correct SHA for v4.0.0 and explain the 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100