docs: split the 8.0 / 8.1 release narratives, and backfill three missing changelog entries - #2010
Merged
Merged
Conversation
… entries Three releases were tagged and deployed but never written up, so the changelog jumps from 8.0.2.07 straight to 8.0.5.01. The gap hides the arrival of the SpringSaLaD 3D trajectory viewer (8.0.3.02) and the fix that made it reach remotely-run simulations (8.0.4.01) — reading the changelog, the viewer appears never to have shipped at all. Entries are reconstructed from the diffs of the merged PRs rather than from their titles: #1745, #1784, #1787, #1788, #1789/#1790/#1791 for 8.0.3.01; #1795, #1796, #1797 for 8.0.3.02; #1798 for 8.0.4.01. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FUd61NUJgz88h4PZs5MqHn
jcschaff
force-pushed
the
docs/backfill-8.0.3-8.0.4-changelog
branch
from
August 21, 2026 12:52
f9e3301 to
264a85d
Compare
For release notes and user-facing announcements, VCell 8.0 is the 8.0.0 builds — 8.0.0.01 through 8.0.0.03, the SpringSaLaD GA that ran on the production site from 2026-05-21 to 2026-08-14. Everything released after it belongs to VCell 8.1, which reached production on 2026-08-14 and is still accumulating. Published build numbers are unchanged; this is a narrative boundary, not a renumbering. The 8.0 document had been accumulating every 8.0.x build since the GA, so it credited 8.0 with a viewer, an import overhaul and two dozen fixes that no 8.0.0 build ever contained. Those move to the new 8.1 document — all 26 of its bug-fix bullets were annotated 8.0.5.01 or later, which is the boundary showing itself. Also renames 8.0.0.md to 8.0.md to match the narrative name, and updates the references in the 7.7 documents and the backlog note. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FUd61NUJgz88h4PZs5MqHn
…iffer Nothing in the procedure said which narrative file a release cut should append to, and the obvious guess — the one matching the build's MAJOR.MINOR — is now wrong: 8.0.28.01 is VCell 8.1 work. Says so, and says CHANGELOG.md is unaffected because it is organised by build. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FUd61NUJgz88h4PZs5MqHn
jcschaff
force-pushed
the
docs/backfill-8.0.3-8.0.4-changelog
branch
from
August 21, 2026 13:03
264a85d to
ec3295a
Compare
jcschaff
changed the title
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.
What this does
Two related documentation problems, both found while summarizing what changed across the 8.0 line.
1. Three releases were never written up
8.0.3.01, 8.0.3.02 and 8.0.4.01 were tagged and deployed on 2026-07-29 but have no
CHANGELOG.mdentry — the file jumps from 8.0.2.07 to 8.0.5.01.The gap hides a whole feature. The SpringSaLaD 3D trajectory viewer arrived in 8.0.3.02 (#1795/#1796/#1797) and reached remotely-run simulations in 8.0.4.01 (#1798). Everything the changelog did say about the viewer was a later refinement, so reading it end to end, the viewer appeared never to have shipped.
Entries were written from each PR's diff, not its title. Three came out differently as a result:
ACLState.removeUserFromACLreturned thePRIVATE_TYPEsingleton when the last name was removed, so the dialog flipped to "private" instead of showing an empty list.DecimalFormat("0.######"), applied to geometry extents in the simulation summary; it renders anything below 1e-6 as0, and the entry says so.LocalDataSetControllerMessaging, masked by thedefaultmethod added in SaLaD Phase 0: serve the SpringSaLaD trajectory (viewer) file #1795.2. The 8.0 narrative had absorbed three months of 8.1 work
For release notes and announcements, VCell 8.0 is the 8.0.0 builds — 8.0.0.01 through 8.0.0.03, the SpringSaLaD GA that ran in production from 2026-05-21 to 2026-08-14. Everything after 8.0.0.03 is VCell 8.1, which reached production on 2026-08-14 and is still accumulating.
Published build numbers are untouched. This is a narrative boundary, not a renumbering — 8.1 is delivered by builds numbered
8.0.x, and both documents say so.release-notes/major/8.0.0.mdhad been accumulating every build since the GA, so it credited 8.0 with a viewer, an import overhaul and two dozen fixes that no 8.0.0 build contained. All 26 of its bug-fix bullets were annotated 8.0.5.01 or later — the boundary showing itself.Changes
CHANGELOG.mdrelease-notes/major/8.0.md8.0.0.md, trimmed to 8.0.0.x contentrelease-notes/major/8.1.mddocs/RELEASING.md7.7-*.md,docs/backlog/01-close-and-verify.mdVerification
8.0.0.mdremains.git merge-base --is-ancestorconfirms the viewer commit is not in 8.0.0.03.🤖 Generated with Claude Code
https://claude.ai/code/session_01FUd61NUJgz88h4PZs5MqHn