Repository navigation
release: scanner 0.3.20 and npm 1.1.13 - #113
Merged
Merged
Conversation
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
1 participant
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.
Prepare scanner v0.3.20 and npm tooltrust-mcp 1.1.13. Synchronize VERSION, npm binary pin and server.json, and add release notes covering Rust presence, empty discovery, OSV failures, security/toolchain updates and compatibility implications.
Add release verification to the project skill and CI: actual npm tarball allowlist/install, version alignment, MCP RPC calls, empty/OSV failures, cached-binary startup errors and cache reuse. Post-release smoke checks on Linux/macOS/Windows download the exact pinned assets and compare platform checksums. Replace the previous npm@latest smoke test, which could exercise an older release. The npm wrapper now supports an isolated cache and exits nonzero on launch failure.
Validation: baseline, discovery, OSV and release preflight drives all passed locally; workflow syntax passed actionlint. Cold-download checks run only after release assets exist and must pass before npm publication. Changes are reviewed before tagging; Homebrew checksum updates follow the tag archive.