Uh oh!
There was an error while loading. Please reload this page.
chore: release packages - #2130
Closed
github-actions[bot] wants to merge 1 commit into
Closed
Conversation
github-actionsBotforce-pushed
the
changeset-release/main
branch
from
July 1, 2026 05:06
160e208 to
46aae46CompareThe latest updates on your projects. Learn more about Vercel for GitHub. |
github-actionsBotforce-pushed
the
changeset-release/main
branch
15 times, most recently
from
July 2, 2026 15:17
2654d60 to
a9f6e9eComparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
July 2, 2026 15:32
a9f6e9e to
3b9b921Compare
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 freeto 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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm 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
@object-ui/console@11.3.1
Patch Changes
@object-ui/app-shell@11.3.1
Patch Changes
839f6c2: fix(studio): stamp packageId on pillar draft saves → true package-scoped publish
Studio pillar draft-saves now pass the active
packageId, so each draft row isstamped with its package binding (
sys_metadata.package_id) instead ofnull.This makes the package-scoped surfaces reliable: the top-bar count + Changes review
filter via
GET /meta/_drafts?packageId=, and Publish promotes exactly thispackage's drafts via
POST /packages/:id/publish-drafts(which matchesWHERE package_id = X). Replaces the previous "publish all pending" fallback thatwas only needed because null-package drafts couldn't be package-filtered or picked
up by publish-drafts.
5ba3d0e: feat(studio): WYSIWYG form-layout designer in the Data pillar
The Data pillar's Form view gains a 布局 (Layout) designer: the object's default
form rendered WYSIWYG, where an admin adds sections, drag-reorders fields within
a section and drags them across sections, and clicks a field to edit it in the
same protocol inspector the grid uses — one screen, no Data↔Interface switch.
Sections persist as the object's
fieldGroups, and membership/order asfield.groupplus field order, via the existing draft → publish. The drag/section chrome (dnd-kit)
is the only new code; the data model and all mutations reuse the existing, tested
object-fields-iohelpers (readGroups/addGroup/renameGroup/removeGroup/moveGroup/clearFieldGroup/groupEntries).Also fixes the Data pillar clobbering an in-progress draft when the metadata client
identity churned (e.g. toggling the live preview): the object baseline is now loaded
exactly once per selected object.
65efc01: feat(studio): package-level draft publish (replaces per-item publish)
The pillar Studio now publishes at the package level, not item-by-item. Edits
across Data / Automation / Interface accumulate as per-item drafts; the top bar
shows a pending-draft count, a 变更 (Changes) review, and one 发布 that
publishes all pending drafts in a single governed pass — reusing
usePublishAllDrafts(per-packagepublish-draftswith structure-before-seeds + theADR-0038 L3 probes, and by-reference for orphan / null-package drafts).
every other edit, so nothing goes live outside the one package publish.
and a draft-save refreshes the pending count.
Updated dependencies [5160832]
Updated dependencies [69d6b94]
Updated dependencies [243a9ba]
Updated dependencies [289be5b]
@object-ui/auth@11.3.1
Patch Changes
@object-ui/cli@11.3.1
Patch Changes
@object-ui/collaboration@11.3.1
Patch Changes
@object-ui/components@11.3.1
Patch Changes
@object-ui/core@11.3.1
Patch Changes
@object-ui/data-objectstack@11.3.1
Patch Changes
@object-ui/fields@11.3.1
Patch Changes
5160832: fix(fields): inline-edit relational fields with the standard picker (not a text box)
Inline cell editing reuses the form's field widgets, but the inline map
(
EDIT_WIDGETS) was a hand-maintained subset of the form's (fieldWidgetMap)and had drifted: lookup / master_detail / user / owner had perfectly good
form pickers yet fell back to a plain text box inline (you'd type a raw record
id). Wire them up —
lookup/master_detail→LookupField,user/owner→UserField, the exact widgets the form uses. They read the related-objectdataSource from
SchemaRendererContext(which the grid provides), so therecord picker opens, fetches, and selects inline.
To stop the two lists drifting again,
indexnow exportsFORM_FIELD_TYPESand a drift-guard test pins the contract: every form widget type must have an
explicit inline decision — an editor in
EDIT_WIDGETSor an entry in the newINLINE_EXCLUDED_FIELD_TYPES(computed/binary/heavy/container types, each witha reason). A future form widget can no longer silently become a text box (or a
missing editor) in the grid.
69d6b94: feat(fields): inline-edit structured-value fields (color, address, location, geolocation, code, qrcode)
Completes the inline-editor ↔ form-widget parity from the previous fix: the six
structured types that already had lightweight form widgets —
color,address,location,geolocation,code,qrcode— now edit inline withthose same widgets instead of being deferred. All are dependency-light (no map
or code-editor libraries) and use the standard
FieldWidgetProps. Verifiedinline on the field-zoo: color → a color picker, code → a textarea, the rest
their value editors. The drift-guard's exclusion set now contains only the
genuinely-non-inline types (computed, binary, heavy editors, containers).
243a9ba: fix(fields): inline lookup editor shows the selected record's name (not the "Select…" placeholder)
When editing a
lookup/master_detail/user/ownerfield inline in thedata grid, the
LookupFieldpicker showed the placeholder instead of thecurrent record's name. The grid requests
$expandfor visible referencecolumns, so a lookup cell's value arrives as the related record object
(
{ id, name }) rather than a bare id. The read cell (LookupCellRenderer)already resolves objects via the display-name path, but the inline editor only
matched primitive ids (
findOption(value)with a strict===), so anobject value never resolved — and the hydration effect made it worse by calling
findOne(referenceTo, <object>)with a bogus id.LookupFieldnow resolves an expanded-reference object directly into itsdisplay option (mirroring the read cell), skips the pointless per-object fetch,
and normalises object values to their id for option matching / multi-select
toggle / removal.
FieldEditWidgetalso renders the relational pickerscompactinline — the same single-line, borderless trigger the line-item griduses — so the record name shows in the trigger instead of a chip stacked
above a "Select…" button.
289be5b: fix(fields): align inline lookup value resolution with the read cell (external-id strings, tolerant id match)
Follow-up to Inline lookup editor: picker trigger shows placeholder instead of the selected record's name #2125.
LookupField's inline display now resolves every valueshape the read cell (
LookupCellRenderer) does:'{"externalId":"Website Relaunch"}')are parsed and shown by their external id, and excluded from the hydration
fetch (so we never
findOnewith a raw JSON string).recordToOptiongainedan
externalIdfallback for both the value and the label.String()-coerced fallback (findOptionLoose)resolves a numeric cell value against a string-keyed option (and vice versa),
matching the read cell's
String(a) === String(b)comparison. Only consultedwhen the strict match misses, so homogeneous option lists are unaffected.
Also adds explicit inline-editor tests for
user/ownerfields (theydelegate to
LookupFieldviaUserField), completing coverage for the fullrelational set wired inline in fix(fields): inline-edit relational fields with the standard picker (not a text box) #2122.
@object-ui/layout@11.3.1
Patch Changes
@object-ui/mobile@11.3.1
Patch Changes
@object-ui/permissions@11.3.1
Patch Changes
@object-ui/plugin-ai@11.3.1
Patch Changes
@object-ui/plugin-calendar@11.3.1
Patch Changes
@object-ui/plugin-charts@11.3.1
Patch Changes
@object-ui/plugin-chatbot@11.3.1
Patch Changes
@object-ui/plugin-dashboard@11.3.1
Patch Changes
@object-ui/plugin-designer@11.3.1
Patch Changes
@object-ui/plugin-detail@11.3.1
Patch Changes
@object-ui/plugin-editor@11.3.1
Patch Changes
@object-ui/plugin-form@11.3.1
Patch Changes
@object-ui/plugin-gantt@11.3.1
Patch Changes
@object-ui/plugin-grid@11.3.1
Patch Changes
@object-ui/plugin-kanban@11.3.1
Patch Changes
@object-ui/plugin-map@11.3.1
Patch Changes
@object-ui/plugin-markdown@11.3.1
Patch Changes
@object-ui/plugin-report@11.3.1
Patch Changes
@object-ui/plugin-timeline@11.3.1
Patch Changes
@object-ui/plugin-tree@11.3.1
Patch Changes
@object-ui/plugin-view@11.3.1
Patch Changes
@object-ui/providers@11.3.1
Patch Changes
@object-ui/react@11.3.1
Patch Changes
@object-ui/runner@11.3.1
Patch Changes
@object-ui/tenant@11.3.1
Patch Changes
@object-ui/create-plugin@11.3.1
@object-ui/i18n@11.3.1
@object-ui/plugin-list@11.3.1
@object-ui/react-runtime@11.3.1
@object-ui/sdui-parser@11.3.1
@object-ui/types@11.3.1
object-ui@11.3.1
Patch Changes