Skip to content

Point the install snippet back at 1.4.4 - #38

Open
ladec-iadvize wants to merge 1 commit into
masterfrom
SYSTEM-2717-readme-back-to-144
Open

ladec-iadvize wants to merge 1 commit into
masterfrom
SYSTEM-2717-readme-back-to-144

Conversation

@ladec-iadvize

Copy link
Copy Markdown
Contributor

What

The README advertised boxed-tag/1.4.5/index.js, which does not exist — the URL answered 404. Puts it back to 1.4.4, and removes the changelog entry that went with the release that never happened.

Why 1.4.5 never existed

TOKEN_REPO_WRITE expired (April 2023)
   → "On merge" fails at actions/checkout
   → package.json is never bumped, still "1.4.4"
   → the tag created by hand points at that commit
   → the CI reads the version from package.json, not from $CIRCLE_TAG
   → it publishes to boxed-tag/1.4.4/ and succeeds
   → no 1.4.5 anywhere, while the README announces it

The upload job is green because it did exactly what it is asked: read package.json. That is the behaviour of the original script, kept as is by #37.

The v1.4.5 tag and GitHub release have been deleted; v1.4.4 is the latest again.

Verified

  • https://static.iadvize.com/boxed-tag/1.4.4/index.js → 200
  • the SRI hash in the README still matches that bundle byte for byte, checked against S3

Not fixed here

⚠ TOKEN_REPO_WRITE is still expired. Until it is renewed, no release can be cut on this repo: On merge will keep failing at checkout, package.json will never be bumped, and any tag created by hand will publish under the previous version — silently, with a green build.

Worth its own ticket. The lasting fix is a GitHub App rather than a personal token that expires with its owner.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FKQu2WBeddwCaYJ1wA69JD

No 1.4.5 was ever published. The `On merge` workflow failed at checkout —
TOKEN_REPO_WRITE dates from April 2023 and is no longer valid — so
package.json was never bumped. The tag created afterwards pointed at a commit
still declaring 1.4.4, and the CI published under that version, as the script
reads it from package.json rather than from the tag.

The README therefore advertised a version that does not exist, and the URL
answered 404. The tag and the GitHub release have been removed.

The SRI hash is unchanged and still matches the published 1.4.4 bundle,
verified against S3.

The changelog entry goes with it: nothing is released, so there is nothing to
note. The migration it described is a CI change with no effect on consumers.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FKQu2WBeddwCaYJ1wA69JD
@ladec-iadvize
ladec-iadvize requested a review from a team as a code owner September 21, 2026 12:40
@github-actions
github-actions Bot requested a deployment to npm September 21, 2026 12:41 Abandoned

This branch had an error being deployed

1 abandoned deployment
npm — 6ca374fb Deployed Sep 21, 2026 by github-actions[bot]
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.

2 participants