What this guide covers
This guide explains how changelog and release process updates stay aligned with the help center.
It includes the current landing-web-only exception for deploy validation and push checks, plus the folder-level AGENTS.md maintenance rule for major apps/, packages/, and scripts/ scopes.
Before you begin
- Confirm whether the change is landing-web-only or part of a broader release.
- Keep this article open while you update both the process docs and platform-operations help content.
Workflow overview
- Classify the release scope.
- Handle release-note implications.
- Run the matching deploy validation path.
- Sync the help-center record.
Step 1: Classify the release scope
Use the landing-web-only path only when the change is isolated to the marketing site and its direct content/config surfaces. If another app or shared package changed, use the normal repo release workflow.
Route checklist
- CHANGELOG/unreleased/release-notes.md
- CHANGELOG/vX.Y.Z/release-notes.md
- AGENTS.md
- CLAUDE.md
- DEPLOYMENT.md
- apps/landing-web/vercel.json
Step 2: Handle release-note implications
Landing-web updates stay excluded from public and unreleased customer-facing release notes. Still keep the normal changelog/version automation intact, but do not force a public release-note entry for landing-web-only work.
Step 3: Run the matching deploy validation path
For landing-web-only pushes:
- Run
pnpm exec prettier -c <changed-files...> - Run
pnpm --filter landing-web build - Confirm
apps/landing-web/vercel.jsonstill targets onlylanding-web - Push and let the landing-web Vercel project deploy through Git integration
Skip these for landing-web-only work:
pnpm deploy:preflightpnpm deploy:preflight:strictpnpm deploy:verify:vercel-aliasespnpm test:regression:remote
Use the broader release flow when the change is not landing-web-only.
Step 4: Sync the help-center record
Any AI-agent, changelog, or release-process policy update must update the platform-operations help articles in the same change set.
Update this article and the AI-agent maintenance article together, and keep the canonical task record under TODO/*.md plus TODO/PROGRESS.md aligned before implementation begins.
If the policy change touches a governed apps/, packages/, or scripts/ path, stage the applicable folder-level AGENTS.md files too so the pre-commit gate passes.
Validation checklist
- Changelog automation rules stayed intact.
- Landing-web-only work used
pnpm --filter landing-web buildonly. apps/landing-web/vercel.jsonstill uses app-scoped commands.- Applicable folder-level
AGENTS.mdfiles were staged for touched governed paths. - Platform-operations help content was updated in the same change set.
Troubleshooting
Do I need a public release-note entry for landing-web-only work?
No. Landing-web changes remain excluded from customer-facing release-note generation.
Should I still run deploy preflight for a landing-web-only push?
No. The isolated workflow is pnpm --filter landing-web build plus the landing-web Vercel config check.
Why did pre-commit fail on folder-level AGENTS files?
Changes under apps/, packages/, and scripts/ now require the matching folder-level AGENTS.md summaries to be staged too. Update the applicable summaries in the touched path, then recommit.
When do remote suites still apply?
Remote suites still apply for broader release work that includes other apps, APIs, or shared packages.
FAQ
Do landing-web-only pushes still use Vercel?
Yes. They still deploy through Vercel Git integration, but only the landing-web project should rebuild.
Does this change the changelog version bump rules?
No. Changelog/version automation still runs as normal.
What is the minimum release check for landing-web-only work?
A clean pnpm --filter landing-web build and a correct apps/landing-web/vercel.json.
Notes
This article documents the current repo policy for landing-web-only release handling.