docs(dev): add Step 0 to release process runbook#589
Merged
Conversation
Captures the convention introduced in the 0.6.1 cycle: before preparing the changelog or branching, open a GitHub issue to coordinate the release, explain why we are cutting it now, and list any unusual pre-release todos. Routine steps are already covered by this runbook and need not be repeated.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #589 +/- ##
=======================================
Coverage 73.67% 73.67%
=======================================
Files 22 22
Lines 4483 4483
=======================================
Hits 3303 3303
Misses 1180 1180 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
utiberious
added a commit
to utiberious/galgebra
that referenced
this pull request
Apr 4, 2026
… update release date Adds changelog entries for three PRs merged after the initial 0.6.1 changelog write (pygae#583): - pygae#590 / pygae#576: SymPy 1.13 TR3 performance workaround in curvi_linear_latex - pygae#589 / pygae#588: Step 0 added to release-process runbook - pygae#587 / pygae#586: pyproject.toml migration (PEP 517/621) Also updates the 0.6.1 release date from 2026.04.02 to 2026.04.04 (actual merge date of the last included PR). Addresses the changelog TODOs listed in release issue pygae#588.
3 tasks
utensil
pushed a commit
that referenced
this pull request
Apr 4, 2026
…se date * docs(changelog): add 0.6.1 entries for #587, #589, #590; update release date Adds changelog entries for three PRs merged after the initial 0.6.1 changelog write (#583): - #590 / #576: SymPy 1.13 TR3 performance workaround in curvi_linear_latex - #589 / #588: Step 0 added to release-process runbook - #587 / #586: pyproject.toml migration (PEP 517/621) Also updates the 0.6.1 release date from 2026.04.02 to 2026.04.04 (actual merge date of the last included PR). Addresses the changelog TODOs listed in release issue #588. * docs(changelog): expand 0.6.1 entries for #570, #572, #585 - #570: add ZeroDivisionError fix in Mv._latex, validate_nb_refresh.py, bumping-sympy.md guide, sympy pin bump, and issue #566 reference - #572: remove bumping-sympy.md (belongs to #570, not #572) - #585: add missing entry for is_blade test expansion * docs(changelog): address review — fix tag, ordering, and 570 ZDE split - #590: :support: → 🐛 (restores broken CI, not just a workaround) - #585: move to correct descending-number position (between #587 and #580) - #570: split ZeroDivisionError fix into separate 🐛`570` entry so it leads clearly; :support:`570` retains notebook refresh / tooling content
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Step 0 to
doc/dev/release-process.md: open a release issue before preparing the changelog or branching.Captures the convention introduced in the 0.6.1 cycle (see #588). The issue should explain why we are cutting the release now, summarize what is in it (including any motivation or backstory), and list unusual pre-release todos. Routine steps are already covered by the runbook.