Skip to content

chore: use the verified Vercel canonical origin - #3

Merged
jasonHzq merged 1 commit into
mainfrom
agent/pinhere-vercel-canonical
Aug 15, 2026
Merged

chore: use the verified Vercel canonical origin#3
jasonHzq merged 1 commit into
mainfrom
agent/pinhere-vercel-canonical

Conversation

@jasonHzq

Copy link
Copy Markdown
Contributor

Summary

  • pin the SDK/CLI to the publicly verified project-controlled Vercel production discovery URL
  • regenerate all generated sources from the exact 34-Endpoint / 36-Schema canonical PontxSpec
  • update default base URL, OAuth route assertions, provenance, notice, and release documentation

Verification

  • pnpm release:verify
  • release gate passed with deterministic generation, 8/8 unit tests, built-package E2E, ESM/CJS/types, package fresh-install, and Node 18/20/22
  • Agent Browser verified the Vercel discovery document and its SHA-256

No live Pinhere API call, credential, or mutation was used.

@jasonHzq
jasonHzq force-pushed the agent/pinhere-vercel-canonical branch from fa65373 to b4b246a Compare August 15, 2026 13:08
@jasonHzq
jasonHzq merged commit 024321a into main Aug 15, 2026
3 checks passed
@jasonHzq
jasonHzq deleted the agent/pinhere-vercel-canonical branch August 15, 2026 13:09
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