Add --force to sc deploy for an empty bump over an identical revision #38

Merged
geusebio merged 1 commit from chore/force-deploy-empty-bump-48d2a0 into main 2026-08-24 17:07:19 +00:00
Owner

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.

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.
Add --force to sc deploy for an empty bump over an identical revision
All checks were successful
CI / build (pull_request) Successful in 1m55s
d63f4b6dd4
The bundle endpoint refuses an upload identical to the application's current
revision as a duplicate. --force asks for a new revision anyway by setting
manifest.force, which the platform now honours to mint a fresh Deployment
instead of answering 409.
Sign in to join this conversation.
No reviewers
No labels
in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grey.ooo/someones.computer_agent!38
No description provided.