Skip to content

Upload one release archive per platform - #7

Merged
ddehilster merged 1 commit into
mainfrom
fix/release-asset-collision
Oct 14, 2026
Merged

ddehilster merged 1 commit into
mainfrom
fix/release-asset-collision

Conversation

@ddehilster

Copy link
Copy Markdown
Member

The GitHub release step of run 38599499844 failed with `Not Found - update-a-release-asset`.

Cause: each platform prebuild is a file named `bindings.node`, and release assets have no folders. `files: prebuilds/**/*` uploaded three files with the same name at the same time, and `overwrite_files` let each upload delete another's asset. Earlier releases (v1.3.59, v1.3.60) didn't fail, but each kept only one platform's `bindings.node`.

Fix: pack each `prebuilds//` into `nlpplus--.tar.gz` and upload only those archives.

Not affected: npm installs. The prebuilds ship inside the npm package, and `scripts/install.js` never downloads from releases. `nlpplus@1.3.61` published normally.

v1.3.61 release: repaired by hand with the three archives, built from that run's saved build files.

Testing: the packing was tested by hand on v1.3.61's files. The workflow step itself first runs on the next release.

🤖 Generated with Claude Code

Every platform prebuild is named bindings.node and release assets are
flat, so uploading prebuilds/**/* raced three same-named uploads:
overwrite_files deleted each other's asset (404 on v1.3.61) and earlier
releases silently kept only one platform. Tar each platform dir into
nlpplus-<tag>-<platform>.tar.gz and upload those instead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ddehilster
ddehilster merged commit aea7dd2 into main Oct 14, 2026
5 checks passed
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