Release-cut docs for 8.0.8.01 (and backfill 8.0.7.01) - #1858
Merged
Conversation
8.0.8.01 is a backend stability release: the export-progress Infinity incident and the chain of JMS problems it exposed, the SED-ML export id collisions that had been failing the nightly suite, and the Langevin solver at 1.4.12. 8.0.7.01 was cut with only an auto-generated GitHub body, so CHANGELOG.md jumped from [Unreleased] to [8.0.6.01]. Backfilled from that window's PRs (#1794, #1832, #1833, #1834) to close the hole. User-facing items from both are folded into release-notes/major/8.0.0.md: the update-alert fix, exports no longer stalling on an unrepresentable progress value, SED-ML/OMEX exports no longer carrying duplicate ids, OMEX validation errors being reported, and the solver update. Per docs/RELEASING.md this lands before the tag, so the tag points at a self-describing tree. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SY1XHgTZXZPqUECo2VBAWg
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.
Release-cut documentation for 8.0.8.01, landing before the tag so it points at a
self-describing tree (
docs/RELEASING.md).8.0.8.01 — backend stability
The export-progress
Infinityincident and the chain of JMS problems it exposed(#1837, #1838, #1839, #1842, #1844, #1845, #1847, #1850), the SED-ML export id collisions
that had been failing the nightly suite (#1827, #1840, #1843, #1846), and the Langevin
solver at 1.4.12 (#1857). The 3D field viewer's web content is packaged into the installers
but remains a flag-off proof of concept (#1829, #1854).
Version choice: PATCH bump with BUILD reset, per
docs/RELEASING.mdfor a bugfix release.Nothing user-facing is switched on — #1829 ships flag-off — so no MINOR bump.
8.0.7.01 backfill
That release was cut with only an auto-generated GitHub body, so
CHANGELOG.mdjumpedstraight from
[Unreleased]to[8.0.6.01]. Backfilled from its PR window (#1794, #1832,#1833, #1834) so the file is a complete record.
release-notes/major/8.0.0.md
Folded in the items a user would notice: the update-alert fix, exports no longer stalling on
an unrepresentable progress value, SED-ML/OMEX exports no longer carrying duplicate ids, OMEX
validation errors being reported, and the solver update.
tools/openapi.yamlis unchanged in both windows, so both sections say so under Notes forAPI consumers.
🤖 Generated with Claude Code
https://claude.ai/code/session_01SY1XHgTZXZPqUECo2VBAWg