fix(ci): unescape ${version%%.*} in post-release-docs-issue.yml heredoc - #828
Conversation
There was a problem hiding this comment.
Sorry @robotrocketscience, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
|
Warning Rate limit exceeded
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 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
|
[claim:review:oppenheimer:2026-05-14T23:16:42Z] |
|
[release:review:oppenheimer:2026-05-14T23:18:25Z] |
|
merge-train: blocked branch is not fast-forward on The |
…doc (#827) The heredoc was unquoted (<<EOF), so the backslash before \${version%%.*} suppressed expansion and emitted the literal string instead of the major-version digit; removing the backslash makes it consistent with the unescaped \${version} on the adjacent line.
cca0cd3 to
5f71d80
Compare
|
[claim:review:oppenheimer:2026-05-14T23:39:30Z] |
Approve-equivalent — single-character fix matches #827 acceptance exactlyOne atomic commit ( Diff is one character on line 49: drops the Bash semantics verified locally: Matches the issue's "Intended" output exactly. Aligns with surrounding CI status: pytest 3.12 / 3.13, secrets-scan, history-scan, pattern-scan, label, typos, size-check (latest run), release-docs-check, commit-msg-prefix, pr-title-prefix, pr-body-issue-link all SUCCESS. No CHANGELOG entry needed — this is a CI/workflow fix to a generated nag issue body, not user-facing behavior. Labeling |
|
[release:review:oppenheimer:2026-05-14T23:40:41Z] |
|
merge-train: merged 5f71d80 → |
Summary
Closes #827. One-char fix in
.github/workflows/post-release-docs-issue.ymlline 49 — drops the backslash before${version%%.*}inside the unquoted heredoc so the major-version expansion fires instead of emitting literal${version%%.*}text into the generated docs-sweep nag issue.Surrounding
${version}on the same line and on line 50 is already unescaped; this commit removes the inconsistency.Verification
For a release tagged
v3.1.0, the post-release-docs issue body will now correctly readCHANGELOG/v3.md has a ## [3.1.0] section ...rather thanCHANGELOG/v${version%%.*}.md.Out of scope
The other two CodeRabbit findings on #811 (
file=CHANGELOG.mdannotation, regex-metachar dot escaping) — both noted as defensible / pedantic in #827's body.Closes #827.