Repository navigation
chore(deps): move .objectstack-sha to objectstack 18.0.0 version commit 06cab4849a (objectui#13261) - #13266
Merged
Conversation
chore: version packages (#24524) objectstack@06cab4849a8a616487d468a11dd370e929137990 -- the commit the @objectstack/spec@18.0.0 tag names. Pin and packed manifests written by scripts/bump-objectstack.sh; pnpm-lock.yaml is unchanged (a frozen install accepts it). Claude-Session: https://claude.ai/code/session_01XVp19E1MYUTFM3dnkwz8gB Co-authored-by: Claude <noreply@anthropic.com>
…talled-pin claims restamped The pin delta f4755a68..06cab4849a reddens three things here: - objectstack 4bc3becd5f (objectstack#24640) carries the spec's retirement tombstone for the list view's filterableFields, whose reader objectui#13118 already removed. The object-view census's sixth bucket empties into the protocol-retired ones, the object-view anchor re-triages the key as a tombstone declared by reference, the list-view parity exemption leaves, the list-view block pins the row's refusal, and the served list form no longer offers the key. - e2e/live/ci/backend.env pairs the live lane with @objectstack 18.0.0. - 34 installed-pin sentences re-measured against the 18.0.0 build (a probe answering identically on the f4755a68 and 06cab4849a builds) and restamped. Empty-frontmatter changeset: comment-only edits in published sources. Claude-Session: https://claude.ai/code/session_01XVp19E1MYUTFM3dnkwz8gB Co-authored-by: Claude <noreply@anthropic.com>
Contributor
✅ Console Performance Budget
The eager closure is every chunk the entry reaches through static imports — what the browser fetches and parses before the app renders. The entry chunk on its own is a small fraction of it. 📦 Bundle Size Report
Size Limits
|
This was referenced Oct 20, 2026
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.
Fixes #13261
Clause-②: no
Scope: move
.objectstack-shafromf4755a68a797to06cab4849a8a616487d468a11dd370e929137990, objectstack's 18.0.0 version commit. Then fix every test the pin delta turns red, with no skip and no retry-wrap. The pin does not go past06cab4849a.The pin
git rev-parse 'refs/tags/@objectstack/spec@18.0.0^{}'andgit ls-remote originfor the same ref both answer06cab4849a8a616487d468a11dd370e929137990(chore: version packages objectstack#24524, "chore: version packages").git merge-base --is-ancestor 06cab4849a origin/mainexits 0 in the objectstack checkout (origin/maina8b44d4070). Exit 0 holds in a shallow checkout too..objectstack-pin/were written byscripts/bump-objectstack.sh --no-commit 06cab4849a…and committed together ind51d0408ae. The bump read a detached objectstack worktree at the target. The script reported "(on origin/main)", and the build ran under the verify lock withVERDICT command-exit 0.18.0.0-next.5to18.0.0). No dependency name changes.pnpm-lock.yamlis unchanged. The printed second half,pnpm install, rewrote it, but only by flipping whichesbuildpeer context vite resolves under two importers (0.27.7and0.28.2). Nothing in that diff comes from the pinned packages. I restored the committed lockfile and ranpnpm install --frozen-lockfile, which exits 0.check:lockfile-integrityreads clean andcheck:lockfile-dedupereads deduped.node scripts/objectstack-floor.mjs --dry-runexits 0 with "Floor 18.0.0: the earliest published @objectstack/spec whose tag @objectstack/spec@18.0.0 contains the pin 06cab4849a8a616487d468a11dd370e929137990." It reports 37 ranges that would move to^18.0.0at publish and writes nothing.Reds at the new pin, and what this PR does
registry-inputs-spec-parity: 3 rows aboutlist-view.filterableFields4bc3becd5f(objectstack#24640)UNPUBLISHED_EXEMPTIONSentry leaves, as it said it would at this pin. The key is now a harvested tombstoneobject-view-unmirrored-keys-7779: 13 rows4bc3becd5fBUCKET_SPEC_RETIRED_AHEAD_OF_PIN) empties intoPROTOCOL_RETIRED_KEYS(now 8) andBUCKET_PROTOCOL_RETIRED_TOMBSTONED(now 3), as its failure message prescribed. The live count goes 44 to 43. The accept legs parse the seven live mirrored keys. A new row pins thatfilterableFieldsis refused by name on both entry paths with the spec's prescription. The "legacy shorthand" description row is inverted to the[REMOVED]markerobject-view-spec-parity: thefilterableFieldsanchor reads RETIRED4bc3becd5fSPEC_COUNTERPARTand intoSANCTIONED_LOCAL, on the same footing asviewTabBar(a tombstone still declared on both faces)ListViewBlock.specInputs-13047: 2 rows4bc3becd5flist-viewrow now refuses the fixture. One row pins that refusal (pathfilterableFields, prescription text, plus an accept control). The Filter-panel measurement is kept on a node built past the row on purpose. The old quick-filter-bar row is removed: no node the save gate accepts can carry the key nowSchemaForm.topLevelUnion-11251: the served list form4bc3becd5f(view.form.tsdrops the input)filterableFieldsabsentci-cd-pipeline-doc: live-e2e pine2e/live/ci/backend.envreadsOBJECTSTACK_VERSION=18.0.0. The tag@objectstack/cli@18.0.0^{}resolves to06cab4849a, and npm serves@objectstack/cli@18.0.0check:installed-pin-claimsand its blocking test: 34 sentences in 24 files18.0.0(see below). Nine sentences that carry the re-measure chain also gainobjectui#13261The renderer needed no change. objectui#13118 had already removed the
filterableFieldsreader ahead of the pin.How the 34 sentences were re-measured
I wrote a probe and ran it unchanged against both builds in the pin store:
f4755a68(18.0.0-next.5) and06cab4849a(18.0.0). For every exported zod schema in@objectstack/spec,/ui,/dataand/automation(510 schemas), plus everyComponentPropsMaprow, it hashesz.toJSONSchema. It also runs the concrete parses the sentences state:ViewDataSchemaproviders;CalendarConfigSchemalegs and theobject-calendardataarms;FieldSchemalookupreferenceTo/referencepair,rowson four types, anddependsOnshapes;SelectOptionSchemawith label''and withdescription;record:highlightsiconandlayout: 'grid', andrecord:detailscolumns;object-kanbankey set and theObjectListViewSchemakey count;@objectstack/lint'sfieldRuleRootIssuetext forcurrent_userandapp.Results:
filterableFieldstombstone) or schemas that embed it (ObjectSchema,ViewSchema, the stack and artifact aggregates).FieldSchema,FlowSchemaandRecordRelatedListPropsdiffer in descriptions only.flow-node-config.startGates-12780: between the two commits, the automation engine changed only run-as identity, and the trigger packages changed only their changelogs and manifests.Verification at head
586a6233b5pnpm --workspace-concurrency=2with--filterset to@object-ui/app-shell^...,@object-ui/plugin-view^...,@object-ui/data-objectstack^...and@object-ui/plugin-list^..., thenbuild. The lock printedVERDICT command-exit 0.@object-ui/types,core,data-objectstack,plugin-list,plugin-viewandapp-shell. Each log echoestype-check.types,plugin-listandapp-shellwere re-run after the test edits.--maxWorkers=1, one package directory at a time, under the lock. These are the 106 test files that name a key or symbol the delta moved (filterableFields,NavigationItemSchema/navItemVisibleDataNeedsDataSource, the spec forms,retiredKey, the pin and lockfile scripts), pluscheck-installed-spec-pin-claims.test.ts.apps/console,app-shell,plugin-list,typesandscripts. Those are the reds in the table.586a6233b5:apps/console325/325,app-shell620 passed and 1 skipped,plugin-list220/220,types658/658,scripts318/318.586a6233b5, each exit 0:check:phantom-deps,self-import,unreferenced-sources,doc-example-readersandhandler-key-reads;check:side-effects-array,element-data-source-declaration,spec-symbols,action-forward-parityanddesigner-field-key-parity;check:icon-record-names,i18n-keys,i18n-drift,i18n-designer-parityandcontrol-bytes;check:installed-pin-claims,lockfile-integrity,lockfile-dedupeandnew-line-citations;check-hand-rolled-comment-mask.mjs,check-changeset-fixed.mjsandcheck-changeset-presence.mjs;check:changeset-claims,check:pending-changeset-literals,changeset:checkandcheck-changeset-no-major.mjs.check:spec-floorsexits 1, with every finding[no-artifact]: the workspace was not fully built. This is NOT MEASURED, not a red. The order said to record it and leave it.eslint --no-inline-config --format jsonover the 27 changed.ts/.tsxfiles reportsfiles 27, errors 0. All 147 warnings sit on lines this PR does not change.eslint.config.jshas noparserOptions.projectand no projectService, so type-aware linting is off and this diff cannot change the verdict on any untouched file.pnpm test(every package directory this PR touches, includingplugin-calendar,plugin-designer,plugin-detail,plugin-form,plugin-gantt,plugin-kanbanandcore), the whole-repopnpm lint,type-checkacross the workspace, andspec-range-floors.Changeset
.changeset/13261-objectstack-pin-18-0-0.mdhas an empty frontmatter, so it releases nothing. The only published-source edits are doc comments, whichcheck-changeset-presencecounts. It reads OK on the empty declaration.Acceptance notes
pnpm installat this pin rewritespnpm-lock.yamlwith anesbuildpeer-context flip that the pin did not cause. It is left uncommitted, because the committed lockfile installs frozen. A later unrelatedpnpm installmay show the same churn.packages/plugin-detailandpackages/typesstill declare@objectstack/spec^18.0.0-next.5inpackage.json. The floor step moves every range to^18.0.0at publish, so this PR leaves them.navItemVisibleDataNeedsDataSourcein the hand-writtenNavigationItemSchemasuperRefine (objectui half of objectstack-ai/objectstack#24534) #13076 and approvals B1 closing card (ruling C on objectui#12438): the inbox opens a request on the served sys_approval_request page where the side sheet is, deletes the sheet, and lists each retired pin against its user report #12484 remain open. Releasing them after this lands is triage's call.Generated by Claude Code