Skip to content

chore(release): record CLI bootstrap and retirement - #213

Merged
Pepps233 merged 1 commit into
feat/publication-trustfrom
chore/cli-bootstrap-evidence
Sep 13, 2026
Merged

Pepps233 merged 1 commit into
feat/publication-trustfrom
chore/cli-bootstrap-evidence

Conversation

@Pepps233

@Pepps233 Pepps233 commented Sep 13, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Record the public CLI 0.2.1 bootstrap and retirement of the original eleven 0.2.0 package versions.

Reasoning

The owner approved publishing the exact locally validated replacement after GitHub blocked final CLI validation because of account billing or an Actions spending limit.
The evidence distinguishes accepted registry operations, verified public bytes, and remaining live checks.

Changes

  • Retain the published source identity, tarball checksums, registry versions/tags, and npm publisher configuration.
  • Record anonymous npm/Bun installation checks and retirement verification.
  • Document the owner-approved GitHub validation exception and the credential scope checks that require the workflow on main.

Testing

  • Published bytes match the approved SHA-256 and SHA-512 identities.
  • Fresh anonymous npm/Bun installs passed CLI startup, exports, installed-file hashes, native modules, WASM, and HTML export, with cleanup confirmed.
  • The shared cloud release contract passed.
  • Local source checks and the isolated test suite passed for the implementation in feat(release): configure private-source npm publication trust #212; final GitHub validation was explicitly waived by the owner.
  • Production probing still returned no announced release (404), healthy readiness (200), and anonymous auth rejection (401).

npm rejected latest tag removal with HTTP 400 after 2FA approval, so both bootstrap and latest currently resolve to 0.2.1.
The no-latest acceptance condition and the live credential scope checks on main remain open.

- Retain verified CLI publication and retirement evidence with the owner-approved validation exception and unresolved registry tag condition.
@Pepps233 Pepps233 added the enhancement New feature or request label Sep 13, 2026
@Pepps233 Pepps233 self-assigned this Sep 13, 2026
@Pepps233
Pepps233 added this pull request to stack #214 September 13, 2026 17:20
@Pepps233
Pepps233 merged commit 672d559 into main Sep 13, 2026
1 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant