Skip to content

release: version packages - #99

Open
github-actions[bot] wants to merge 1 commit into
devfrom
changeset-release/dev
Open

release: version packages#99
github-actions[bot] wants to merge 1 commit into
devfrom
changeset-release/dev

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to dev, this PR will be updated.

Releases

@proofoftech/breakwater@0.13.0

Minor Changes

  • b85a872: Add a supported connector invocation boundary for trusted hosts and workflows. Direct calls now preserve Mastra validation and Breakwater grants without fabricated tool contexts, and validation failures expose no rejected values or schema messages.

  • fa0d11d: Add an optional content-policy boundary for agent signals. Breakwater exposes createContentPolicyGate(), a reusable opaque input-policy gate for host code outside Mastra's processor chain, and FlowSafe's thread signal routes accept a structural contentPolicy callback that inspects Mastra's canonical escaped XML before delivery, persistence, wake, or run start — covering direct ingestion, providers, schedules, and notification dispatch. Denial is terminal and evaluator failure stays recoverable on every lane; neither exposes policy names, reasons, content, or causes.

    Signal attributes whose keys are not XML names are now dropped when a signal is ingested, and a schedule whose stored target cannot be rendered settles a terminal discard receipt instead of failing every later tick with the same broken target.

    Provider deliveries now distinguish a terminal refusal from one the deployment could not decide: an undecided webhook is answered with 503 so the sender redelivers, and every delivery carries a dedupe key derived from the signed bytes and the subscription so a redelivery coalesces into a still-pending notification instead of duplicating it. Webhook and poll results report denied, failed, and deferred counts.

Patch Changes

  • 66c19f1: Clean generated output at the packaging boundary so deleted source modules cannot remain in published tarballs.
  • 5cbe01d: Align the package and documented Node.js runtime floor with the required @mastra/core 1.50.0 peer dependency.

@proofoftech/flowsafe@0.19.0

Minor Changes

  • fa0d11d: Add an optional content-policy boundary for agent signals. Breakwater exposes createContentPolicyGate(), a reusable opaque input-policy gate for host code outside Mastra's processor chain, and FlowSafe's thread signal routes accept a structural contentPolicy callback that inspects Mastra's canonical escaped XML before delivery, persistence, wake, or run start — covering direct ingestion, providers, schedules, and notification dispatch. Denial is terminal and evaluator failure stays recoverable on every lane; neither exposes policy names, reasons, content, or causes.

    Signal attributes whose keys are not XML names are now dropped when a signal is ingested, and a schedule whose stored target cannot be rendered settles a terminal discard receipt instead of failing every later tick with the same broken target.

    Provider deliveries now distinguish a terminal refusal from one the deployment could not decide: an undecided webhook is answered with 503 so the sender redelivers, and every delivery carries a dedupe key derived from the signed bytes and the subscription so a redelivery coalesces into a still-pending notification instead of duplicating it. Webhook and poll results report denied, failed, and deferred counts.

Patch Changes

  • da6a0aa: Export deployment identity headers from the protocol leaf so external candidates do not import the Durable Object runner barrel.
  • 66c19f1: Clean generated output at the packaging boundary so deleted source modules cannot remain in published tarballs.
  • 5cbe01d: Align the package and documented Node.js runtime floor with the required @mastra/core 1.50.0 peer dependency.

@proofoftech/fleet-control@0.3.4

Patch Changes

  • 66c19f1: Clean generated output at the packaging boundary so deleted source modules cannot remain in published tarballs.
  • Updated dependencies [fa0d11d]
  • Updated dependencies [da6a0aa]
  • Updated dependencies [66c19f1]
  • Updated dependencies [5cbe01d]
    • @proofoftech/flowsafe@0.19.0

anchorage-agent-starter@0.0.15

Patch Changes

  • b85a872: Add a supported connector invocation boundary for trusted hosts and workflows. Direct calls now preserve Mastra validation and Breakwater grants without fabricated tool contexts, and validation failures expose no rejected values or schema messages.
  • 5cbe01d: Align the package and documented Node.js runtime floor with the required @mastra/core 1.50.0 peer dependency.
  • Updated dependencies [b85a872]
  • Updated dependencies [fa0d11d]
  • Updated dependencies [da6a0aa]
  • Updated dependencies [66c19f1]
  • Updated dependencies [5cbe01d]
    • @proofoftech/breakwater@0.13.0
    • @proofoftech/flowsafe@0.19.0

showcase@0.0.21

Patch Changes

  • Updated dependencies [b85a872]
  • Updated dependencies [fa0d11d]
  • Updated dependencies [da6a0aa]
  • Updated dependencies [66c19f1]
  • Updated dependencies [5cbe01d]
    • @proofoftech/breakwater@0.13.0
    • @proofoftech/flowsafe@0.19.0

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
anchorage-showcase-single-tenant 670f3b3 Aug 20 2026, 02:29 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants