Release 0.4.0 - #8
Merged
Merged
Conversation
Adds --idempotency-key to `anyapi run`, so a re-run can replay an earlier result instead of charging again. Supports an explicit key or `auto`, which derives a stable key from the SKU, canonicalized input, and UTC date. Co-Authored-By: Claude <noreply@anthropic.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
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.
Cuts 0.4.0 so the
--idempotency-keyflag from #7 actually reaches npm.anyapi-cliis still published at 0.3.3, so the feature is merged but not installable.Minor rather than patch: the flag is an additive feature.
What ships
anyapi run <sku> --input '<json>' --idempotency-key <key>sends a singleIdempotency-Keyheader, so a re-run replays the earlier result instead of charging again.--idempotency-key autoderives a stable key from the SKU, canonicalized input, and UTC date, and sends the canonicalized body so equivalent JSON formatting produces both the same key and byte-identical bytes.Omitting the flag sends no header, so intentional repeated runs are unaffected.
Verification
🤖 Generated with Claude Code