What
The force option's description now covers the case where a newer version was saved from inside the artifact page itself, not just another session publishing, warns never to force purely to get past a conflict, and notes the server may refuse a force over an in-page save.
Details
- The client-side stale-version check that could abort a publish with
stale_version_guardorstale_version_guard_seededwas removed from this path. - The read performed before publishing now passes session credentials.
Evidence
unless it refuses force over a version saved from inside the page
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundleforce
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Extend Claude with skills touched a line naming force after this was published.
If the install summary reports `Run /reload-plugins to activate.`, Claude Code then runs that reload for you. If the reload warns that your next message would re-read the conversation, run `/reload-plugins --force` to make the plugin's ski…skills see the edit
Confirmed since
Anthropic's documentation has since written up force, on Deploy managed settings.
| `allowedHttpHookUrls` | Claude Code enforces an empty managed [allowlist](/docs/en/settings-reference#allowedhttphookurls) until you fix the value, so an HTTP hook runs only if another settings file lists its URL. If only an individual e…managed-settings see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up force, on Deploy managed settings.