Add --force to sc deploy for an empty bump over an identical revision #38
No reviewers
Labels
No labels
⏳in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grey.ooo/someones.computer_agent!38
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/force-deploy-empty-bump-48d2a0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The bundle endpoint refuses an upload identical to the application's current
revision as a duplicate (409). --force asks for a new revision anyway, by
setting manifest.force — the platform now honours that to mint a fresh
Deployment at the next sequence number instead of refusing, carrying the same
digest as the revision it bumps (an empty bump).
Lands alongside the corresponding platform-side change
(BundleManifest/BundleIngestor honouring manifest.force) in
Grey.ooo/Someones.Computer.