chore(release): 0.39.54 - #195
Merged
Merged
Conversation
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
PR Goal (one sentence)
Bump
@ipv9/tokentracker-clito 0.39.54 to release the vendor-rename normalizer + fuzzy-pricing disclosure fix (#193/#192, merged in #194) through npm.Scope
src/)dashboard/)Checklist
npm run ci:localpassespackage.json,package-lock.json)npm view @ipv9/tokentracker-cli version versions --jsonconfirmed0.39.53is latest/immutable; publish handled via.github/workflows/npm-publish.ymlon merge (falling back to the documented local-recovery path per release: migrate npm publication to Trusted Publishing OIDC #179 if CI OIDC still fails)Why
Same pattern as #189: a source-only fix needs a version bump for
npm-publish.ymlto actually publish (it only fires when the on-diskpackage.jsonversion is not yet on the registry).Regression Test Gate
Verification method
node --test test/npm-publish-workflow.test.js test/release-automation.test.js test/web-only-product-scope.test.js(peragent-os/standards/release/version-lockstep.md) → 24/24 passnpm run ci:localfull gate → dashboard 320/320, product suite 1059/1059, all validators passUncovered scope