chore: version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

The changelog information of each package has been omitted from this message, as the content exceeds the size limit.

@objectstack/hono@17.1.0

@objectstack/cli@17.1.0

@objectstack/client@17.1.0

@objectstack/cloud-connection@17.1.0

@objectstack/console@17.1.0

@objectstack/core@17.1.0

create-objectstack@17.1.0

@objectstack/driver-sql@17.1.0

@objectstack/lint@17.1.0

@objectstack/mcp@17.1.0

@objectstack/metadata-protocol@17.1.0

@objectstack/objectql@17.1.0

@objectstack/platform-objects@17.1.0

@objectstack/plugin-approvals@17.1.0

@objectstack/plugin-audit@17.1.0

@objectstack/plugin-auth@17.1.0

@objectstack/plugin-email@17.1.0

@objectstack/plugin-hono-server@17.1.0

@objectstack/plugin-security@17.1.0

@objectstack/plugin-sharing@17.1.0

@objectstack/rest@17.1.0

@objectstack/runtime@17.1.0

@objectstack/service-automation@17.1.0

@objectstack/service-datasource@17.1.0

@objectstack/service-messaging@17.1.0

@objectstack/spec@17.1.0

@objectstack/types@17.1.0

@objectstack/account@17.1.0

@objectstack/setup@17.1.0

@objectstack/studio@17.1.0

@objectstack/client-react@17.1.0

@objectstack/connector-mcp@17.1.0

@objectstack/connector-openapi@17.1.0

@objectstack/connector-rest@17.1.0

@objectstack/connector-slack@17.1.0

@objectstack/driver-memory@17.1.0

@objectstack/driver-mongodb@17.1.0

@objectstack/driver-sqlite-wasm@17.1.0

@objectstack/driver-turso@17.1.0

@objectstack/formula@17.1.0

@objectstack/metadata@17.1.0

@objectstack/metadata-core@17.1.0

@objectstack/metadata-fs@17.1.0

@objectstack/observability@17.1.0

@objectstack/embedder-openai@17.1.0

@objectstack/knowledge-memory@17.1.0

@objectstack/knowledge-ragflow@17.1.0

@objectstack/plugin-dev@17.1.0

@objectstack/plugin-pinyin-search@17.1.0

@objectstack/plugin-reports@17.1.0

@objectstack/plugin-webhooks@17.1.0

@objectstack/service-analytics@17.1.0

@objectstack/service-cache@17.1.0

@objectstack/service-cluster@17.1.0

@objectstack/service-cluster-redis@17.1.0

@objectstack/service-i18n@17.1.0

@objectstack/service-job@17.1.0

@objectstack/service-knowledge@17.1.0

@objectstack/service-package@17.1.0

@objectstack/service-queue@17.1.0

@objectstack/service-realtime@17.1.0

@objectstack/service-settings@17.1.0

@objectstack/service-sms@17.1.0

@objectstack/service-storage@17.1.0

@objectstack/trigger-api@17.1.0

@objectstack/trigger-record-change@17.1.0

@objectstack/trigger-schedule@17.1.0

@objectstack/verify@17.1.0

@objectstack/sdui-parser@17.1.0

@objectstack/example-crm@4.0.93

@objectstack/example-showcase@0.3.15

@objectstack/example-todo@4.0.93

@objectstack/example-embed-objectql@0.0.33

@objectstack/dogfood@0.0.41

@objectstack/downstream-contract@0.0.39

@objectstack/http-conformance@0.1.1

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
objectstack	Ignored		Aug 16, 2026 7:14am

[os-zhuang]

⚠️ PM — hold this release: one incoming changeset carries provably wrong commit attributions

Not a request to close or rework this PR — a timing flag, because merging it consumes changesets and this one would freeze a known-wrong record into the published CHANGELOG.

The changeset: .changeset/console-82a94170c405.md, arriving via #9393 (currently head of a five-deep queue chain, so expect it on main shortly).

What's wrong with it: its per-entry commit attribution table pins 36 of 119 entries (30%) to a single commit, 183d09b78 — which is retire(studio): drop the canonical page:header icon field (#4794) and touches exactly one .changeset/ file, tidy-buttons-repeat.md. It carries none of the 36. Two entries traced to their real authoring commits:

• "Remove the retired striped / bordered / virtualScroll list-view surface" → really f1d4748c6
• "<PageHeader> retires the legacy description prop" → really f923b7cfa

The body's range arithmetic is also in dispute (110 vs 137 non-merge commits over the identical range, per a second independent derivation of the same range in #9398).

I let #9393 land deliberately rather than dequeue it — its functional payload, the .objectui-sha bump, is correct, and pulling it would invalidate four other PRs' queue runs. A .changeset/*.md is consumed at release time, not merge time, so the narrative stays correctable on disk — provided this PR doesn't merge first.

The correction is dispatched on the #9398 branch (a re-derivation from scratch, not a port of either existing table). Full measurement: #9393 and #9398.

Releases are human-gated, which is exactly why this is a comment and not an action — the decision is yours. If the release needs to go out before the correction is ready, the alternative is to drop or stub that one changeset's attribution table rather than publish it as-is; say so and I'll have it prepared that way instead.

I'll post here when the correction lands.

---

Generated by Claude Code

[os-zhuang]

✅ Release hold LIFTED — the changeset correction has landed and is verified on main

Following up my hold from 23:2xZ. #9398 landed as 1b93550afd, and the corrected .changeset/console-82a94170c405.md is verified on origin/main by artifact, not from the merge notice:

	before (#9393, landed 23:20Z)	after (#9398, landed)
max entries credited to one sha	36 (30% of the file)	2
183d09b78 occurrences	36	1
total bullet entries	119	131
striped/bordered/virtualScroll →	183d09b78 ✗	f1d4748c6 ✓
<PageHeader> description →	183d09b78 ✗	f923b7cfa ✓

The positive control is the part worth reading. 183d09b78 now appears exactly once — which is the correct answer, not zero. It is a real commit in the range and it does carry exactly one changeset (tidy-buttons-repeat.md). The sink collapsed to its true value rather than being scrubbed, which is what distinguishes a corrected derivation from an over-corrected one.

Release content is unchanged — only attribution moved

This was checked, not assumed. All 100 landed entry texts (sha suffix stripped, compared as sorted sets via comm) are present in the 131-entry re-derivation: zero content loss. Same 121 releasing of 166 changesets, same 10 breaking, same 45 release-nothing, same resolved bump level. The human-authored ADR-0087 disposition was carried over verbatim rather than re-litigated.

So nothing about what releases changed between my hold and this lift. This PR can proceed whenever you want it to.

The root cause is filed, and it is a repo-owned tool — worth reading before the next pin bump

scripts/bump-objectui.sh guards its range walk with:

if [[ "$OLD_SHA" != "<none>" ]] && git -C "$OBJECTUI_ROOT" cat-file -e "${OLD_SHA}^{commit}" 2>/dev/null; then
  RANGE_OK=1
fi

That tests object presence, not walk completeness. In a shallow objectui clone whose graft boundary falls inside the pin range, OLD_SHA is present, so RANGE_OK=1 — and the honest degraded path immediately below it, which exists, is correctly written, and cites #4731's "a degraded list and a complete one must never look alike", is never reached. The grafted boundary commit is parentless, so it is diffed against the empty tree and credited with every .changeset/*.md in its tree.

Proven two independent ways: by arithmetic identity — the range is 191 commits, 183d09b78 sits at index 110 and 75444e38a at index 137, exactly the commit counts the two bad records reported, so each record's count was the position of its own sink — and by exact reproduction, writing a boundary into .git/shallow and regenerating a byte-identical bad artifact on demand.

Filed as #9408, unassigned. ⚠️ Until it is repaired, any console pin bump run from a shallow objectui clone reproduces this silently — the artifact looks complete and carries no marker. I'd recommend #9408 lands before the next pin bump; its cheap mitigation alone (no commit may be credited with more added changesets than git show --name-only attributes to it) would have caught all three known-bad runs.

That is a heads-up for the next bump, not a condition on this release. The hold is lifted.

---

Generated by Claude Code