Repository navigation
fix(pkarr): bootstrap a brand-new Worker via cf deploy (#1829) - #3241
Conversation
cf workers versions create refuses to create a new Worker ('run
the deploy command first') — found by the first real deploy run.
deploy.mjs now checks whether the Worker exists: if not, the first
deploy goes through cf deploy with the same git-SHA tag/message
(creating version 1 and its deployment together); every later
deploy uses the versions flow. Gap recorded in the README and the
deployment-standard design doc.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 52 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Found by the first real deploy run:
cf workers versions createcannot create a brand-new Worker — it refuses and says to run the deploy command first.deploy.mjsnow checkscf workers get pkarr: when the Worker doesn't exist, the first deploy bootstraps viacf deploy --tag git-<sha12> --message ...(creates version 1 + its deployment together, same stamps); every later deploy uses the versions flow. Still cf-only — no wrangler fallback needed. Gap recorded in the package README and the deployment-standard design doc.Need help on this PR? Tag
@codesmith-botwith what you need.