Repository navigation
Release v0.4.0 - #14
Merged
Merged
Conversation
Bump @basou/core, @basou/cli, @basou/sdk, and the (still unpublished) unscoped basou to 0.4.0. This is the first release that goes through the OIDC trusted-publisher pipeline introduced in PR #2: - npm publishes are signed with SLSA provenance v1 attestation - tarballs are republished as signed GitHub Release assets with cosign sign-blob bundles - no `NPM_TOKEN` secret is involved No code changes ride along with this bump - 0.3.1 -> 0.4.0 marks the supply-chain transition, not new functionality. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
First release through the new OIDC trusted-publisher pipeline (PR #2). 0.3.1 -> 0.4.0 is the supply-chain transition marker, not a feature bump.
What lands on tag push:
@basou/core,@basou/cli,@basou/sdkpublished to npm with SLSA provenance v1 attestationBasou v0.4.0GitHub Release with signed tarballs (cosign sign-blob bundles attached)NPM_TOKENsecret in the workflow at any pointThe unscoped
basoupackage is also bumped to keep the workspace in lockstep, but its npm name is still pending the support ticket, so it is not part of the publish-npm matrix.Test plan
quality.ymlCI is green on this branchv0.4.0is pushedverify,publish-npm(x3), andgithub-releasejobs all succeednpm view @basou/<core|cli|sdk>@0.4.0 --json | jq '.dist.attestations'returns a non-null provenance object