Repository navigation
fix(pro): accept current Money signer and isolate test licences (8.5.6) - #980
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.
AnyMD currently rejects licences signed by its live Money environment because its offline policy trusts only the historical seller key. Add the current live signer without removing the old key and release 8.5.6.
Add explicit
anymd pro --test status|activateverification with separate test trust, token variable and file. It reportsPro (TEST)and cannot buy a production licence or unlock ordinary CLI/MCP Pro operations.Validation: all six Money public signers reread through scoped APIs; AnyMD licence tests pass (9 passed, 1 subprocess fixture ignored); version manifests agree. Signature, plan, product, expiry and existing licence terms remain enforced. The existing paid TEST token reports active through the real candidate CLI in explicit test mode; normal production mode and a tampered signature both report inactive. Tokens stayed in memory. Published-package verification follows release. No payment or merchant changes.