chore: bump release to v2026.09.0 - #51
Merged
Merged
Conversation
Frontend-scoped release covering two fixes: form references now bind to their own deployment rather than the latest version repository-wide, and the deploy modal refuses a bundle whose forms or documents are missing from local storage. Root and packages/frontend go to 2026.09.0, in package.json and in the matching package-lock.json entries. packages/backend stays at 2026.08.9 - nothing under packages/backend changed, so its version legitimately lags the release. First release of September, so CalVer resets the patch to 0.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://brave-bay-04f351e03-51.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.0, scope
frontend. First release of September, so CalVer resets the patch to0.Entry
Two fixes, both from the same investigation:
45d3d2fformRefBindingrefs, plus the seven seededEXAMPLE_VERSIONSbumps9abc2f2Versions
package.json(root)packages/frontend/package.jsonpackages/backend/package.jsonpackage-lock.jsonpackages[""],packages["packages/frontend"]Nothing under
packages/backendchanged, so its version — and its lockfile entry — legitimately lag this release.Versions were edited by hand rather than with
npm version, which coerces to strict SemVer and would have written2026.9.0.Verification
npm ci --dry-run— exit 0, lockfile still resolves"version"lines — no dependency churnChangelog.test.tsxrendering the new entrynpm run formatno-op;npm run check-formatclean in both workspacesScope reconciliation
Renovate's five open PRs — #39, #40, #43, #44, #48 — were deliberately left out and will be gathered by the next release. Four of them rewrite
package-lock.json, the same file this PR edits, so they were kept out of the version bump rather than merged alongside it.Merge method
Merge commit only — not squash, not rebase. The changelog entry names
45d3d2fand9abc2f2by SHA; both alternatives rewrite those hashes and would leave the entry citing commits that do not exist onacc. The ruleset pins merge-only, but the default button is otherwise "Squash and merge".