fix(deployments): external build token generation issue#3070
Conversation
🦋 Changeset detectedLatest commit: b44bfb8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 28 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Caution Review failedThe pull request is closed. 📜 Recent review detailsConfiguration used: Repository UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
WalkthroughAdds explicit local-build handling end-to-end. The CLI gains a new Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
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. Comment |
967455f to
9f19f50
Compare
Fixes an issue introduced in #3024.
The behavior for local builds in older CLI versions relies on
externalBuildDatato be defined to distinguish from the self-hosting local build path, even though it doesn't actually use the token.