Repository navigation
fix(security): harden CLI and automate npm releases (0.1.1) - #2
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…y paths - Strip C1 control characters and bidi overrides from terminal output and escape them in --json output so untrusted ticket content cannot drive or spoof the terminal. - Stop gitdog.json discovery at the repository root or home directory so a file in a shared parent directory cannot select the project. - Record the owner PID in the session lock and recover locks left by dead processes, claiming them atomically. - Refuse keys create --out paths that Git would track, before issuing a key. - Read the development deployment and report directory for test:dev from the environment instead of committing them. Co-Authored-By: Claude Opus 5.5 <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
CLI hardening, automated npm releases, and the 0.1.1 mascot/version bump.
Hardening
--jsonoutput so the JSON value is unchanged.gitdog.jsonlookup stops at the Git repository root or the home directory.keys create --outresolves the real path and refuses a location Git would track, failing closed when Git cannot verify it; checked before a key is issued.GITDOG_DEV_DEPLOYMENT/GITDOG_TEST_REPORT_DIR.Release automation
release.ymlruns on a published GitHub Release taggedvVERSION: validates tag/version/commit (must be onmain), tests, packs once, smoke-tests the archive, then publishes that archive through npm trusted publishing with provenance from thenpmenvironment (tagsv*only). Existing versions are never republished; the published tarball and provenance are verified against the tag and commit.Verification
bun run typecheck,bun run lint,bun run test(94 pass),bun audit --production,npm pack --dry-run; CI green.🤖 Generated with Claude Code