ci: Forward-port manual SHA deploy escape hatch from #1502 - #1504
Conversation
Ports the Deploy www (manual SHA) workflow_dispatch and CONTRIBUTING docs from merged dev PR #1502 so v1 maintainers can redeploy any commit to arkenv-dev / arkenv-v1 / production stable URLs. Co-authored-by: Yam Borodetsky <hi@yam.codes>
|
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — forward-port of the manual SHA deploy escape hatch from dev PR #1502, adding a workflow_dispatch workflow and documenting it for maintainers.
- Add
deploy-www-manual.ymlworkflow — maintainer-triggeredworkflow_dispatchthat deploys any commit SHA toarkenv-dev.vercel.app,arkenv-v1.vercel.app, or productionarkenv.js.orgvia Vercel CLI with git metadata. - Document the escape hatch in
CONTRIBUTING.md— expands the Preview deployments section to describe the Actions/Vercel CLI branch-domain behavior and the new manual SHA deploy option.
DeepSeek Pro (free via Pullfrog for OSS) (GPT Sol not used — the program covers this model; add its provider key to run your pick) | 𝕏

Summary
Forward-ports merged dev PR #1502 onto
v1.workflow_dispatch) so maintainers can deploy any commit toarkenv-dev.vercel.app,arkenv-v1.vercel.app, or productionarkenv.js.orgwithout moving the branch.devfrom Safely remove native Vercel Git noise after Actions owns all deploys #1460) indocs/CONTRIBUTING.md.No package code changes; no changeset.
Source
dev:4111bda7Test plan
dev(paths/secrets identical; no v1 package-layout remap needed)v1SHA →arkenv-v1.vercel.app