Repository navigation
release-doc-npm-trusted-publisher - #898
Merged
Merged
Conversation
Record in step 8a of docs/stackql_release_process.md how the npm trusted publisher configuration is created and why it must be created immediately before the dispatch: npm drops a new configuration that has not completed a successful publish within 2 days, which is what failed the first OIDC publish of 1.0.888 (404 on PUT right after the dry run). Also note the publish timing and the local npm cache when verifying, and add the npmjs.com row to the credentials table. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Fold the rest of the v1.0.888 run into docs/stackql_release_process.md: a pre-flight section (version.txt, build number, empty prerelease suffix, unexpired artifacts, credentials, release notes), the gh release create command, rerun guidance for mcp-packaging (publish targets skip existing versions; the Windows ARM64 smoke test has flaked), what the releases.stackql.io tag does and how to verify it, the Chocolatey package as step 7a (it lived only in the stackql-windows-installer README), the stamped pyproject.toml belonging to the pin PR, the pin branch base and the CI it triggers, and the Chocolatey rows in the surfaces and credentials tables. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
15 of 21 tasks
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.
Doc-only follow-up from the v1.0.888 release.
The first OIDC publish of
@stackql/mcp-server(PR #880 merged after 0.12.824, so 1.0.888 was the first real run) failed withnpm error 404 Not Found - PUT https://registry.npmjs.org/@stackql%2fmcp-serverright after the dry run succeeded. Cause: the trusted publisher configuration on npmjs.com had not been created immediately before the dispatch; npm discards a new configuration that has not completed a successful publish within 2 days. Creating it (organizationstackql, repositorystackql, workflowmcp-packaging.yml, environment blank,Allow npm publishticked,Allow npm dist-tagunticked) and rerunning the failed job published 1.0.888 with a SLSA provenance attestation, which makes the configuration permanent.Step 8a of
docs/stackql_release_process.mdpreviously only said the configuration "is permanent once validated by its first publish". It now records the exact fields, the 2-day rule, the failure signature, the recovery (recreate, rerun the failed job), and that the job publishes at the end of the run sonpm viewneeds--prefer-onlineif run too early. The credentials table gains the npmjs.com row.One file touched, under
docs/, so only Lint runs.🤖 Generated with Claude Code