Repository navigation
Release v4.4.0 #276
Description
Bart asked for a release. Follow the release procedure in AGENTS.md §4 ("Releasing").
State as of 2026-09-07:
- Latest release is v4.3.1 (2026-09-01,
gh release view). - Only PR Give a wing's mesh and airfoil settings a home in the settings file #271 (mesh:/airfoil: settings blocks) has merged since that tag. The
## Unreleasedchangelog section describes exactly that and nothing else — check it again againstv4.3.1...mainyourself before trusting this. - The additions are purely additive API, so the version is v4.4.0. Bart has asked for this release and named that number, so the Project.toml bump is prompted rather than on your own initiative.
What is wanted:
- Open a PR against main that sets
version = "4.4.0"in Project.toml and turns the## Unreleasedchangelog header into## VortexStepMethod v4.4.0 <merge date>. Nothing else in that PR. Bart merges it; the release waits for it. - If PR Take the panel normal from the quarter-chord step #273 ("Take the panel normal from the quarter-chord step") merges before you get there, it belongs in this release too: add its
### Fixedentry to the same section. Still v4.4.0. If it has not merged, do not wait on it — release on Give a wing's mesh and airfoil settings a home in the settings file #271 alone. - Confirm main is green and that the docs and README describe what is going out. Anything that needs changing is its own PR Bart merges, and the release waits for it — say so on the thread.
- Then
agent release: the notes go to Slack for a thumbs up before anything is registered.
Activity
1-Bort-1 commentedon Sep 7, 2026
Queued as
VortexStepMethod.jl-276.1-Bort-1 commentedon Sep 7, 2026
Taken — v5.0.0, not v4.4.0. This repo bumps the major for a break (its only other BREAKING entries are under v4.0.0), so breaking off v4.3.1 is v5.0.0.
#281 now sets
Project.tomlto 5.0.0, heads the section## VortexStepMethod v5.0.0 2026-09-07, and prefixes #262's entryBREAKING:. That entry already states the break you named: the wrap sits at exactlyclearanceinstead of a cell over it, so a V3 canopy's aft strip comes out2 * clearancethick where the grid gave3.5 * cell_size.ShrinkWrap'scell_sizerename rides along under the same prefix. I rewrapped that bullet to 80 columns while adding the prefix —git show --word-diff 5612d24shows the only tokens that changed are-v4.4.0,+v5.0.0,+BREAKING:. Title and body of #281 rewritten too; they said 4.4.0 throughout.The release waits for you to merge #281 — I do not push to main, and #280 means
agent releasemust not run before that merge. #273 is still open, so it is not in this release.mainis green at 0a8f046 (run 34126474537, all 7 jobs), and the docs cover what is going out; the gap I found is #278, which predates this release and did not hold it up.Two things to look at before you merge: if you meant to keep the number and only flag the notes, say so and I will put it back — registration is irreversible. And
gh auth statusexits 1 on the box ("the token in ~/.config/gh/hosts.yml is invalid") whilegh pr viewstill works;bin/release:45gates on it, soagent releasewill abort there until that token is refreshed.