Skip to content

ci: pin softprops/action-gh-release to v2.6.2 (dodge v3.0.0 regression)#2385

Merged
bpamiri merged 1 commit intodevelopfrom
peter/pin-action-gh-release-v2.6.2
Apr 30, 2026
Merged

ci: pin softprops/action-gh-release to v2.6.2 (dodge v3.0.0 regression)#2385
bpamiri merged 1 commit intodevelopfrom
peter/pin-action-gh-release-v2.6.2

Conversation

@bpamiri
Copy link
Copy Markdown
Collaborator

@bpamiri bpamiri commented Apr 30, 2026

Summary

Pin softprops/action-gh-release from the floating @v3 tag to @v2.6.2 in three workflow steps. v3.0.0 (released 2026-04-12) introduced a deterministic regression that breaks every snapshot publish on develop.

The bug

After PR #2381 merged to develop, Wheels Snapshots run #1657 failed at Create Snapshot Pre-Release with:

##[error]The "chunk" argument must be of type string or an instance of
Buffer, TypedArray, or DataView. Received an instance of ArrayBuffer

The error fires three times in a row at exactly 30-second intervals, matching the Wandalen/wretry.action@v3 cadence configured in #2380 — proving the retry-wrap is working as designed but cannot help because the error is deterministic, not transient. Same error pattern visible on the previous run #1656 on commit f791d404 (which was the #2380 merge itself).

Root cause

softprops/action-gh-release@v3.0.0 shipped on 2026-04-12. The repo pinned @v3 (a floating major tag), so it auto-upgraded the moment v3.0.0 went live. The new release has a regression in how it streams asset uploads — passing an ArrayBuffer into Node's stream-write API where Node 20+ requires Buffer/TypedArray/DataView/string. Affects at minimum .zip.sha512 files.

v2.6.2 was cut the same day as v3.0.0 and is the last known-good release for this repo's upload pattern. overwrite_files: true (which #2380 relies on for retry idempotency) exists in v2.x as well.

Upstream issue: softprops/action-gh-release#790

Changes

  • .github/workflows/release.yml:325@v3@v2.6.2 (Create GitHub Release, main only)
  • .github/workflows/release.yml:367@v3@v2.6.2 (Create Snapshot Pre-Release, develop only)
  • .github/workflows/release-candidate.yml:244@v3@v2.6.2 (Create GitHub Prerelease)
  • Expanded the comment block above Create GitHub Release to capture the regression rationale so a future maintainer doesn't silently bump the major version back without checking that v3.x is healthy.

Test plan

  • CI: Lucee 7 + SQLite (LuCLI) passes (sanity).
  • CI: verify and Validate Commit Messages pass.
  • After merge to develop: next Wheels Snapshots run completes without the ArrayBuffer error and the snapshot release attaches all 18 assets cleanly.
  • Once upstream ships v3.0.1 with the chunk-type fix, follow up to re-pin to @v3 (or @v3.0.1 if we want belt-and-suspenders).

🤖 Generated with Claude Code

Three workflow lines were tracking the floating major tag @V3, which
auto-upgraded to softprops/action-gh-release@v3.0.0 the moment it
shipped on 2026-04-12. v3.0.0 introduced a deterministic regression
where `.zip.sha512` asset uploads fail with:

  ##[error]The "chunk" argument must be of type string or an instance
  of Buffer, TypedArray, or DataView. Received an instance of
  ArrayBuffer

The error fires inside the action's stream-write call, not the
network layer, so the Wandalen/wretry.action@v3 wrap added in #2380
runs all 3 attempts with the identical failure and exits 1. First
seen on SNAPSHOT+1656; same error on +1657. No upstream issue exists
yet at softprops/action-gh-release; we are early adopters of v3.0.0.

Pin to v2.6.2 in three locations:

  - release.yml: Create GitHub Release  (stable, main)
  - release.yml: Create Snapshot Pre-Release  (develop)
  - release-candidate.yml: Create GitHub Prerelease

v2.6.2 was cut the same day as v3.0.0 and is the last known-good
release for this repo's upload pattern. The `overwrite_files: true`
flag we depend on for retry idempotency exists in v2.x as well, so
no other changes are required.

Re-pin to @V3 once upstream ships a v3.0.1 with the chunk-type fix.
The expanded comment in release.yml captures the rationale so a
future maintainer doesn't quietly bump the major version back without
checking that v3.x is healthy first.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@bpamiri bpamiri merged commit f53f3ca into develop Apr 30, 2026
3 checks passed
@bpamiri bpamiri deleted the peter/pin-action-gh-release-v2.6.2 branch April 30, 2026 12:09
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