feat: add Vercel production deployment workflow by amikofalvy · Pull Request #1679 · inkeep/agents

amikofalvy · 2026-02-03T10:45:05Z

Summary

Add GitHub Actions workflow to deploy to Vercel production only when a GitHub release is published
Enables separation of staging (main branch) and production (release-based) deployments

Deployment Strategy

Trigger	Environment	URL
Push to PR/branch	Preview	`<branch>-<project>.vercel.app`
Push to `main`	Staging (persistent)	`main-<project>.vercel.app`
Release published	Production	Production domain

Setup Required

1. Add GitHub Secrets

Secret	How to Obtain
`VERCEL_TOKEN`	Vercel Dashboard → Settings → Tokens → Create
`VERCEL_ORG_ID`	Run `vercel link` locally, check `.vercel/project.json`
`VERCEL_PROJECT_ID`	Same as above

2. Vercel Dashboard Configuration

Project Settings → Git → Production Branch: Change from main to _disabled_

This prevents main from auto-deploying to production while keeping preview deployments working.

How It Works

PRs and branches get automatic preview deployments (unchanged)
Main branch gets persistent staging deployment (now a "preview" not "production")
When you publish a GitHub release (from the existing changesets workflow), it triggers production deployment

Test plan

Add required secrets to GitHub
Configure Vercel Production Branch setting
Merge a PR to main → verify staging deploys but not production
Publish a GitHub release → verify production deploys

changeset-bot · 2026-02-03T10:45:10Z

⚠️ No Changeset found

Latest commit: 9db47c9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

vercel · 2026-02-03T10:45:10Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
agents-api	Ready	Preview, Comment	Feb 4, 2026 8:23pm
agents-docs	Ready	Preview, Comment	Feb 4, 2026 8:23pm
agents-manage-ui	Ready	Preview, Comment	Feb 4, 2026 8:23pm

Add GitHub Actions workflow to deploy to Vercel production only when a GitHub release is published. This integrates with the existing changesets release flow.

Deploy to preview URL first, wait for Vercel deployment checks to pass, then promote to production. This ensures API health before going live.

- Document Production Branch configuration (set to '_disabled_') - Document GitHub Actions workflow for release-triggered deployments - Document required secrets (VERCEL_TOKEN, VERCEL_ORG_ID, VERCEL_PROJECT_ID) - Document optional staging domain configuration - Add deployment flow diagram and troubleshooting section - Add secrets documentation comments to workflow file Completes US-001, US-002, US-003, US-004 from vercel-deployment-strategy PRD. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

claude · 2026-02-04T19:46:15Z

Claude finished @amikofalvy's task in 3m 37s —— View job

PR Review Summary

3 Key Findings | Risk: Low

🟠🔶⚠️ Major (2) 🟠🔶⚠️

🟠 1) .github/workflows/vercel-production.yml:18-20 Missing explicit permissions declaration

files: .github/workflows/vercel-production.yml

Issue: The workflow doesn't declare explicit permissions for the job. The existing release.yml explicitly sets permissions (contents: write, pull-requests: write, etc.) which is a security best practice.

Why: Without explicit permissions, the workflow uses default permissions which may be more permissive than necessary. Explicit permissions help prevent accidental access to resources the workflow doesn't need, following the principle of least privilege.

Fix: Add an explicit permissions block:

permissions:
  contents: read  # Only needs read access to checkout the release tag

🟠 2) .github/workflows/vercel-production.yml Monorepo single-project limitation

scope: Architectural consideration

Issue: The workflow uses a single VERCEL_PROJECT_ID secret, but this is a monorepo with multiple Vercel projects (agents-api, agents-manage-ui, agents-docs). The current workflow will only deploy one project.

Why: Per the Vercel bot comment, there are three projects in this monorepo. The PRD and documentation mention "production deployment" but don't clarify whether this workflow is intended to deploy all three projects or just one. If it's meant for all projects, the workflow needs to be expanded. If it's just for one, this should be documented clearly.

Fix: Consider one of:

If deploying all projects: Use a matrix strategy with project-specific secrets (VERCEL_PROJECT_ID_API, VERCEL_PROJECT_ID_UI, VERCEL_PROJECT_ID_DOCS)
If deploying one project: Document which project this workflow deploys and why others are excluded
Clarify in docs: Update the documentation to specify the scope

📌 Point-fix Edits (1)

🟠 .github/workflows/vercel-production.yml:43-46 Shell command error handling

💡 APPROVE WITH SUGGESTIONS

Summary: This is a well-structured PR that adds a clean deployment strategy for separating staging and production. The documentation is comprehensive and follows existing patterns. The main suggestions are: (1) add explicit permissions to the workflow for security hygiene, and (2) clarify the monorepo deployment scope—whether this workflow covers all Vercel projects or just one specific project.

Other Findings (5)

Location	Issue	Reason Excluded
`vercel-production.yml:44`	`DEPLOYMENT_URL` capture could fail silently if `vercel deploy` fails	LOW confidence—Vercel CLI exits non-zero on failure, so shell will fail anyway
`vercel-production.yml:53`	`vercel inspect --wait` has no explicit timeout	LOW severity—Vercel CLI has internal timeouts and this matches existing patterns
`agents-docs/vercel.mdx:536-580`	Duplicates workflow YAML already in the actual file	Intentional for documentation purposes—inline code examples are standard practice
`spec/prd-vercel-deployment-strategy.md:113`	PRD shows `--prod` flag but actual workflow removed it for preview-then-promote pattern	Not an issue—workflow correctly uses preview-first approach; PRD just outdated
`vercel.mdx:649`	`pnpm changeset` example doesn't mention using `pnpm bump` per CLAUDE.md	Documentation shows generic changeset usage which is valid; `pnpm bump` is a convenience alias

.github/workflows/vercel-production.yml

…ranch Replace _disabled_ approach (which Vercel doesn't support) with a never-deploy orphan branch. Update staging domain examples to use api-staging.agents.yourdomain.com pattern.

claude · 2026-02-04T20:12:48Z

Claude finished @amikofalvy's task in 4m 9s —— View job

PR Review Summary

3 Key Findings | Risk: Low

🟠🔶⚠️ Major (2) 🟠🔶⚠️

🟠 1) .github/workflows/vercel-production.yml Missing explicit permissions declaration

files: .github/workflows/vercel-production.yml

Issue: The workflow doesn't declare explicit permissions for the job. The existing release.yml explicitly sets permissions (contents: write, pull-requests: write, etc.) which is a security best practice.

Why: Without explicit permissions, the workflow uses default permissions which may be more permissive than necessary. Explicit permissions help prevent accidental access to resources the workflow doesn't need, following the principle of least privilege.

Fix: Add an explicit permissions block at the job level:

jobs:
  deploy:
    name: Deploy to Production
    runs-on: ubuntu-latest
    permissions:
      contents: read  # Only needs read access to checkout the release tag
    steps:
      # ...

🟠 2) .github/workflows/vercel-production.yml Monorepo single-project limitation

scope: Architectural consideration

Issue: The workflow uses a single VERCEL_PROJECT_ID secret, but this is a monorepo with three Vercel projects (agents-api, agents-manage-ui, agents-docs). The current workflow will only deploy one project to production.

Why: Based on my exploration of the codebase:

All three projects have separate Vercel configurations
The existing deployment-health-check.yml explicitly filters for agents-api only
The documentation in vercel.mdx mentions deploying multiple projects but the workflow doesn't support this

This appears to be an intentional v1 implementation focused on agents-api, but this should be explicitly documented to avoid confusion.

Fix: Consider one of:

Document the scope: Add a comment at the top of the workflow clarifying this is for agents-api only, with a note about future expansion
If deploying all projects: Use a matrix strategy with project-specific secrets (VERCEL_PROJECT_ID_API, VERCEL_PROJECT_ID_UI, VERCEL_PROJECT_ID_DOCS)
Update the docs: Clarify in vercel.mdx which specific project this workflow deploys

📌 Point-fix Edits (1)

⏳ .github/workflows/vercel-production.yml:43-46 Add error handling for deployment URL capture - Previous suggestion still pending

💡 APPROVE WITH SUGGESTIONS

Summary: This is a well-structured PR that adds a clean deployment strategy for separating staging and production. The "deploy to preview, wait for checks, then promote" pattern is solid. The documentation is comprehensive and the never-deploy branch approach is clearer than the original _disabled_ suggestion. Main suggestions are: (1) add explicit permissions for security hygiene, (2) clarify the monorepo deployment scope, and (3) address the pending inline suggestion for error handling robustness.

Other Findings (4)

Location	Issue	Reason Excluded
`vercel-production.yml:53`	`vercel inspect --wait` has no explicit timeout	LOW severity—Vercel CLI has internal timeouts and this matches the existing deployment-health-check pattern
`vercel.mdx:536-580`	Duplicates workflow YAML already in the actual file	Intentional—inline code examples in docs are standard practice for discoverability
`prd-vercel-deployment-strategy.md:113`	PRD shows `--prod` flag on deploy but workflow uses preview-first	Not an issue—PRD was the initial design doc, workflow correctly uses improved preview-then-promote pattern
`vercel-production.yml`	No concurrency handling	LOW severity—releases are infrequent and sequential; unlikely to have concurrent production deploys

Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com>

claude · 2026-02-04T20:17:44Z

Claude encountered an error —— View job

PR Review In Progress

Analyze PR context and changes
Explore codebase for relevant patterns
Dispatch domain-specific reviewers
Aggregate and filter findings
Post final review summary

Revert vercel.mdx to main branch version and remove the PRD file.

claude · 2026-02-04T20:18:52Z

PR Review In Progress

Analyze PR context and changes
Explore codebase for relevant patterns
Dispatch domain-specific reviewers
Aggregate and filter findings
Post final review summary

View job run

Update production workflow to deploy both projects in parallel using a matrix strategy. Each project uses its own secret for the Vercel project ID.

claude · 2026-02-04T20:21:58Z

Claude finished @amikofalvy's task in 2m 13s —— View job

PR Review Summary

2 Key Findings | Risk: Low

🟠🔶⚠️ Major (1) 🟠🔶⚠️

🟠 1) .github/workflows/vercel-production.yml Missing explicit permissions declaration

files: .github/workflows/vercel-production.yml

Issue: The workflow doesn't declare explicit permissions for the job. Other workflows in this repo (release.yml lines 14-19, deployment-health-check.yml lines 13-15) follow the best practice of declaring explicit permissions.

Why: Without explicit permissions, the workflow uses the default GITHUB_TOKEN permissions which may be more permissive than necessary. Following the principle of least privilege is a security best practice that prevents accidental access to resources the workflow doesn't need. This is especially important for workflows that handle deployment secrets.

Fix: Add an explicit permissions block at the job level:

jobs:
  deploy:
    name: Deploy ${{ matrix.project.name }}
    runs-on: ubuntu-latest
    permissions:
      contents: read  # Only needs read access to checkout the release tag
    strategy:
      # ... rest of job

📌 Point-fix Edits (1)

✅ .github/workflows/vercel-production.yml:53-60 Previous error handling suggestion has been implemented - nice work!

ℹ️ Clarification Request

agents-docs excluded from deployment matrix - The Vercel bot shows 3 projects (agents-api, agents-manage-ui, agents-docs), but only 2 are in the matrix. If this is intentional (e.g., docs deploy differently or don't need release-based deployment), consider adding a comment in the workflow to explain the exclusion:

        # Note: agents-docs deploys via standard Vercel Git integration (not release-based)
        project:
          - name: agents-api
            project_id_secret: VERCEL_API_PROJECT_ID
          - name: agents-manage-ui
            project_id_secret: VERCEL_MANAGE_UI_PROJECT_ID

💡 APPROVE WITH SUGGESTIONS

Summary: Well-structured PR that cleanly separates staging and production deployments using a "preview → verify → promote" pattern. The previous error handling suggestion has been nicely implemented. The main remaining ask is adding explicit permissions to follow repo conventions and security best practices. The agents-docs exclusion is likely fine but worth a clarifying comment.

Other Findings (3)

Location	Issue	Reason Excluded
`vercel-production.yml`	No concurrency handling	LOW severity - releases are infrequent and sequential; unlikely to have concurrent production deploys
`vercel-production.yml:65`	`vercel inspect --wait` has no explicit timeout	LOW severity - Vercel CLI has internal timeouts and this matches existing patterns
`vercel-production.yml:40`	Dynamic secret reference `secrets[matrix.project.project_id_secret]`	Valid pattern - GitHub Actions supports this syntax for matrix-based secret access

@claude

* feat: add Vercel production deployment workflow Add GitHub Actions workflow to deploy to Vercel production only when a GitHub release is published. This integrates with the existing changesets release flow. * feat: add deployment checks before promoting to production Deploy to preview URL first, wait for Vercel deployment checks to pass, then promote to production. This ensures API health before going live. * PRD for vercel deployment strategy * docs: add Vercel staging/production deployment strategy documentation - Document Production Branch configuration (set to '_disabled_') - Document GitHub Actions workflow for release-triggered deployments - Document required secrets (VERCEL_TOKEN, VERCEL_ORG_ID, VERCEL_PROJECT_ID) - Document optional staging domain configuration - Add deployment flow diagram and troubleshooting section - Add secrets documentation comments to workflow file Completes US-001, US-002, US-003, US-004 from vercel-deployment-strategy PRD. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: update Vercel staging/production strategy to use never-deploy branch Replace _disabled_ approach (which Vercel doesn't support) with a never-deploy orphan branch. Update staging domain examples to use api-staging.agents.yourdomain.com pattern. * Apply suggestion from @claude[bot] Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com> * revert: remove Vercel deployment docs changes and PRD Revert vercel.mdx to main branch version and remove the PRD file. * feat: deploy both agents-api and agents-manage-ui to Vercel Update production workflow to deploy both projects in parallel using a matrix strategy. Each project uses its own secret for the Vercel project ID. --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com> Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com>

@v1

…chat or if custom headers are invalid (#1699) * upd * upd * upd * upd * upd * upd * upd * typecheck is ok now * wip custom headers dialog * upddd * upddd * upddd * brand color * upd * validate on mount * polish * fix lint * format * review fixes * feat(pr-review): add clickable links to inline comments in review summary (#1714) - Add `url` field to GraphQL queries for review threads and PR comments - Add Phase 5.4 to capture inline comment URLs after posting - Update Point-Fix Edits section to include clickable links - Update Pending Recommendations to use URLs from pr-context skill - Add `gh api` to allowed tools for fetching comment URLs - Add secure debug artifact uploads for Claude review runs * Revert "fix(agents-core): remove refine call in resource id schema (#1689)" (#1691) This reverts commit 938ffb8. * fix: pin claude-code-action to SDK 0.2.25 to avoid AJV crash (#1716) SDK versions 0.2.27+ have a bug causing AJV validation crashes before any API calls are made. This affects all PR reviews. Tracking issue: anthropics/claude-code-action#892 Related: #852, #880, #804 Will revert to @v1 when the upstream issue is resolved. * bump zod to latest 4.3.6 and fix `.omit() cannot be used on object schemas containing refinements` error (#1712) * Revert "fix(agents-core): remove refine call in resource id schema (#1689)" This reverts commit 938ffb8. * Revert "fix(agents-core): remove refine call in resource id schema (#1689)" This reverts commit 938ffb8. * bump * upd * remove zod from pnpm overrides * update zod peerdependencies too, and we have error reproducible locally * minimal fix * rm unrelated changes * rm unrelated changes * rm unrelated changes * rm unrelated changes * rm unrelated changes * rm unrelated changes * rm unrelated changes * rm unrelated changes * Version Packages (#1701) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * feat: add Vercel production deployment workflow (#1679) * feat: add Vercel production deployment workflow Add GitHub Actions workflow to deploy to Vercel production only when a GitHub release is published. This integrates with the existing changesets release flow. * feat: add deployment checks before promoting to production Deploy to preview URL first, wait for Vercel deployment checks to pass, then promote to production. This ensures API health before going live. * PRD for vercel deployment strategy * docs: add Vercel staging/production deployment strategy documentation - Document Production Branch configuration (set to '_disabled_') - Document GitHub Actions workflow for release-triggered deployments - Document required secrets (VERCEL_TOKEN, VERCEL_ORG_ID, VERCEL_PROJECT_ID) - Document optional staging domain configuration - Add deployment flow diagram and troubleshooting section - Add secrets documentation comments to workflow file Completes US-001, US-002, US-003, US-004 from vercel-deployment-strategy PRD. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: update Vercel staging/production strategy to use never-deploy branch Replace _disabled_ approach (which Vercel doesn't support) with a never-deploy orphan branch. Update staging domain examples to use api-staging.agents.yourdomain.com pattern. * Apply suggestion from @claude[bot] Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com> * revert: remove Vercel deployment docs changes and PRD Revert vercel.mdx to main branch version and remove the PRD file. * feat: deploy both agents-api and agents-manage-ui to Vercel Update production workflow to deploy both projects in parallel using a matrix strategy. Each project uses its own secret for the Vercel project ID. --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com> Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com> * remove cursor specific rules in favor or skills and agents.md (#1717) * chore: trigger release for all packages (#1718) No-op patch bumps to trigger a new release. * Version Packages (#1719) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * updating release action (#1720) * fix: add --scope flag to Vercel CLI commands in production workflow (#1721) The vercel inspect and promote commands were failing with authorization errors because VERCEL_ORG_ID as an environment variable isn't used by the CLI for scope resolution - it requires the --scope flag explicitly. * fix: use staged production deployments in Vercel workflow (#1722) - Deploy with --prod --skip-domain to create staged production builds - This ensures production env vars are used and avoids rebuild on promote - Add --yes flag to auto-confirm prompts in CI environment - Fixes issue where promoting preview deployments triggered interactive prompt * fix: add --archive=tgz to prevent CLI hanging during deploy (#1724) Large file uploads can cause the Vercel CLI to hang. The --archive=tgz flag compresses files before upload which resolves this issue. * fix: use repository variables instead of secrets for non-sensitive values (#1723) Move TURBO_TEAM and VERCEL_ORG_ID from secrets to vars to prevent GitHub Actions from masking these values in logs. Secret values are automatically masked, which was causing "inkeep" to appear as "***" throughout CI logs. * fix: simplify Vercel workflow to use direct production deploy (#1725) - Remove --skip-domain flag which was causing CLI to hang - Remove separate promote step (--prod auto-assigns domains) - Simpler, more reliable workflow * fix: use secrets for VERCEL_ORG_ID (#1726) * apply review * pnpm i * polish * format * Rename convert-json-schema-to-zod.ts to convert-json-schema-to-zod.test.ts * add tests * wip tests * wip tests * wip tests * upd * upd * upd * upd * polish error names * upd * move to __tests__ * format * chore: add changeset for custom headers validation feature Co-authored-by: Dimitri POSTOLOV <undefined@users.noreply.github.com> --------- Co-authored-by: Nick Gomez <122398915+nick-inkeep@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Andrew Mikofalvy <5668128+amikofalvy@users.noreply.github.com> Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com> Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com> Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com> Co-authored-by: Dimitri POSTOLOV <undefined@users.noreply.github.com>

@v1

…fromJSONSchema()` method (#1735) * upd * upd * upd * upd * upd * upd * upd * typecheck is ok now * wip custom headers dialog * upddd * upddd * upddd * brand color * upd * validate on mount * polish * fix lint * format * review fixes * feat(pr-review): add clickable links to inline comments in review summary (#1714) - Add `url` field to GraphQL queries for review threads and PR comments - Add Phase 5.4 to capture inline comment URLs after posting - Update Point-Fix Edits section to include clickable links - Update Pending Recommendations to use URLs from pr-context skill - Add `gh api` to allowed tools for fetching comment URLs - Add secure debug artifact uploads for Claude review runs * Revert "fix(agents-core): remove refine call in resource id schema (#1689)" (#1691) This reverts commit 938ffb8. * fix: pin claude-code-action to SDK 0.2.25 to avoid AJV crash (#1716) SDK versions 0.2.27+ have a bug causing AJV validation crashes before any API calls are made. This affects all PR reviews. Tracking issue: anthropics/claude-code-action#892 Related: #852, #880, #804 Will revert to @v1 when the upstream issue is resolved. * bump zod to latest 4.3.6 and fix `.omit() cannot be used on object schemas containing refinements` error (#1712) * Revert "fix(agents-core): remove refine call in resource id schema (#1689)" This reverts commit 938ffb8. * Revert "fix(agents-core): remove refine call in resource id schema (#1689)" This reverts commit 938ffb8. * bump * upd * remove zod from pnpm overrides * update zod peerdependencies too, and we have error reproducible locally * minimal fix * rm unrelated changes * rm unrelated changes * rm unrelated changes * rm unrelated changes * rm unrelated changes * rm unrelated changes * rm unrelated changes * rm unrelated changes * Version Packages (#1701) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * feat: add Vercel production deployment workflow (#1679) * feat: add Vercel production deployment workflow Add GitHub Actions workflow to deploy to Vercel production only when a GitHub release is published. This integrates with the existing changesets release flow. * feat: add deployment checks before promoting to production Deploy to preview URL first, wait for Vercel deployment checks to pass, then promote to production. This ensures API health before going live. * PRD for vercel deployment strategy * docs: add Vercel staging/production deployment strategy documentation - Document Production Branch configuration (set to '_disabled_') - Document GitHub Actions workflow for release-triggered deployments - Document required secrets (VERCEL_TOKEN, VERCEL_ORG_ID, VERCEL_PROJECT_ID) - Document optional staging domain configuration - Add deployment flow diagram and troubleshooting section - Add secrets documentation comments to workflow file Completes US-001, US-002, US-003, US-004 from vercel-deployment-strategy PRD. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: update Vercel staging/production strategy to use never-deploy branch Replace _disabled_ approach (which Vercel doesn't support) with a never-deploy orphan branch. Update staging domain examples to use api-staging.agents.yourdomain.com pattern. * Apply suggestion from @claude[bot] Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com> * revert: remove Vercel deployment docs changes and PRD Revert vercel.mdx to main branch version and remove the PRD file. * feat: deploy both agents-api and agents-manage-ui to Vercel Update production workflow to deploy both projects in parallel using a matrix strategy. Each project uses its own secret for the Vercel project ID. --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com> Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com> * remove cursor specific rules in favor or skills and agents.md (#1717) * chore: trigger release for all packages (#1718) No-op patch bumps to trigger a new release. * Version Packages (#1719) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * updating release action (#1720) * fix: add --scope flag to Vercel CLI commands in production workflow (#1721) The vercel inspect and promote commands were failing with authorization errors because VERCEL_ORG_ID as an environment variable isn't used by the CLI for scope resolution - it requires the --scope flag explicitly. * fix: use staged production deployments in Vercel workflow (#1722) - Deploy with --prod --skip-domain to create staged production builds - This ensures production env vars are used and avoids rebuild on promote - Add --yes flag to auto-confirm prompts in CI environment - Fixes issue where promoting preview deployments triggered interactive prompt * fix: add --archive=tgz to prevent CLI hanging during deploy (#1724) Large file uploads can cause the Vercel CLI to hang. The --archive=tgz flag compresses files before upload which resolves this issue. * fix: use repository variables instead of secrets for non-sensitive values (#1723) Move TURBO_TEAM and VERCEL_ORG_ID from secrets to vars to prevent GitHub Actions from masking these values in logs. Secret values are automatically masked, which was causing "inkeep" to appear as "***" throughout CI logs. * fix: simplify Vercel workflow to use direct production deploy (#1725) - Remove --skip-domain flag which was causing CLI to hang - Remove separate promote step (--prod auto-assigns domains) - Simpler, more reliable workflow * fix: use secrets for VERCEL_ORG_ID (#1726) * apply review * pnpm i * polish * format * Rename convert-json-schema-to-zod.ts to convert-json-schema-to-zod.test.ts * add tests * wip tests * wip tests * wip tests * upd * upd * upd * upd * polish error names * upd * move to __tests__ * rm jsonSchemaToZod * rm jsonSchemaToZod * rm jsonSchemaToZod * rm jsonSchemaToZod * format * chore: add changeset for custom headers validation feature Co-authored-by: Dimitri POSTOLOV <undefined@users.noreply.github.com> * chore: add changeset for jsonSchemaToZod removal Replace custom implementation with Zod's native z.fromJSONSchema() method Co-authored-by: Dimitri POSTOLOV <dimaMachina@users.noreply.github.com> * fix lint * Update validation.test.ts --------- Co-authored-by: Nick Gomez <122398915+nick-inkeep@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Andrew Mikofalvy <5668128+amikofalvy@users.noreply.github.com> Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com> Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com> Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com> Co-authored-by: Dimitri POSTOLOV <undefined@users.noreply.github.com> Co-authored-by: Dimitri POSTOLOV <dimaMachina@users.noreply.github.com>

vercel bot deployed to Preview – agents-api February 3, 2026 10:47 View deployment

vercel bot deployed to Preview – agents-manage-ui February 3, 2026 10:47 View deployment

vercel bot deployed to Preview – agents-docs February 3, 2026 10:47 View deployment

vercel bot deployed to Preview – agents-api February 3, 2026 10:52 View deployment

vercel bot deployed to Preview – agents-manage-ui February 3, 2026 10:52 View deployment

vercel bot deployed to Preview – agents-docs February 3, 2026 10:53 View deployment

vercel bot deployed to Preview – agents-api February 3, 2026 19:22 View deployment

vercel bot deployed to Preview – agents-manage-ui February 3, 2026 19:22 View deployment

vercel bot deployed to Preview – agents-docs February 3, 2026 19:22 View deployment

amikofalvy and others added 4 commits February 4, 2026 11:45

feat: add Vercel production deployment workflow

9290fec

Add GitHub Actions workflow to deploy to Vercel production only when a GitHub release is published. This integrates with the existing changesets release flow.

feat: add deployment checks before promoting to production

1049978

Deploy to preview URL first, wait for Vercel deployment checks to pass, then promote to production. This ensures API health before going live.

PRD for vercel deployment strategy

b3d77bb

nick-inkeep force-pushed the feat/vercel-deployment-strategy branch from f251d8c to 4232be1 Compare February 4, 2026 19:45

inkeep deleted a comment from claude bot Feb 4, 2026

vercel bot deployed to Preview – agents-api February 4, 2026 19:47 View deployment

vercel bot deployed to Preview – agents-manage-ui February 4, 2026 19:47 View deployment

vercel bot deployed to Preview – agents-docs February 4, 2026 19:48 View deployment

claude bot reviewed Feb 4, 2026

View reviewed changes

.github/workflows/vercel-production.yml Show resolved Hide resolved

docs: update Vercel staging/production strategy to use never-deploy b…

3b09efd

…ranch Replace _disabled_ approach (which Vercel doesn't support) with a never-deploy orphan branch. Update staging domain examples to use api-staging.agents.yourdomain.com pattern.

vercel bot deployed to Preview – agents-api February 4, 2026 20:14 View deployment

vercel bot deployed to Preview – agents-manage-ui February 4, 2026 20:14 View deployment

vercel bot deployed to Preview – agents-docs February 4, 2026 20:14 View deployment

Apply suggestion from @claude[bot]

c2c00b9

Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com>

revert: remove Vercel deployment docs changes and PRD

1f7c136

Revert vercel.mdx to main branch version and remove the PRD file.

vercel bot deployed to Preview – agents-api February 4, 2026 20:19 View deployment

vercel bot deployed to Preview – agents-manage-ui February 4, 2026 20:20 View deployment

vercel bot deployed to Preview – agents-docs February 4, 2026 20:20 View deployment

feat: deploy both agents-api and agents-manage-ui to Vercel

9db47c9

Update production workflow to deploy both projects in parallel using a matrix strategy. Each project uses its own secret for the Vercel project ID.

vercel bot deployed to Preview – agents-manage-ui February 4, 2026 20:23 View deployment

vercel bot deployed to Preview – agents-docs February 4, 2026 20:23 View deployment

vercel bot deployed to Preview – agents-api February 4, 2026 20:23 View deployment

amikofalvy merged commit 90ea4b3 into main Feb 4, 2026
9 checks passed

amikofalvy deleted the feat/vercel-deployment-strategy branch February 4, 2026 22:46

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: add Vercel production deployment workflow#1679

feat: add Vercel production deployment workflow#1679
amikofalvy merged 8 commits intomainfrom
feat/vercel-deployment-strategy

amikofalvy commented Feb 3, 2026

Uh oh!

changeset-bot bot commented Feb 3, 2026 •

edited

Loading

Uh oh!

vercel bot commented Feb 3, 2026 •

edited

Loading

Uh oh!

claude bot commented Feb 4, 2026 •

edited

Loading

💡 APPROVE WITH SUGGESTIONS

Uh oh!

Uh oh!

claude bot commented Feb 4, 2026 •

edited

Loading

💡 APPROVE WITH SUGGESTIONS

Uh oh!

claude bot commented Feb 4, 2026 •

edited

Loading

Uh oh!

claude bot commented Feb 4, 2026 •

edited

Loading

Uh oh!

claude bot commented Feb 4, 2026 •

edited

Loading

💡 APPROVE WITH SUGGESTIONS

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Comments

Conversation

amikofalvy commented Feb 3, 2026

Summary

Deployment Strategy

Setup Required

1. Add GitHub Secrets

2. Vercel Dashboard Configuration

How It Works

Test plan

Uh oh!

changeset-bot bot commented Feb 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ No Changeset found

Uh oh!

vercel bot commented Feb 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

claude bot commented Feb 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Review Summary

🟠🔶⚠️ Major (2) 🟠🔶⚠️

📌 Point-fix Edits (1)

💡 APPROVE WITH SUGGESTIONS

Uh oh!

Uh oh!

claude bot commented Feb 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Review Summary

🟠🔶⚠️ Major (2) 🟠🔶⚠️

📌 Point-fix Edits (1)

💡 APPROVE WITH SUGGESTIONS

Uh oh!

claude bot commented Feb 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Review In Progress

Uh oh!

claude bot commented Feb 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Review In Progress

Uh oh!

claude bot commented Feb 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Review Summary

🟠🔶⚠️ Major (1) 🟠🔶⚠️

📌 Point-fix Edits (1)

ℹ️ Clarification Request

💡 APPROVE WITH SUGGESTIONS

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Comments

changeset-bot bot commented Feb 3, 2026 •

edited

Loading

vercel bot commented Feb 3, 2026 •

edited

Loading

claude bot commented Feb 4, 2026 •

edited

Loading

claude bot commented Feb 4, 2026 •

edited

Loading

claude bot commented Feb 4, 2026 •

edited

Loading

claude bot commented Feb 4, 2026 •

edited

Loading

claude bot commented Feb 4, 2026 •

edited

Loading