Skip to content

chore(release): release v0.4.3#156

Merged
acgetchell merged 1 commit into
mainfrom
release/v0.4.3
Jun 9, 2026
Merged

chore(release): release v0.4.3#156
acgetchell merged 1 commit into
mainfrom
release/v0.4.3

Conversation

@acgetchell

@acgetchell acgetchell commented Jun 9, 2026

Copy link
Copy Markdown
Owner
  • Bump crate, script package, lockfile, README, and citation metadata to v0.4.3
  • Promote the v0.4.3 performance report and archive the v0.4.2 comparison
  • Refresh README nalgebra/faer benchmark data and plot assets
  • Reorganize benchmark documentation around release, local, and artifact workflows
  • Update release guidance and roadmap follow-up items for v0.4.4 performance work

Summary by CodeRabbit

  • Documentation

    • Released v0.4.3 with performance optimizations to factorization and solver kernels.
    • Introduced performance comparison reports and archival system for tracking improvements across releases.
    • Enhanced benchmarking documentation with updated methodology and release workflow guidance.
  • Chores

    • Updated version to 0.4.3 across project manifests and metadata.

- Bump crate, script package, lockfile, README, and citation metadata to v0.4.3
- Promote the v0.4.3 performance report and archive the v0.4.2 comparison
- Refresh README nalgebra/faer benchmark data and plot assets
- Reorganize benchmark documentation around release, local, and artifact workflows
- Update release guidance and roadmap follow-up items for v0.4.4 performance work
@acgetchell acgetchell enabled auto-merge June 9, 2026 08:49
@coderabbitai

coderabbitai Bot commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

This PR releases v0.4.3 by bumping version numbers across all manifests, documenting release notes in CHANGELOG.md and roadmap.md, reorganizing benchmarking documentation with structured guidance, publishing the v0.4.3 vs v0.4.2 performance report, archiving the prior v0.4.2 vs v0.4.1 report, and updating scripts/tests to consistently reference archived performance comparisons.

Changes

v0.4.3 Release with Performance Documentation

Layer / File(s) Summary
Version bumps across manifests
Cargo.toml, CITATION.cff, pyproject.toml, README.md
Package version incremented from 0.4.2 to 0.4.3 across all manifest files and README dependency examples.
Release notes and planning documentation
CHANGELOG.md, docs/roadmap.md
v0.4.3 release section added to CHANGELOG documenting Added (performance automation, vs_linalg checks), Changed (Rust hygiene hardening), Fixed (error handling), and Performance items. Roadmap updated with Release posture guidance and v0.4.4 leaf-kernel performance planning.
Benchmarking documentation and release procedures
docs/BENCHMARKING.md, docs/RELEASING.md
BENCHMARKING.md restructured with Start Here table, Contents index, and Release Notes section. RELEASING.md updated to describe Release Benchmarks workflow artifact attachment and removal of earlier manual baseline save step.
v0.4.3 benchmark report and archived v0.4.2 comparison
docs/PERFORMANCE.md, README.md, docs/archive/performance/*
PERFORMANCE.md refreshed with v0.4.3 vs v0.4.2 benchmark tables and archive guidance. README.md lu_solve benchmark table updated. v0.4.2 vs v0.4.1 comparison archived as new docs/archive/performance/v0.4.2-vs-v0.4.1.md with archive index updated.
Script and test updates for archived performance links
scripts/archive_performance.py, scripts/bench_compare.py, scripts/tests/test_archive_performance.py, scripts/tests/test_bench_compare.py
Scripts updated to reference archived performance reports under docs/archive/performance/ in "How to Update" sections. Test assertions added/extended to verify archive link presence in generated reports.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • acgetchell/la-stack#150: Introduces core archive release performance reports functionality that this PR builds upon by adding documentation and test coverage for the archived performance links.
  • acgetchell/la-stack#144: Adds Release Benchmarks workflow for publishing/restoring Criterion baselines to GitHub releases, which this PR documents and integrates into the release procedures.
  • acgetchell/la-stack#70: Introduces scripts/bench_compare.py for benchmark reporting, which this PR extends with archived performance comparison links.

Suggested labels

documentation, release, testing

Poem

🐰 A version bumped, reports compiled with care,
Benchmarks archived, workflows now fair,
Performance tracked from 0.4.2 to the new,
Documentation guides what reviewers must do! 📊

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'chore(release): release v0.4.3' clearly and concisely summarizes the primary change: bumping the crate to version 0.4.3, which is confirmed by updates across Cargo.toml, CITATION.cff, pyproject.toml, and related documentation.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/v0.4.3

Comment @coderabbitai help to get the list of available commands and usage tips.

@acgetchell acgetchell self-assigned this Jun 9, 2026
@codecov

codecov Bot commented Jun 9, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.13%. Comparing base (45affa8) to head (925cbb7).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #156   +/-   ##
=======================================
  Coverage   98.13%   98.13%           
=======================================
  Files           7        7           
  Lines        3323     3323           
=======================================
  Hits         3261     3261           
  Misses         62       62           
Flag Coverage Δ
unittests 98.13% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
CHANGELOG.md (1)

90-93: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix stale release version label in v0.4.3 notes.

Within the 0.4.3 section, this entry still says “Sync citation metadata for v0.4.2”, which makes the release notes internally inconsistent.

Suggested patch
-- Sync citation metadata for v0.4.2 [`f473ec5`](https://github.com/acgetchell/la-stack/commit/f473ec50946e5f668e9ad9a2d978e499dcb10f04)
+- Sync citation metadata for v0.4.3 [`f473ec5`](https://github.com/acgetchell/la-stack/commit/f473ec50946e5f668e9ad9a2d978e499dcb10f04)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CHANGELOG.md` around lines 90 - 93, The release notes in the 0.4.3 section
contain a stale label "Sync citation metadata for v0.4.2"; update that
header/text to reference v0.4.3 (e.g., change the phrase to "Sync citation
metadata for v0.4.3") so the 0.4.3 changelog entry is internally consistent;
search for the string "Sync citation metadata for v0.4.2" in CHANGELOG.md and
replace it with the corrected v0.4.3 wording, then run any local linting/format
checks before committing.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@CHANGELOG.md`:
- Around line 90-93: The release notes in the 0.4.3 section contain a stale
label "Sync citation metadata for v0.4.2"; update that header/text to reference
v0.4.3 (e.g., change the phrase to "Sync citation metadata for v0.4.3") so the
0.4.3 changelog entry is internally consistent; search for the string "Sync
citation metadata for v0.4.2" in CHANGELOG.md and replace it with the corrected
v0.4.3 wording, then run any local linting/format checks before committing.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c70bd792-125a-49c4-80fe-947bc25b5521

📥 Commits

Reviewing files that changed from the base of the PR and between 45affa8 and 925cbb7.

⛔ Files ignored due to path filters (4)
  • Cargo.lock is excluded by !**/*.lock
  • docs/assets/bench/vs_linalg_lu_solve_median.csv is excluded by !**/*.csv
  • docs/assets/bench/vs_linalg_lu_solve_median.svg is excluded by !**/*.svg
  • uv.lock is excluded by !**/*.lock
📒 Files selected for processing (15)
  • CHANGELOG.md
  • CITATION.cff
  • Cargo.toml
  • README.md
  • docs/BENCHMARKING.md
  • docs/PERFORMANCE.md
  • docs/RELEASING.md
  • docs/archive/performance/README.md
  • docs/archive/performance/v0.4.2-vs-v0.4.1.md
  • docs/roadmap.md
  • pyproject.toml
  • scripts/archive_performance.py
  • scripts/bench_compare.py
  • scripts/tests/test_archive_performance.py
  • scripts/tests/test_bench_compare.py

@acgetchell acgetchell merged commit 95118dd into main Jun 9, 2026
20 checks passed
@acgetchell acgetchell deleted the release/v0.4.3 branch June 9, 2026 08:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant