Flowmark v0.12.0

Overview

Flowmark v0.12.0 is the application release from PR #139 (staging → main, merge commit 2df5e864e7abca67f6ad60195ff2a8f317c23a25). This release follows v0.11.0.

Highlights

Agent access and OAuth

• Delegated reader project binding — delegated reads are tied to grant projects in persistence.
• Session consent, connections, and lifecycle — session consent APIs, connection management, and revoke flows; password reset invalidates delegated connections where applicable.
• OAuth routing and grant family — issuer OAuth path forwarding without widening ordinary auth redirects; code exchange bound to a provider grant family that carries no project; regression coverage so ordinary auth stays closed when a provider token has no project grant.
• Protocol contract — ADR 0008, frozen agent-access protocol contract, Effect-based decoders, and MCP/OAuth dependency ADR updates.

Dashboard and Studio

• Connect — agent and manual setup paths, four-client manual agent access guide, Studio navbar shortcut to Connect.
• Explore / handoffs — insights and issues context in Explore; safe run investigation preview and manual handoffs for issues and insights.
• Reliability — Studio responsive and route compatibility fixes; proxy transport failures mapped to retry guidance; well-known proxy import fix for production dashboard build.

Data and reads

• Bounded reads — bounded run investigation summaries, event paging, nested run evidence, workflow and declaration discovery reads; parity tests for analytics stability.

Examples and docs

• Booking setup demo (memory-first).
• Implementation status mirror and delegated reader header documentation.

Tooling and maintenance

• SDK — public packages bumped to 0.2.1 in workspace (see changelog/commits).
• CI / tests — integration coverage for delegated grant isolation and a follow-up fix for the AgentAccessConsentRejected import in that test (PR #140), included in this release line.

Database

This range includes new committed migrations under packages/db/migrations/ (0018–0021 in tree at this tag). Hosted environments should receive these through your Migrate and deploy pipeline and verified rollout process.

Upgrade notes

• Review OAuth/agent-access behavior if you integrate custom clients or proxies.
• After deploy, confirm auth, delegated connections, and dashboard routes on your Production domains per your checklist.

Full diff

Compare: v0.11.0...v0.12.0

Flowmark v0.11.0

Flowmark v0.11.0 delivers the Studio product experience, Product 1.0 landing updates, dashboard investigation guidance, and a shared SDK workflow lifecycle refactor.

Web

• Product 1.0 landing and messaging, Platform visualization, and Studio emphasis.
• Landing atmosphere and SDK experience refinements.

Dashboard / Studio

• Studio workspace with guided setup and Explore.
• Unified search and shared product shell.
• Inspect runs from Studio without leaving Explore.
• Investigation tabs and evidence handoffs.

SDK

• Share advanced workflow lifecycle logic across client paths.

Reliability

• CI fixes for integration interrupt cleanup on Linux and Studio CLI startup timeouts.

No schema changes or new required environment variables in this release.

Validation includes format, lint, typecheck, unit and disposable-PostgreSQL integration checks, Staging rollout, and Production Migrate and deploy at merge SHA 6aba3ac (workflow run).

Release: #111.

Flowmark v0.10.0

Flowmark v0.10.0 adds optional email verification in account settings.

• See whether your email is verified, request or resend a confirmation link, and refresh the status.
• Get clear feedback for expired or invalid links, rate limits, and session lookup failures.
• Verification status comes from your session; requesting a message does not mark your email verified.
• Confirmation links preserve the currently signed-in account and return to the same app's account settings.

Email verification remains optional for normal signup and sign-in. The secure password recovery flow from v0.9.0 remains available. Changing an account's email address remains disabled.

No schema changes, new dependencies, infrastructure changes, or new environment variables are required.

Validation includes format, lint, typecheck, unit and disposable-PostgreSQL integration checks, desktop/mobile UI checks, and Staging and Production deployment checks. A real inbox journey remains a manual acceptance step; deployment checks do not claim inbox delivery.

Changes: #95. Release: #96.

Flowmark v0.9.0

Adds secure password recovery while keeping normal signup and sign-in free of mandatory email verification.

What's changed

• Request a reset link, choose a new password and return to the same account.
• Use hashed, single-use reset links with a 30-minute lifetime; revoke previous sessions after recovery and send a security notice.
• Handle expired/used links, throttling and uncertain network results with safe recovery guidance.
• Deliver branded mail through Resend with separate Staging/Production settings and platform-managed task lifetime.
• Protect callback redirects, caching and referrers. Password changes require the current password and sign out other sessions.
• Refresh the repository README around product value and links to detailed guides.

Verification and rollout

Deployed to all four Production applications at commit b85cfa9fa269a9ec6a0da7185fd882c04b9006cf. Required CI, PostgreSQL integration, migration-history checks and deployment/domain checks passed. Feature validation included 57 database and 109 server tests plus desktop/mobile UI checks. Production health, anonymous auth proxy and recovery-page checks passed.

No schema migration or new infrastructure setting is required. Normal account access does not require prior email verification. Real inbox and new-password sign-in acceptance remains a manual Production check; it is not claimed as completed.

Production rollout · Release PR #94 · Full changelog

v0.8.0

Flowmark v0.8.0

Dashboard-focused release: global search, Insights and Issues, action toasts, and a cleaner feature architecture. Adds the @flowmark/email foundation with Resend support and Pulumi bindings for hosted email configuration.

Highlights

• Dashboard: command-palette search across projects, workflows, and runs; new Insights and Issues pages; toast feedback for settings and project actions; feature modules colocated with clearer server/browser boundaries.
• Reporting API: project search and period-report queries backing dashboard search and analytics views.
• Email: branded HTML templates, test capture adapter, and Resend delivery adapter in @flowmark/email.
• Infrastructure: Pulumi resources for Resend domain/API key and Vercel email environment variables.
• Developer experience: full local stack command (pnpm dev:stack), Drizzle Studio in the stack workflow, and expanded dashboard architecture docs.

Notes

• No database schema migrations since v0.7.0.
• Apply and verify Production email infrastructure before relying on transactional email in hosted environments.

Flowmark v0.7.0

What's changed

• Consolidated local PostgreSQL development on checkout-scoped Docker Compose, with explicit readiness checks, service ownership and guarded database targets.
• Added disposable PostgreSQL integration testing with complete-report verification for local development and CI.
• Moved authentication and local account provisioning into the internal @flowmark/auth workspace package.
• Added focused product startup and native backend library watchers.
• Updated development documentation and infrastructure configuration ownership guidance.

Upgrade notes

Local development now uses the managed Docker Compose workflow. Existing local configuration and data are preserved; consult the local development guide when adapting older setups. No database schema migrations or SDK npm release are included.

Full changelog: v0.6.3...v0.7.0

Release PR: #83

Flowmark v0.6.3

Flowmark v0.6.3 restores the provider's normal authentication boundaries and adds durable, shared abuse limits. It also improves internal API read paths and project metadata correctness.

Authentication and resource limits

• Hosted email/password sign-in uses Better Auth's normal security behavior. Registration delegates to its protected HTTP handler, with generic failures and safe provider diagnostics.
• Atomic PostgreSQL limits cover auth attempts across instances and bound project/key creation. Storage failures remain unavailable responses rather than an in-memory allow fallback; retry guidance is preserved.
• A separate server-only secret signs client-source metadata across the dashboard/API auth hop. Staging and Production have distinct values managed through Pulumi; existing auth-signing and database secrets were preserved.
• Password-reset session revocation is explicitly configured for the future recovery flow. Verification/recovery email delivery remains disabled until its separate implementation is ready.

API correctness and maintenance

• Return the stored project creation timestamp.
• Authorize workflow reads through a shared reader and load workflow summaries without fetching the full snapshot.
• Consolidate persistence-error translation, enforce read-model contracts, clarify result-declaration types and remove unused internal API paths.

Deployment and verification

The controlled Production rollout passed on 335d3f64f75fdcc184932a236db1e399543e891b:

• Migration history verified at 18/18 after applying additive 0017_auth_rate_limits, before API deployment.
• All four Production apps are READY on that exact revision and their canonical domains.
• All 42 approved functional checks passed, covering registration, direct/proxied sign-in, secure cookies, trusted-source handling, two-owner isolation, ingestion and key/session revocation. Synthetic test keys and sessions were revoked afterward.
• Required CI/PostgreSQL checks passed. Full Pulumi preview and refresh-preview are clean with 29 unchanged Production state resources.
• Public landing/docs/sign-in/sign-up pages and the signed-out dashboard redirect passed their final HTTP checks.

Production workflow · Release PR #73 · Authentication policy

Upgrade notes

Apply migration 0017_auth_rate_limits before deploying dependent API code. Configure the matching FLOWMARK_AUTH_PROXY_SECRET on API and dashboard separately for each hosted environment; it is not the Better Auth signing secret. The guarded local fixture now uses local@flowmark.test; never seed a hosted database.

No SDK/npm release or auth package extraction is included. Automatic feature Preview deployments remain paused.

Full changes: v0.6.2...v0.6.3

Flowmark v0.6.2

Flowmark v0.6.2 improves credential safety and completes Pulumi management of the reference deployment.

Safer key management

• Emergency write-key rotation now replaces the selected key and revokes the old key in one database transaction. Failed or concurrent attempts cannot leave hidden active replacements.
• Rotation rejects revoked, missing, wrong-kind and other-project keys without creating a new credential.
• Dashboard confirmations identify the project and key before rotation or revocation. Key lists distinguish loading, errors and empty states; clipboard failures are reported.
• New projects receive one write key with the correct key ID. Existing read keys remain valid.
• Documentation explains immediate emergency rotation, planned create → update application → revoke replacement, and recovery if the replacement secret is lost. Project names and reported environments are labels, not authorization boundaries.

Infrastructure management

• Complete protected Pulumi adoption of persistent Neon resources, Vercel projects, seven custom-domain assignments and all 21 application environment bindings.
• Keep sensitive values encrypted, environment scopes explicit and all 45 adopted cloud resources protected against deletion. Application deployment, database migration and CI secrets retain their existing owners.
• Feature Preview deployments remain paused; Staging remains the active nonproduction rollout.

Upgrade notes

No database schema migration, SDK version change or npm publication is included. Existing credentials continue working unless explicitly rotated or revoked. Emergency rotation invalidates the selected old key immediately; a request already authorized may still finish. Use create → update application → revoke when an overlap is needed.

Verification

The Production rollout passed format/lint/type/unit checks, PostgreSQL integration tests, database-history verification and deployment checks. API, dashboard, docs and web are READY at bfd65c85e28803129609244bce6655fe7d08b165, with their canonical domains verified. Health, signed-out sessions and public pages passed; unauthenticated ingestion is rejected. All 21 app environment bindings are unchanged. Hosted customer credentials were not rotated as a release test.

Changes: #58, #59. Release PR: #60. Full comparison: v0.6.1...v0.6.2

Flowmark v0.6.1

Documentation and examples

• Align the public SDK reference with SDK 0.2.0, including workflow results, intermediate reporting, attempt metadata, continuation and expectations.
• Correct API and onboarding documentation: registration creates an account, while the first project and write key are created in onboarding or Settings. Document the existing query and mutation surface accurately.
• Add typechecked illustrative SDK examples for batch progress, retries, correlation, continuation, background jobs, webhooks and route handlers.

Infrastructure

• Add a separate Pulumi TypeScript project and environment ownership catalog for the existing Vercel/Neon reference deployment.
• Record protected adoption of the non-production Neon branches and environment bindings, plus the four shared Vercel projects. Remaining production resource classes stay separate.
• Resolve post-import Passport input normalization so standard Pulumi refresh and preview are clean.
• Exclude infrastructure tooling and stack configuration from app uploads. Automatic feature previews remain paused; Staging uses the controlled rollout.

Compatibility

This patch changes documentation, examples and infrastructure tooling. It adds no application runtime source or database migration definitions. SDK npm publication remains separate from the application release.

Full comparison: v0.6.0...v0.6.1

Release commit: 9f67474. All four Production deployments were verified Ready at this commit after the controlled rollout.

Flowmark v0.6.0

Draft only. Do not publish until Production is verified at the main merge commit. Before publishing, change this release's target from the pre-merge candidate 32ba28359721dcfc58a97514c8295b403cbbf721 to that exact verified SHA.

Business references and outcomes

• Find historical runs by explicitly enabled business references and categories.
• Follow declared business outcomes over time, with totals, reason distributions, weighted ratios and the runs behind each figure. Missing reports stay unknown rather than zero or success.
• Compare a run with an explicit earlier peer population, and distinguish repeated short operations from one long occurrence.

Runs, delivery and retries

• The first terminal event accepted by persistence closes the run. A later conflicting terminal report returns HTTP 409 and leaves the recorded result unchanged.
• Opt-in latest-progress delivery keeps the newest unsent progress snapshot under queue pressure. Bounded admission and local delivery health do not turn telemetry loss into a business failure.
• Operation callbacks can report a safe error code, message and retryable flag while the application keeps its original exception.
• Record application-owned attempt numbers and link a new execution to an earlier retry, without Flowmark deciding retry policy.

Durable expectations

• Applications can declare expected confirmations with flow.expect(), then resolve or cancel them explicitly.
• Deadlines are stored and evaluated on read, including after process restarts and after the run has completed. Overdue investigation is separate from execution status. Flowmark does not schedule or retry the application's work.

Compact historical facts

• Run summaries, search, outcome windows, technical metrics and operation comparison can read compact facts maintained in the same transaction as each accepted event.
• Migrations 0015 and 0016 install that projection without scanning existing history. Unbackfilled runs still read raw events. Hosted backfill is a separate operation and is not part of this release.
• Migrations 0011–0014 add search configuration, attempt metadata and expectation storage. They are additive. Rolling the application back does not undo the schema.