CI on push and PR#1
Merged
Merged
Conversation
Adds a GitHub Actions workflow so the release checks run before a tag, not after it. Also adds a public-API contract test that guards the barrel export surface consumers pin against.
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.
adds a github actions workflow that runs typecheck, vitest, and smoke on every push to master and every PR. before this the only real exercise of the release path happened after a tag was already pushed, which is a bad time to find out a change broke. i also threw in a small public-api contract test that checks the barrel in src/index.ts still exports the full documented surface at the right runtime kinds, since pixel-wand and atlas pin against a tag and a dropped export used to only show up when their install broke. writing that test actually caught that MIN_QUALITY_FLOOR is a nested record and not a scalar, so the assertion reflects reality now. nothing changed in the library itself, just the checks around it for now.