Skip to content

docs: document partial publish recovery and registry-truth rules#579

Merged
EffortlessSteven merged 1 commit into
mainfrom
docs/publish-recovery
May 11, 2026
Merged

docs: document partial publish recovery and registry-truth rules#579
EffortlessSteven merged 1 commit into
mainfrom
docs/publish-recovery

Conversation

@EffortlessSteven

@EffortlessSteven EffortlessSteven commented May 11, 2026

Copy link
Copy Markdown
Member

Summary

Pure docs PR. Captures publish-recovery operational procedure and registry-truth rules as durable institutional knowledge after the v0.7.0 publish lane.

This is "PR 6" of the v0.7.1 publish-system hardening series:

Files added

  • docs/how-to/recover-partial-publish.md — operator-facing procedure: when to retry vs patch vs retag, what counts as a partial publish, anti-patterns.
  • docs/release/publish-recovery.md — release-process posture: registry truth, recovery posture by failure class, when to yank, current shipper status.

Complementary to #571 (v0.7.0 lessons-learned retrospective). #571 = what happened in v0.7.0; these docs = what to do during any future partial publish.

References

Test plan

  • CI green (docs only; no source changes)

@EffortlessSteven
docs: document partial publish recovery and registry-truth rules
adee751 
Add a how-to and a release-policy doc that capture the operational
playbook for partial-publish incidents (one or more crates published,
release as a whole failed) and the registry-truth posture the release
process should hold.

- docs/how-to/recover-partial-publish.md: operator-facing recovery
  procedure (recognize, inspect registry, choose path A/B,
  anti-patterns, hardening tooling).
- docs/release/publish-recovery.md: release-process policy
  (registry-truth, failure-class recovery table, tag-touching rules,
  yank rules, hardening backlog).

These are the how-to + policy side. The v0.7.0 retrospective
(lessons-learned narrative) is the complementary doc in #571.
@gemini-code-assist

gemini-code-assist Bot commented May 11, 2026

Copy link
Copy Markdown

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented May 11, 2026

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@coderabbitai

coderabbitai Bot commented May 11, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@EffortlessSteven has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 13 minutes and 42 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: b3028749-b1b3-4ed2-acba-ae245c22c08b

📥 Commits

Reviewing files that changed from the base of the PR and between 1a5b944 and adee751.

📒 Files selected for processing (2)
  • docs/how-to/recover-partial-publish.md
  • docs/release/publish-recovery.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/publish-recovery

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@EffortlessSteven EffortlessSteven merged commit 2827093 into main May 11, 2026
5 checks passed
@EffortlessSteven EffortlessSteven mentioned this pull request May 11, 2026
Merged
4 tasks
EffortlessSteven added a commit that referenced this pull request May 11, 2026
@EffortlessSteven
release: cut v0.7.1 (#583)
4a758a3 
Bump workspace version 0.7.0 -> 0.7.1 and seed the CHANGELOG entry
describing the release-hardening additions (#572, #577, #578, #580,
#581) and docs (#571, #579). No new product surface; no shim removal;
no profile work. Patch evidence lane passes.
@EffortlessSteven EffortlessSteven mentioned this pull request May 11, 2026
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@EffortlessSteven