Repository navigation
Document returning to a previous release by deployment_id, and retrying an activation - #696
Merged
Merged
Conversation
…id, and retrying an activation Companion to HarperFast/harper#2897 (#2315 step 5). A deploy now keeps the release it replaces under the deployment id that deployed it, so deploy_component { deployment_id } returns to it; activating the id that is already live succeeds without a swap, so a retry converges. Kept releases share deployment.stagingRetention.maxCount with staged builds, and each is a full installed copy. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
…ve retry restarts every worker From review: "published by that deployment", a capitalized retry list, Oxford commas, and a simpler statement of when retention runs. Also states what harper#2897 now does on an already-live retry with `restart`: it restarts every worker, isolated applications' included. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dawsontoth
marked this pull request as ready for review
September 29, 2026 14:05
cb1kenobi
reviewed
Sep 29, 2026
cb1kenobi
left a comment
cb1kenobi
left a comment
Member
There was a problem hiding this comment.
The changed docs at this commit match the stated deploy behavior: kept releases are activated by deployment_id, already-live activation is retryable without a swap, and retention plus disk use are described the same way in the operations reference, config option, and 5.3 note. Prior inline wording notes are already addressed. No remaining blocking defect on the changed lines.
—
Reviewed bf5a265
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents #2315 step 5, from HarperFast/harper#2897: a deploy now keeps the release it replaces under the deployment id that deployed it, so
deploy_component { project, deployment_id }returns to it, and activating the id that is already live succeeds without a swap, so a partial activation can be retried with the same id.reference/operations-api/operations.md: thedeployment_idparameter row, the staging caveats (a retry of the live id is safe; kept releases count against retention; a deployment id names one release while the node holds it), the 404 wording, and two new sections — Going back to a previous release and Retrying an activation.reference/configuration/options.md:stagingRetention.maxCountnow also bounds kept releases, each a full installed copy.release-notes/v5-lincoln/5.3.md: a Going Back to a Previous Release note, including the disk-use change.Badges stay
v5.3.0: 5.3.0 is still in beta (latest tagv5.3.0-beta.4), and the staged-deploy section they extend is itself new in 5.3.0.Verified with
npm run format:checkandnpm run build(no broken links or anchors).🤖 Generated with Claude Code