Repository navigation
Prepare preview.25 for current Omni prices and five MCP tools - #7
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.
Preview.24's immutable package still contains the historical news price and four-tool MCP union, while reviewed source now binds news at 0.010 USDC and includes premarket at 0.100 USDC. Prepare preview.25 so those contracts can be installed through a new versioned GitHub archive.
Bump package/lock metadata, update active install references, document nine HTTP recipe templates versus five paid MCP tools, and preserve historical release notes/tags. The release notes explicitly distinguish this prepared source from publication and funded settlement. Rebuilt generated dist already matches the reviewed source, so no generated diff is necessary.
Validation on Dell with Node 22.23.2:
No paid calls, signing, runtime changes, tag creation, or publication. After merge, publish only the exact CI-qualified release commit as v0.1.0-preview.25, then verify the immutable archive from a clean consumer.