Skip to content

docs(CHANGES): Refresh release notes#349

Merged
tony merged 2 commits intomasterfrom
changes-refresh-may-2026
May 10, 2026
Merged

docs(CHANGES): Refresh release notes#349
tony merged 2 commits intomasterfrom
changes-refresh-may-2026

Conversation

@tony
Copy link
Copy Markdown
Member

@tony tony commented May 10, 2026

Summary

  • Rewrite CHANGES into release-note prose with lead paragraphs and user-facing deliverables
  • Consolidate the unreleased 0.33.x docs refresh around CLI reference, docs navigation, and gp-sphinx adoption
  • Normalize historical headings to the current changelog conventions while preserving release headers and dates

Validation

  • git diff --check
  • just build-docs — passed with 3 pre-existing duplicate-label warnings outside CHANGES
  • uv run pytest — 10 passed
  • uv run ruff check .
  • uv run mypy

why: Make the changelog useful as release documentation, not just a commit list. The May 2026 docs refresh needs product-level context and consistent prose before a release cut.\n\nwhat:\n- Rewrite CHANGES with lead paragraphs and prose deliverables\n- Consolidate the 0.33.x documentation refresh narrative\n- Normalize historical section headings to current conventions
@codecov
Copy link
Copy Markdown

codecov Bot commented May 10, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.06%. Comparing base (56cadaf) to head (ffa1aa8).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #349   +/-   ##
=======================================
  Coverage   91.06%   91.06%           
=======================================
  Files           9        9           
  Lines         347      347           
=======================================
  Hits          316      316           
  Misses         31       31           

☔ View full report in Codecov by Sentry.
📢 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.

why: The 0.5.0 release entry opened two Development sections, which duplicated rendered navigation and broke the fixed changelog section shape.\n\nwhat:\n- Remove the second Development heading\n- Keep the support-package note under the existing section
@tony tony merged commit ffa1aa8 into master May 10, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant