chore: bump release to v2026.09.1 - #70
Merged
Merged
Conversation
Cuts v2026.09.1 covering 18 commits since v2026.09.0, scope both. Five of those eighteen had shipped silently. R2.3, R2.4, R3.1, R3.2 and R4.1 merged on 1 September at 20:40-20:54, after the v2026.09.0 bump at 18:08, so they appear in no changelog entry. This is the first record of them, which is what reconciling outstanding pull requests before versioning is for. Scope is both on evidence rather than assumption: packages/backend was touched by the typecheck script added in b0e1580 and by the coverage tests in c886fe0. The backend therefore catches up from 2026.08.9 rather than lagging further. What the entry covers: Nine RIP phase bundles. R5.1, R5.2, R5.4 and R6.1 complete the Flevoland ladder to eleven phases; R2.3 through R4.1 are the five that had gone unrecorded. R5.3 remains unmodelled, having no design sheet. Three fixes. Fifteen pre-existing type errors cleared and a tsc gate added across both workspaces and all four deployment workflows, closing a gap where nothing in the repository typechecked. Four further type errors in the ChainComposer tests. The deploy modal restructured so its actions stay reachable at 48 resources. Per-file branch coverage raised above 80% across both packages, frontend from 65.89% to 90.62% and backend from 91.49% to 92.22%. Five dependency updates, each verified locally before merge. Two findings worth keeping: check-format passes untouched under prettier 3.9.6, and TypeScript 5.9 produces exactly the same fifteen pre-existing errors as 5.8, so the tsc gate in this same release covers precisely the right set. Versions were edited by hand in all three package.json files and in the three matching package-lock.json entries. Not npm version: it coerces its argument to strict SemVer, and a zero-padded CalVer month is not a valid SemVer numeric identifier, so it would have written 2026.9.1 to every file it touched. Verified: typecheck, lint, check-format and build all clean, and npm ci --dry-run still resolves the lockfile. The build is the meaningful check on the entry itself, since changelog.json is imported by Changelog.tsx.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://brave-bay-04f351e03-70.westeurope.4.azurestaticapps.net |
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.
Cuts v2026.09.1, scope both, covering 18 commits since v2026.09.0.
Five commits had shipped silently
R2.3,R2.4,R3.1,R3.2andR4.1merged on 1 September at 20:40–20:54 — after the v2026.09.0 bump at 18:08. That entry covers only #49 and #50, so those five appear in no changelog at all. This entry is the first record of them.That is exactly what step 0 of
bump-releaseexists to catch: a pull request merged outside a release entry ships silently and the release history stops being a record of what is actually deployed.What the entry covers
tscgate; 4 further type errors in ChainComposer; deploy-modal scrollR5.3 remains unmodelled — no design sheet exists for it.
Scope is
both, on evidenceSo the backend catches up from
2026.08.9rather than lagging further. Nothing was left behind.Versions edited by hand
All three
package.jsonfiles plus the three matchingpackage-lock.jsonentries (top-level,packages[""], and each workspace).Not
npm version— it coerces to strict SemVer, and a zero-padded CalVer month is not a valid SemVer numeric identifier, so it would have written2026.9.1everywhere. Verified: zero occurrences of2026.9.1in the tree.Two findings from verifying the dependency updates
check-formatpasses untouched under prettier 3.9.6 — the reformatting that broke things on 2026-08-29 was already absorbed intoacc.tscgate landing in this same release covers precisely the right set.Verification
typecheck0 ·lint0 ·check-formatclean ·build0 ·npm ci --dry-run0The build is the meaningful check on the entry itself:
changelog.jsonis imported byChangelog.tsx, so a green build proves the new entry parses and its shape is accepted.Merging
Merge commit only — squash and rebase are disabled repo-wide because this entry cites each commit by SHA, and both alternatives rewrite them. Merging this PR pushes
acc, which triggers the acceptance deploys.