Repository navigation
docs(issues): refresh stale versions placeholder in bug report template - #21
Conversation
The Versions placeholder still advertised ruby2html 2.0.0 / ruby 3.4.7. Point it at the current gem version (2.1.0) and dev Ruby (4.0.9). GitHub issue forms cannot derive values at fill time, so the string stays static; the release checklist now refreshes it with the version bump. Dz-Task-Id: tsk_e9fb14743141af19c9e205093c758762
Benchmarks: x86_64 (linux)
escape_bench (C ext) · peak RSS 107 MB
escape_bench (pure Ruby) · peak RSS 148 MB
render_bench (C ext) · peak RSS 132 MB
render_bench (pure Ruby) · peak RSS 132 MB
tag_bench (C ext) · peak RSS 39 MB
tag_bench (pure Ruby) · peak RSS 27 MB
Rails request (C ext) · peak RSS 240 MB
|
Benchmarks: aarch64 (linux)
escape_bench (C ext) · peak RSS 118 MB
escape_bench (pure Ruby) · peak RSS 150 MB
render_bench (C ext) · peak RSS 131 MB
render_bench (pure Ruby) · peak RSS 131 MB
tag_bench (C ext) · peak RSS 39 MB
tag_bench (pure Ruby) · peak RSS 26 MB
Rails request (C ext) · peak RSS 233 MB
|
|
Waiting for a review of this head. Nothing is needed from you right now.
Status for head 🤖 Posted by developerz.ai — an automated agent, not a human. |
|
Fix failing CI on #21
Work landed on #21 — watching it toward merge. 43m · 49 tool calls · 11 messages Sessions: coding run · review 1 🤖 developerz.ai, an automated agent, not a human — sebastian-3 (developerz-ai[bot]) · model |
|
File fence widened for a CI fix. The
Why: The bundle-audit job runs The platform granted it under the same area lock a new task takes (no other in-flight task holds these files), after checking the path is not a secret, CI configuration or a human-merge path. Posted automatically by the developerz bot (AI-authored). |
Follow-up intent: Fix failing CI on #21 Dz-Task-Id: tsk_5ea594400e0f97c31ba24826ce856298
🟡 Reviewed1 actionable comment(s) · grounded on your code ⏱ 23s wall clock · 🤖 developerz.ai — automated review, running on your model and your box. |
There was a problem hiding this comment.
Review summary — 3 file(s), 1 finding(s).
Critical 0 · Major 0 · Minor 1 · Nit 0
Docs-only refresh of the issue-template Versions placeholder (2.1.0 / ruby 4.0.9) plus a release-checklist and skill step for keeping it current. Low risk, but the Rails value in the placeholder was changed to a version that contradicts the PR's own stated source.
- 1 noise file(s) auto-skipped (lockfiles/generated/vendored — re-include with path_filters)
- test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against
🤖 developerz.ai review — automated, running on your model and your box. What is this? · Reviewed by router/MiniMax-M3 — 12.4k in / 264 out over 1 call, on your flat-rate plan: no per-token charge (~<$0.01 at list price).
Follow-up intent: Address review findings on #21 Dz-Task-Id: tsk_88e8255a784ab2ea1bf3e63653322f42
|
File fence widened for a CI fix. The
Why: The failing job The platform granted it under the same area lock a new task takes (no other in-flight task holds these files), after checking the path is not a secret, CI configuration or a human-merge path. Posted automatically by the developerz bot (AI-authored). |
Follow-up intent: Fix failing CI on #21 Dz-Task-Id: tsk_1e0269b54c96136b9640ff31a5d1b300
There was a problem hiding this comment.
Review summary — 3 file(s), 1 finding(s).
Critical 0 · Major 0 · Minor 1 · Nit 0
Docs-only change refreshing the stale Versions placeholder in the bug report form and adding release-checklist steps to keep it current. Low risk; one docs contradiction: the placeholder advertises Rails 8.1.4.1 while its own comment and the PR point at the lockfile's 8.1.4.
- 1 noise file(s) auto-skipped (lockfiles/generated/vendored — re-include with path_filters)
- test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against
🤖 developerz.ai review — automated, running on your model and your box. What is this? · Reviewed by router/MiniMax-M3 — 12.9k in / 308 out over 1 call, on your flat-rate plan: no per-token charge (~<$0.01 at list price).
There was a problem hiding this comment.
Review summary — 3 file(s), 1 finding(s).
Critical 0 · Major 0 · Minor 1 · Nit 0
Refreshes the issue-template Versions placeholder to the current gem/Ruby/Rails versions, adds a release-checklist step (docs/release.md) and a matching step to the release skill.
- test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against
🤖 developerz.ai review — automated, running on your model and your box. What is this? · Reviewed by router/MiniMax-M3 — 26k in / 512 out over 2 calls, on your flat-rate plan: no per-token charge (~<$0.01 at list price).
What
The Versions placeholder still advertised ruby2html 2.0.0 / ruby 3.4.7. Point it
at the current gem version (2.1.0) and dev Ruby (4.0.9). GitHub issue forms
cannot derive values at fill time, so the string stays static; the release
checklist now refreshes it with the version bump.
Acceptance
Changes
.github/ISSUE_TEMPLATE/bug_report.yml(edit) — Fix the stale Versions placeholder (line 44) to "ruby2html 2.1.0, ruby 4.0.9 +YJIT, Rails 8.1.4, x86_64-linux" — gem version from lib/gem/ruby2html/version.rb:4, Ruby from .ruby-version:1, Rails 8.1.4 unchanged (Gemfile.lock:204) — and add a short YAML comment above it saying issue forms cannot derive the value at fill time and how to refresh it on release. Keep it a placeholder (the reporter supplies their own versions); touch no other field of the form.docs/release.md(edit) — Add a release-PR checklist step (between the CHANGELOG step and Verify) that refreshes the issue-template versions placeholder — gem version from lib/gem/ruby2html/version.rb, Ruby from .ruby-version, Rails from Gemfile.lock — and narrow the 'containing nothing else' rule so that refresh may ride along in the release PR. Renumber the following items; change nothing else in the file..claude/skills/release/SKILL.md(edit) — Handoff from editor:issue-template: docs/release.md now has a release-PR step that refreshes the issue-template versions placeholder from version.rb, .ruby-version and Gemfile.lock, and explicitly allows that refresh in the release PR. — The skill's own numbered Steps (Bump / Verify / PR) mirror the release-PR procedure but do not mention the placeholder refresh, so an agent following the skill could ship a release with a stale placeholder. Add the same refresh to the skill's steps (or state that the skill's step list follows docs/release.md's checklist including the issue-template refresh).Verification
./bin/checkpassed (exit 0) in 17s.Notes
Premises of the request the team disproved:
Follow-up work this change creates outside its diff:
.github/ISSUE_TEMPLATE/performance.yml— This task refreshed the bug-report Versions placeholder but left the sibling performance Environment placeholder unchanged; performance.yml:17 still shows 'ruby 3.4.7 +YJIT'; it is outside this task's acceptance scope, so performance reporters still see a stale Ruby version.dz/briefs/release-due.md— docs/release.md's release-PR checklist gained a placeholder-refresh step; the weekly brief's mirrored list was not changed here; the agent opens release PRs from .dz/briefs/release-due.md:38-47; without the mirrored step the placeholder is not refreshed on release and drifts again🤖 Opened by developerz.ai for task
tsk_e9fb14743141af19c9e205093c758762on sebyx07/ruby2html.Raised automatically by the
raw_task_triagelane.