Repository navigation
chore(release): 4.0.1 - #2056
Merged
Merged
Conversation
…ls whole 4.0.0's marketplace listing was withdrawn and production never had it, so 4.0.1 is the first 4.x an installer upgrades to from 3.1.0. The listing notes for a release without a major are the head of its CHANGELOG section, so this entry's first paragraph now says so in plain words and carries 4.0.0's one-time contact mailing-address conversion (the backfill script before `os migrate apply --allow-destructive`), pointing at the 4.0.0 entry for the commands. Text only; the bump level stays patch. Claude-Session: https://claude.ai/code/session_012zh91QzFgePbkmuHnugLN3 Co-authored-by: Claude <noreply@anthropic.com>
`pnpm changeset:version` consumed the 2 pending changesets (2 patch: 2051-inline-logo, 2053-publish-flat-bundle) and computed 4.0.0 -> 4.0.1: it wrote `package.json` and spliced the 4.0.1 section into `CHANGELOG.md` (+16 lines; every byte from `## 4.0.0` down unchanged). Each entry is stamped with the main commit that added its changeset: 4547858 (#2055) and d7decd4 (#2054). Claude-Session: https://claude.ai/code/session_012zh91QzFgePbkmuHnugLN3 Co-authored-by: Claude <noreply@anthropic.com>
Matched by hand, per docs/RELEASE_STRATEGY.md section Version Sources: the app package's `version` in src/sales/index.ts, and the service module's `version` and its `dependencies` range on the app (`^4.0.1`) in src/service/index.ts. The maintainer pages `test/docs-declared-versions.test.ts` binds move with them: the README badge, the version rows in docs/ARCHITECTURE.md and docs/RELEASE_STRATEGY.md, and docs/STATUS.md's version sentence and its `pnpm validate` transcript (re-run: `HotCRM v4.0.1`, every figure unchanged: 18 Objects 358 Fields, 1 Apps 14 Views 8 Pages 5 Dashboards 10 Reports 31 Actions, 32 Flows, 12 Positions 7 Permissions). Claude-Session: https://claude.ai/code/session_012zh91QzFgePbkmuHnugLN3 Co-authored-by: Claude <noreply@anthropic.com>
…alls The latest-release heading and opening sentence state 4.0.1 in all three locales, as `test/docs-declared-versions.test.ts` binds them. One short paragraph above "What 4.0.0 adds" says that 4.0.1 is the first 4.x that installs from the marketplace (4.0.0's publish there was empty and was withdrawn), so a 3.x deployment upgrades straight to it, and that the sidebar logo and favicon now show on hosted installs. "What 4.0.0 adds" and its checks before upgrading stay: they apply to anyone coming from 3.x. Claude-Session: https://claude.ai/code/session_012zh91QzFgePbkmuHnugLN3 Co-authored-by: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
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
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.
Part of #2053
Clause-②: no
The 4.0.1 version PR, round 2 of #2053. It releases the publish flatten and its guard (#2054,
d7decd43) and the inlined app icon (#2055,45478585) through the normal flow ofdocs/RELEASE_STRATEGY.md§ Version Sources and § Release Checklist. There is no code change. The tagv4.0.1is the maintainer's push after the merge, and staging publishes from it.The bump
pnpm exec changeset status --verboseon45478585, before any edit, and again after the text edit below:pnpm changeset:version(exit 0) consumed both and wrote two files:package.json: 4.0.0 → 4.0.1;## 4.0.1section ofCHANGELOG.md: +16 lines, 0 removed, so every byte from## 4.0.0down is unchanged.Each entry is stamped with the main commit that added its changeset:
4547858(#2055) andd7decd4(#2054). Both are ancestors oforigin/main(merge-base --is-ancestor, exit 0).The changeset text edit, and why
4.0.0's staging listing was withdrawn and production never had it, so 4.0.1 is the first 4.x an installer upgrades to from 3.1.0.
scripts/publish-marketplace.mjssends a release's### Major Changessubsection when it has one, and otherwise the head of the section, capped at 8,000 chars. 4.0.1 has no major, so its listing shows its two patch entries. 4.0.0's notes, which carry the one-time contact address conversion, are not on that listing.So the first paragraph of
.changeset/2053-publish-flat-bundle.mdnow says, in plain words:scripts/backfill-contact-mailing-address.tsbeforeos migrate apply --allow-destructive;CHANGELOG.mdholds the commands.The previous text is now the second paragraph. The edit is text only: the bump stays
patch.Where the conversion sentence lands. Changesets orders the one-line 2051 entry first. In the 893-char notes:
os migrate apply --allow-destructiveat 446.All of it is far inside the 8,000-char cap. The offsets come from the script's own
releaseNotesFortext, evaluated against thisCHANGELOG.md; its length, 893, equals the dry run'srelease notes: 893 chars.Manifests and docs, aligned by hand as #2052 did
src/sales/index.tsversion→4.0.1.src/service/index.tsversion→4.0.1, anddependencies['app.objectstack.hotcrm']→^4.0.1.test/docs-declared-versions.test.tsbinds:docs/ARCHITECTURE.mdanddocs/RELEASE_STRATEGY.md;docs/STATUS.md's version sentence, and itspnpm validatetranscript re-read from a real run:HotCRM v4.0.1, every figure unchanged (18 Objects 358 Fields · 1 Apps 14 Views 8 Pages 5 Dashboards 10 Reports 31 Actions · 32 Flows · 12 Positions 7 Permissions).content/docs/whats-new, all three locales.Gates and the dry run, head
979d0ef5pnpm verifyunder the shared lock:os-verify-lock: VERDICT command-exit 0 · held the lock 497s.✓ Validation passed,HotCRM v4.0.1;18 suggestion(s), no errors;✓ i18n lint gate: 0 i18n/missing-* issues;✓ source hygiene clean;✓ source token ratchet clean;✓ Build complete,Artifact: dist/objectstack.json (2343.6 KB);Test Files 177 passed (177),Tests 3635 passed | 1 skipped (3636).pnpm build(Data: 18 Objects 358 Fields), thenDRY_RUN=1 pnpm publish:marketplace, exit 0:The bundle line is identical to round 1's on
6c78cfa1.Size: 13 files, +47 / −35. No governed path, so Tier S.
Acceptance notes
Check Changeset: this PR consumes the two changesets and adds none. It needs theskip-changesetlabel, as chore(release): 3.1.0 #1903 and chore(release): 4.0.0 #2052 carried it; the seat applies it.releaseNotesFor(observation, not filed). The major-section lookahead ends in a backslash-Z escape. A JavaScript regex has no end-of-input anchor by that name, so it matches a literal capital Z. A Major Changes body that contains a capital Z would be cut at that letter. It changes nothing today:Generated by Claude Code