You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since updating a record requires incrementing the sequence number, and because I didn't want to make you keep old revisions around on disk, the publish CLI command fetches the latest value and increments the sequence number if it exists.
At the moment, we're treating all publish errors as if they were "name not found" and falling back to creating a new "v0" revision. We should only do that if we get a 404 back from the API, and bail out on other errors.
The text was updated successfully, but these errors were encountered:
Since updating a record requires incrementing the sequence number, and because I didn't want to make you keep old revisions around on disk, the
publish
CLI command fetches the latest value and increments the sequence number if it exists.At the moment, we're treating all publish errors as if they were "name not found" and falling back to creating a new "v0" revision. We should only do that if we get a 404 back from the API, and bail out on other errors.
The text was updated successfully, but these errors were encountered: