Repository navigation
Simplify capture publishing and add release instructions skill - #63
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
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.
Publishing capture 0.1.7 unexpectedly required a manual Chromium download because its selector regression tests were added to the default test suite. Publishing instructions also expanded the release workflow into unnecessary setup details.
Move browser selector tests to a dedicated PR/main CI job while preserving the standard tests used by the release script. Add a discoverable
publish-captureskill, linked from AGENTS.md, that directs agents to give one copy-pasteable release command, verify the intended version, and leave authentication to npm. Simplify the package release instructions.Validation: 117 default tests passed with PLAYWRIGHT_BROWSERS_PATH pointing to a nonexistent browser installation; 15 browser tests passed separately; production build passed. The new skill passes skill-creator validation.