Flint CLI 0.6.0-beta.20261008022344

What's Changed

• Fix MCP sparse delivery updates with the current API contract by @athammer in #28
• Make CLI sign-up resumable and end in a test payment by @athammer in #29
• Document Linear findings policy and fix Windows signup test by @athammer in #30
• Refresh checkout contract and run release checks on staging by @athammer in #31
• Use protected staging credentials for sandbox checks by @athammer in #32

Full Changelog: cli/v0.6.0-beta.20261007073000...cli/v0.6.0-beta.20261008022344

Flint CLI 0.6.0-beta.20261007073000

This prerelease fixes MCP validation of sparse delivery configuration updates. It is published to npm under the next tag; latest remains 0.5.0.

These notes describe the API source named under API snapshot, not the behavior of a particular deployed Flint environment. See "Earlier API builds" for what changes when an API build doesn't include these changes.

npm install -g @flintpay/cli@0.6.0-beta.20261007073000

Fixed

The delivery-methods.update and delivery-rate-callbacks.update tools in flint mcp serve now accept a partial configuration. Send expected_version and only the configuration keys you want to change. On an API build that includes these changes, keys you leave out keep their current values.

Earlier releases, including 0.5.0 on latest and the earlier 0.6.0 betas, rejected such calls before sending them, with missing properties 'origin', 'pricing' for delivery methods or missing property 'url' for rate callbacks. flint delivery-methods update --input and flint delivery-rate-callbacks update --input don't check the body against these schemas in any release. They send it as written.

The tools now accept arguments like these and send the update to the API:

{"delivery_method_id": "dmet_01K1P6G4M7H2N8Q9R3S5T6V7WX", "expected_version": 4, "configuration": {"taxable": false}}
{"delivery_method_id": "dmet_01K1P6G4M7H2N8Q9R3S5T6V7WX", "expected_version": 4, "configuration": {"charge_tax_category": null}}
{"delivery_rate_callback_id": "dcb_01K1P6G4M7H2N8Q9R3S5T6V7WX", "expected_version": 2, "configuration": {"request_timeout_seconds": null}}

Null resets a key as its schema describes:

• Delivery methods: null on taxable or charge_tax_category returns it to the merchant's default. Null on eligibility, public_details, or buyer_instructions removes that setting, but a pickup method still needs public_details.pickup_mode. origin and pricing can't be null. Send [] to clear recipient_requirements or quote_input_fields.
• Rate callbacks: null on preview_enabled, request_timeout_seconds, maximum_request_bytes, maximum_response_bytes, or redirect_policy restores its default. url can't be null.

The tools still reject these calls without sending them: an empty configuration, a configuration without expected_version, null for a key that can't be null, a value of the wrong type, or an unknown key.

Earlier API builds

An API build that doesn't include one of these changes keeps its earlier behavior for it:

• It replaces the whole configuration on delivery method and rate callback updates. A partial configuration without origin and pricing, or without url for a rate callback, fails validation. One that includes them returns every key you left out, such as eligibility, to its create default. On such a build, include each key you want to keep in the update.
• It leaves configuration.taxable out of a delivery method response when the method follows the merchant's default taxability, and returns "" for configuration.charge_tax_category when the method follows the merchant's default category. flint prints the response as returned, but an MCP client that validates structuredContent against the tool's outputSchema can reject it.
• It still returns hosted_checkout on invoice checkout session results, and flint prints it as returned.

API snapshot

The embedded API description now comes from Flint API source 0a7128cd09609600301ffaad0579585683f1211e. The API version stays 2026-09-07. These changes appear in flint schema input, flint schema output, and MCP tool schemas:

• Delivery method and rate callback updates use the new DeliveryMethodConfigurationPatchInput and DeliveryRateCallbackConfigurationPatchInput schemas.
• The delivery method response schema requires configuration.taxable, which is null when the method follows the merchant's default, and allows null for configuration.charge_tax_category.
• Invoice checkout session results no longer list the deprecated hosted_checkout field. Use checkout_session.url and checkout_access.checkout_auth_token.
• Checkout customer prefill includes shipping_recipient_name.
• Descriptions are clarified for configuration on delivery profile, zone, and location set updates, for delivery_method_ids on checkout session creation, and for default_delivery_method_ids in checkout settings.
• Descriptions of buyer address, location, recipient, instruction, and tracking fields say they're omitted for a checkout session credential that doesn't act for the customer the buyer verified.

Command names, flags, API routes, required scopes, flint schema commands, and flint schema errors are unchanged. The snapshot doesn't change how commands print API responses.

Release workflow

Adds a read-only check that published container images match the reviewed build. The CLI itself is unchanged by this.

Full Changelog: cli/v0.6.0-beta.20261007033000...cli/v0.6.0-beta.20261007073000

Flint CLI 0.6.0-beta.20261007033000

What's Changed

• Add headless API commands and reproducible prerelease archives by @athammer in #22
• Read the checkout URL only from checkout_session.url by @athammer in #23
• Align beta CLI with buyer filters and current checkout contracts by @athammer in #24

Full Changelog: cli/v0.6.0-beta.20261006210100...cli/v0.6.0-beta.20261007033000

Flint CLI 0.6.0-beta.20261006210100

What's Changed

• Make CLI updates preserve working installations by @athammer in #20
• Refresh the API snapshot with the current error contract by @athammer in #21

Full Changelog: cli/v0.5.0...cli/v0.6.0-beta.20261006210100

Flint CLI 0.5.0

What's Changed

• Use server starter scopes for signup and sync CLI baseline by @athammer in #18
• Refresh public API commands and CLI discovery for 0.5.0 by @athammer in #19

Full Changelog: cli/v0.4.0...cli/v0.5.0

Flint CLI 0.4.0

What's Changed

• Improve login summaries and upgrade progress diagnostics by @athammer in #12
• Improve local CLI output and add update alias by @athammer in #13
• Clarify browser login availability messages by @athammer in #15
• Clarify browser login availability messages by @athammer in #16
• Add invoice late fee assessment and waiver commands by @athammer in #14
• Add CLI permission scope enforcement by @athammer in #17

Full Changelog: cli/v0.3.1...cli/v0.4.0

Flint CLI 0.3.1

No-op release to verify the flint upgrade path from 0.3.0.

Built from the same source commit as 0.3.0 (84f974f5446282681e7ed095775d4c886f446c65). Only the release version and distribution metadata change; there are no source or behavior changes.

From an installed 0.3.0 CLI on macOS or Linux:

flint version
flint upgrade
flint version

The final version should be 0.3.1. Windows users receive the update command to run after closing the CLI.

Flint CLI 0.3.0

What changed

• Authorize multiple merchant and environment contexts in one browser session, then choose a default with flint context list and flint context switch.
• Use --context ID for one command or pin a project context in .flint/config.json; use flint reauth to change authorized access.
• flint login reuses valid sessions and opens browser approval again after confirmed revocation or expiry. Session metadata identifies the computer and operating system in the dashboard.
• Run flint upgrade on macOS and Linux to update npm, Homebrew, or standalone installations. Standalone updates verify release checksums; Windows receives explicit update instructions.
• Preserve running commands' selected contexts, recover rotated tokens after temporary failures, and keep environment credentials compatible with saved browser contexts.

Compatibility

Multi-context commands require matching Flint backend support. Existing API keys and legacy single-context OAuth sessions remain supported. Selecting a live context requires explicit acknowledgement; subsequent commands use that selected environment, while destructive confirmations remain required. API keys and legacy sessions retain their per-command --live requirement.

Update

npm install -g @flintpay/cli@0.3.0
# or
brew update && brew upgrade flint-pay/tap/flint

flint upgrade is available starting with this release. Binary archives and checksums are attached below.

Full changes: cli/v0.2.0...cli/v0.3.0

Flint CLI 0.2.0

What's Changed

• Add OAuth browser login and clearer authentication diagnostics by @athammer in #10

Full Changelog: cli/v0.1.1...cli/v0.2.0

Flint CLI 0.1.1

Known issue: The sandbox API currently returns HTTP 503 WEBHOOK_STREAM_LIMITER_UNAVAILABLE, so flint listen may be unavailable until the backend Redis limiter recovers. The live sandbox check was explicitly waived for this release; all other release checks remain required.

What's Changed

• Harden CLI execution and verify release installations by @athammer in #1
• Retire feedback commands and harden CLI cancellation by @athammer in #2
• Add public repository agent guidance by @athammer in #3
• Check installations before release and retry npm propagation by @athammer in #4
• Report sandbox release failures safely and check before tagging by @athammer in #5
• Identify which sandbox release phase stalls by @athammer in #6
• Expose upstream status when diagnosing the sandbox stream by @athammer in #7
• Add AI agent metadata to support composer by @athammer in #8
• Allow an explicit sandbox waiver for one release by @athammer in #9

New Contributors

• @athammer made their first contribution in #1

Full Changelog: https://github.com/flint-pay/flint-cli/commits/cli/v0.1.1