Skip to content

fix(release): upload only the beta archive as the binary artifact - #1600

Merged
ScriptedAlchemy merged 1 commit into
masterfrom
fix/release-binary-artifact-path
Sep 18, 2026
Merged

ScriptedAlchemy merged 1 commit into
masterfrom
fix/release-binary-artifact-path

Conversation

@ScriptedAlchemy

Copy link
Copy Markdown
Owner

beta.43: all four targets built (first time since #707), then publish failed in Assemble retained and newly built prerelease assets:

unexpected release artifacts: tracedecay-beta-v0.1.0-beta.43-aarch64-linux.mcpb, …-aarch64-macos.mcpb, …-x86_64-linux.mcpb, …-x86_64-windows.mcpb

The beta build job's binary artifact was uploaded with path: tracedecay-beta-*, which also matches the .mcpb packaged in the same directory. publish copies new-binaries/tracedecay-beta-* into binaries/, so the MCPBs landed among the archives, and the coverage checker (correctly) refused foreign files. The old strict checker would have refused identically; no earlier tag ever reached this step. release.yml already uploads the exact archive name — the beta workflow now does the same.

Also pins the checker behaviour with a test: an MCPB in the binaries directory is foreign in both strict and --allow-missing-targets modes.

Evidence: scripts/test-check-release-artifacts.py, actionlint, tests/release_safety_test.sh pass. beta.43's tag workflow is frozen with the glob, so the first tag to ship is beta.44.

The beta build job uploaded its binary artifact with path tracedecay-beta-*,
which also matched the MCPB packaged beside it. publish then found MCPBs in
the binaries directory and refused the whole release; on beta.43 that was
the only thing between four green builds and shipped assets. The artifact
now names the exact archive, as the stable workflow already did.
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@changeset-bot

changeset-bot Bot commented Sep 18, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: ba2bf3c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@ScriptedAlchemy
ScriptedAlchemy merged commit 2f44a63 into master Sep 18, 2026
2 of 7 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