Fix release docs automation#9006
Conversation
|
Newest code from mattermost has been published to preview environment for Git SHA 868ae48 |
There was a problem hiding this comment.
Pull request overview
This PR updates the release-docs automation script used by the Update Docs GitHub Actions workflow, primarily to (a) support applying multiple versions in one run and (b) reduce workflow failures from slow Claude responses.
Changes:
- Parse
VERSIONas a comma-separated list (VERSIONS) and apply updates per file once per version (chained). - Adjust prompting to pass the active
versioninto each Claude request. - Increase Anthropic client request timeout from 120s to 300s.
|
Warning Review limit reached
More reviews will be available in 22 minutes and 45 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe script now processes multiple comma-separated release versions sequentially, parsing each into a VERSIONS list and updating targeted documentation files in order with chained outputs so changelog entries accumulate. The refactored ChangesMulti-version documentation release automation
Estimated code review effort🎯 4 (Complex) | ⏱️ ~40 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 |
|
/check-cla |
|
Newest code from mattermost has been published to preview environment for Git SHA cef3bbd |
|
Newest code from mattermost has been published to preview environment for Git SHA 0e7df42 |
| # for multi-version releases (e.g. security patches across several branches). | ||
| # Each version is applied to every file in sequence; the output of one version | ||
| # becomes the input for the next, so entries accumulate correctly in changelogs. | ||
| VERSIONS: list[str] = [v.strip() for v in os.environ["VERSION"].split(",") if v.strip()] |
There was a problem hiding this comment.
The "versions" approach isn't aligned with the respective workflow update-docs.yaml (e.g. expect version, we do normalization there, etc).
Based on the current error I'd do
- Open a new pull-request just bumping the timeout -> merge -> run pipeline with one version to ensure is green
- Keep updating this pull-request to support multiple versions since it'll require more logic.
Two fixes:
Updated spec doc: https://mattermost.atlassian.net/wiki/spaces/Security/pages/4518772760/Automation+-+Release+Docs+Update+GitHub+Actions+Workflow.