chore(release): version packages#28
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
faraa2m
pushed a commit
that referenced
this pull request
May 11, 2026
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
tokenometer@0.1.3
Patch Changes
#27
16daecbThanks @faraa2m! - Fixtokenometer --versionalways printing0.0.2regardless of theinstalled version. The CLI had a hardcoded
const VERSION = '0.0.2'left over from initial scaffolding. Now reads the version from the
package's own
package.jsonat runtime viaimport.meta.url.Also hardens the smoke-test job: switches from
npx --yes tokenometer@<v>(which hit
sh: 1: tokenometer: not foundflakiness on Linux runnerseven when the published bin had the execute bit) to
npm install --no-save+ directnode node_modules/tokenometer/dist/index.js.Adds a 6-attempt × 30s retry loop to absorb npm registry CDN
propagation lag right after publish.
Updated dependencies [
16daecb]:@tokenometer/core@0.1.3
Patch Changes
#27
16daecbThanks @faraa2m! - Fixtokenometer --versionalways printing0.0.2regardless of theinstalled version. The CLI had a hardcoded
const VERSION = '0.0.2'left over from initial scaffolding. Now reads the version from the
package's own
package.jsonat runtime viaimport.meta.url.Also hardens the smoke-test job: switches from
npx --yes tokenometer@<v>(which hit
sh: 1: tokenometer: not foundflakiness on Linux runnerseven when the published bin had the execute bit) to
npm install --no-save+ directnode node_modules/tokenometer/dist/index.js.Adds a 6-attempt × 30s retry loop to absorb npm registry CDN
propagation lag right after publish.
tokenometer-vscode@0.1.3
Patch Changes
16daecb]: