Skip to content

[skills] Say that vercel curl keeps the bypass secret it creates - #380

Draft
Melkeydev wants to merge 1 commit into
mainfrom
melkey/curl-bypass-ready-z4m
Draft

Melkeydev wants to merge 1 commit into
mainfrom
melkey/curl-bypass-ready-z4m

Conversation

@Melkeydev

Copy link
Copy Markdown
Collaborator

Summary

The vercel-cli skill says that vercel curl handles Deployment Protection. This PR adds what an agent must know about the bypass secret that vercel curl can create.

Why

If a project has no Protection Bypass for Automation secret, vercel curl creates one. The secret stays on the project until someone revokes it. A new secret can take a few seconds to work, so the CLI waits for it, and it shows a warning if the secret is not active yet. Without this note, an agent does not know that a secret persists, how to revoke it, or what to do after the warning.

Changes

  • skills/vercel-cli/references/monitoring-and-debugging.md: add one paragraph under "vercel curl — Access Preview Deployments".
  • skills/vercel-cli/upstream/references/monitoring-and-debugging.md: the same paragraph, to keep the two copies the same.

Verification

  • bun run build:from-skills:check: 0 stale.
  • bun run validate: all checks pass.
  • bun test: 1304 pass, 0 fail.

Docs/knowledge: this PR is the knowledge update.

🤖 Generated with Claude Code

The vercel-cli skill says that `vercel curl` handles Deployment
Protection. Add that the Protection Bypass for Automation secret it
creates stays on the project until someone revokes it, how to revoke
it, and that a new secret can take a few seconds to work.

Co-Authored-By: Claude <noreply@anthropic.com>

This branch has not been deployed

No deployments
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.

1 participant