Skip to content

docs: capture v0.7.0 publish-lane lessons learned#571

Merged
EffortlessSteven merged 1 commit into
mainfrom
docs/v0.7.0-lessons-learned
May 11, 2026
Merged

docs: capture v0.7.0 publish-lane lessons learned#571
EffortlessSteven merged 1 commit into
mainfrom
docs/v0.7.0-lessons-learned

Conversation

@EffortlessSteven

@EffortlessSteven EffortlessSteven commented May 11, 2026

Copy link
Copy Markdown
Member

Pure docs PR — captures the v0.7.0 publish lane retrospective.

Summary

Adds docs/release/v0.7.0-lessons-learned.md as the narrative record of the four publish failures the v0.7.0 release lane hit before the live publish completed. The doc covers symptom, root cause, fix PR, and takeaway for each failure, plus the carryover work deferred to v0.8.0.

Files added

  • docs/release/v0.7.0-lessons-learned.md (167 lines)

PRs referenced

External: shipper#173 (non-topological plan in shipper 0.3.0-rc.2).

Test plan

  • CI green on the docs-only diff
  • cargo xtask typos passes (verified locally)
  • git diff --check clean (verified locally)

@EffortlessSteven
docs: capture v0.7.0 publish-lane lessons learned
db841dd 
Adds docs/release/v0.7.0-lessons-learned.md as the narrative
retrospective for the four publish failures the v0.7.0 lane hit:
the PUBLISH_CRATES inversion against compat shims, the workspace
dev-dep version-on-publish=false-helper trap, the dirty-tree
handling needed during shipper adoption, and the non-topological
plan from shipper 0.3.0-rc.2. Captures the fix PRs and the
guardrails v0.8.0 should grow before re-attempting shipper.
@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 49 minutes and 51 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: 8e84e985-a9c8-4e41-93f6-cb937ca9f8fc

📥 Commits

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

📒 Files selected for processing (1)
  • docs/release/v0.7.0-lessons-learned.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/v0.7.0-lessons-learned

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.

This was referenced May 11, 2026
Open
Merged
@EffortlessSteven EffortlessSteven merged commit fc73239 into main May 11, 2026
5 checks passed
EffortlessSteven added a commit that referenced this pull request May 11, 2026
@EffortlessSteven
docs: document partial publish recovery and registry-truth rules (#579)
2827093 
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.
@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