fix(markdown): release-notes details + bust stale readme cache#626
Conversation
There was a problem hiding this comment.
rainxchzed has reached the 50-review limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughDetailsRepositoryImpl updates markdown content processing in two methods: ChangesRelease Body and README Processing Updates
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
Two follow-ups to the markdown preprocessor PRs:
`processReleaseBody` was stripping `
Details
`, `README cache key bumped `details:readme:` → `details:readme:v2:`. Users running pre-fix(markdown): run details normalization before HTML-to-newline passes #625 builds have cached READMEs with stale broken-table output. Bumping the key forces a re-fetch on next view so the new preprocessor output replaces the cached one without waiting for natural TTL.
Test plan
Summary by CodeRabbit