Prepare scoped AgentFence v0.2.0 npm release - #2
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.
Prepares the public scoped @adulph3/agentfence@0.2.0 package while retaining the agentfence binary and existing detector behavior. Adds Node 22/24 runtime support and the six-job Ubuntu/macOS/Windows CI matrix, package metadata checks, and scoped npm/npx documentation. Reconciles the existing landing-page README without dropping its v0.1.0 platform and checksum guidance.\n\nLocal Linux Node 22.23.2 and 24.21.0 quality, security, package, and consumer gates passed. This PR does not itself publish to npm; hosted CI, the final merged-commit artifact, GitHub Release, and npm publication remain sequential release gates.