Release gkit v0.1.1 via public GitHub tarballs - #3
Merged
Conversation
…ublic Bun installation the supported distribution path Release v0.1.1 from the package version on main, keep npm publishing disabled, and verify both local artifacts and tokenless public installs. Raise the existing DataForSEO generator test budget to prevent the known GitHub runner timeout from blocking the release gate.
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.
Summary
gkitexclusively as verified npm tarballs attached to GitHub Releasesmain, with idempotent tag/asset handlingRelease contract
packages/gkit/package.json(0.1.1)gkit-0.1.1.tgz,gkit.tgz,SHA256SUMSLocal verification
bun install --frozen-lockfilebun run check-typesbun run test(139 tests)bun run evalbun run verify:packageactionlint .github/workflows/release.ymlSHA256SUMSverification