Repository navigation
Release 0.6.0 - #12
Merged
Merged
Conversation
Minor, not patch: the bundled scanner-core 0.7.0 reads file types the CLI could not see before — container builds, devcontainers, compose files, nested READMEs and agent command/skill markdown — and the 2026.11.18.001 rules match them. Capped scans also now spend their file budget on build and install scripts ahead of tests and vendored artifacts. All four version sites move together: package.json, both fields in server.json (the release guard checks those three), and the VERSION constant in src/cli.ts, which the guard does not check — `--version` would otherwise have reported 0.5.1 from a 0.6.0 package. Verified: typecheck, 59 tests, build, and `--version` / `--help` on the built CLI.
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.
Minor, not patch: the bundled scanner-core 0.7.0 reads file types the CLI could not see before — container builds, devcontainers, compose files, nested READMEs and agent command/skill markdown — and the
2026.11.18.001rules match them. Capped scans also spend their file budget on build and install scripts ahead of tests and vendored artifacts.Four version sites, not three
release.ymlfails the release unless the tag matchespackage.json .version,server.json .versionandserver.json .packages[0].version. There is a fourth:const VERSIONinsrc/cli.ts, which the guard does not check — so a 0.6.0 package would have published withflagrix --versionstill reporting0.5.1. It has been bumped by hand in every release commit since 0.1.0; this one keeps that up.Worth hardening separately, either by deriving it from
package.jsonat build time or by adding it to the guard.Verification
0.6.0matches all three JSON fieldsnpm run typecheck, 59 tests,npm run build--versionnow prints0.6.0,--helpexits cleanAfter merge
Tag
v0.6.0on main to triggerrelease.yml: npm publish with provenance, then the MCP registry publish ofserver.json.