refactor(changelog)!: adopt pinned shared changelog commands - #261
Conversation
- Delegate generation, normalization, minor archiving, release notes and local tag preparation to the published research-repo-tools 0.1.7 CLI. - Preserve retained release history and dependency-note links while moving completed series to docs/archives/changelog. - Keep the historical git-cliff policy as a documented consumer exception and validate published changelog links alongside the shared checks. BREAKING CHANGE: changelog-unreleased now requires TAG DATE and leaves release metadata preparation separate. Replace the removed standalone archive-changelog, postprocess-changelog and tag-release entry points with research-repo-tools changelog commands. Tags must use v-prefixed SemVer; tagging requires today's UTC release date matching CITATION.cff. Refs #254
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: acgetchell/la-stack/.coderabbit.yaml Review profile: CHILL Plan: Essentials Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (9)
🚧 Files skipped from review as they are similar to previous changes (3)
Included review availability: This review used your included allowance. 2 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 3 reviews per hour. 📝 WalkthroughWalkthroughThe repository replaces local changelog and tag scripts with the pinned ChangesShared changelog tooling
Development pin group handling
Release history updates
Repository maintenance settings
Priority: ➖ Normal Estimated code review effort: 4 (Complex) | ~50 minutes Change: Refactor Sequence Diagram(s)sequenceDiagram
participant justfile
participant CLI as research-repo-tools changelog CLI
participant changelog as CHANGELOG.md
participant archives as docs/archives/changelog/
justfile->>CLI: Run generation, archive, or check command
CLI->>changelog: Generate or validate changelog
CLI->>archives: Rotate release notes or validate archives
Merge Risk: ⚪ Minimal · up to No concrete merge-blocking issue is established. Complete normal validation and retain draft status pending the requested approval. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
@coderabbitai full review Please review this changelog-focused migration while the PR remains a draft for Adam's approval. |
✅ Action performedFull review finished. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #261 +/- ##
==========================================
- Coverage 98.02% 98.00% -0.02%
==========================================
Files 13 13
Lines 6726 6726
==========================================
- Hits 6593 6592 -1
- Misses 133 134 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
- Forward preview options to the shared CLI and keep generated archives under the dedicated changelog formatter and final link check. - Accept valid included dependency groups while advancing only direct dev pins, leaving the shared tooling dependency under its own upgrade policy. - Keep declared release dates valid after a later merge and include canonical changelog archives in the release staging guidance. Refs #254
|
@coderabbitai review Please review follow-up commit cb8c471, including the preview, release-date and included-tooling compatibility repairs. Keep this PR as a draft for Adam's approval. |
✅ Action performedReview finished.
|
- Pin the synthetic Cargo identity independently of the checkout's release version while retaining the real consumer configuration and policy. - Disable inherited commit and tag signing only inside disposable repositories so fixture operations do not require user signing keys. Refs #254
|
@coderabbitai review Please review final fixture-only commit 2372f81 for signing isolation and stable synthetic release metadata. Keep this PR as a draft for Adam's approval. |
✅ Action performedReview finished.
|
- Advance Cargo CLI pins and align the uv pin with version 0.12.19. - Upgrade actionlint-py, Ruff, Semgrep, and Ty development requirements. - Refresh Cargo and Python locked dependencies while retaining the research-repo-tools 0.1.7 pin. Refs #254
- Use the shared 0.1.7 changelog format with a bounded exception for historical deps-dev release-note bodies. - Preserve literal Rust code during generation and retain complete release history, dates and links. - Enable automatic CodeRabbit draft reviews and align zizmor-action with the existing scanner pin. Refs #254 Refs acgetchell/research-repo-tools#62
1 participant
The repository duplicates changelog normalization, minor-series archives and tag preparation. This first phase delegates those commands to the exact PyPI release
research-repo-tools==0.1.7, locked intoolingand included bydev. It removes the three exclusive Python implementations and their unit tests after baseline and parity checks.Thin recipes cover generation, a read-only preview, explicit-date prospective releases, archiving, whole-history checks, root/archive notes and local tags. Completed series move to
docs/archives/changelog/MAJOR.MINOR.md. Dedicated final checks apply the normal repository Markdown/link policy to the published root and archives; generic Markdown formatting leaves these generated files alone.cliff.tomlnow uses the packaged 0.1.7 common template: shared categories, SemVer tag grammar, compare links and Markdown-aware code handling. Its only semantic exception retains historicaldeps-devbodies containing Ruff/Ty/setuptools release-note, changelog and comparison links. An installed-CLI integration assertion prevents unrelated template drift. The supported shared capability is tracked in research-repo-tools#62; no upstream implementation is included. Candidate formatting inherits repository rules and suppresses MD057 only before future archive files exist; final checks retain link validation.CodeRabbit now automatically reviews drafts using the official
reviews.auto_review.draftssetting. The existing zizmor 1.30.1 pin is preserved; its wrapper action advances narrowly to v0.6.4, which supports that scanner version. The broader action-update capability remains research-repo-tools#61.changelog-unreleased TAG DATEnow requires an explicit ISO date and leaves metadata preparation separate. Removed standalone entry points are replaced byresearch-repo-tools changelog; tags require v-prefixed SemVer and a declared heading date matching citation metadata. The consumer'sdeclareddate policy preserves tagging after a later-day merge. The existing updater accepts valid include-group declarations while advancing only directdevpins, preserving deliberate upgrades of the exact shared tooling pin.Validation on implementation head
1572957, preserving maintainer commit8a06208:markdown-ci,lint-config,changelog-check, Ruff formatting/lint/fixture checks and Ty passed. Python tests: 605 passed; 3 Cargo-metadata fixtures could not run because Cargo is absent from this cloud image. All 24 changelog integration cases passed. Local zizmor ran offline because no GitHub token is available to that executor.cb8c471entry, current configuration/guides and tests use the corrected declared-date policy. Authored history is preserved; the declared-date contract is authoritative.1572957, returned success and generated no actionable comments or unresolved threads.Rust/scientific/benchmark/performance implementation and the num-bigint/num-rational exclusions remain unchanged. Shared toolchain/setup/maintenance migration is deferred; the updater change is limited to compatibility with the included tooling group. The released installation contract uses existing uv plus shared setup when that later phase is adopted; this phase adds no generated bootstrap installers or future v0.1.8 capabilities.
Refs #254. This PR implements the changelog phase.
Keep this PR as a draft for Adam's approval; do not merge or enable auto-merge.
Summary by CodeRabbit
New Features
Documentation