chore: release packages#1401
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
6e3d81b to
4173719
Compare
|
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
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/app-shell@6.2.2
Patch Changes
c5821ce:
AiChatPageno longer PATCHes a client-side title-from-first-messageon the freshly-created conversation. The server (
@objectstack/service-ai≥ next minor) now generates a concise LLM-summarised title fire-and-forget
after the first assistant turn lands, and a client-side truncated title
would race that and win — pinning every conversation row to a 40-char
substring of the first user message instead of a real summary.
Drop the PATCH; bump the sidebar list a couple of times (2.5 s + 6 s)
to pick up the LLM title whenever the model finally responds.
3b35084: Fix: floating chatbot now replays persisted conversation history on mount.
The right-corner floating chatbot (
ConsoleFloatingChatbot) was passing onlyconversationIdto its inneruseObjectChat, dropping theinitialMessagesreturned by
useChatConversation. Backend persistence already worked — theserver-side
ai_conversation+ai_messagerows were created and survived apage refresh — but the UI started each session with just the static "welcome"
bubble, making users believe their history had been lost.
Now matches the
/ai/:conversationIdfull-page chat: history is hydratedinto the chat surface, and the welcome bubble is suppressed when prior turns
exist (showing it above real user/assistant turns is confusing).
Updated dependencies [a66f788]
@object-ui/auth@6.2.2
Patch Changes
@object-ui/cli@6.2.2
Patch Changes
@object-ui/collaboration@6.2.2
Patch Changes
@object-ui/components@6.2.2
Patch Changes
@object-ui/core@6.2.2
Patch Changes
@object-ui/data-objectstack@6.2.2
Patch Changes
@object-ui/fields@6.2.2
Patch Changes
@object-ui/layout@6.2.2
Patch Changes
@object-ui/mobile@6.2.2
Patch Changes
@object-ui/permissions@6.2.2
Patch Changes
@object-ui/plugin-ai@6.2.2
Patch Changes
@object-ui/plugin-calendar@6.2.2
Patch Changes
@object-ui/plugin-charts@6.2.2
Patch Changes
@object-ui/plugin-chatbot@6.2.2
Patch Changes
@object-ui/plugin-dashboard@6.2.2
Patch Changes
@object-ui/plugin-designer@6.2.2
Patch Changes
@object-ui/plugin-editor@6.2.2
Patch Changes
@object-ui/plugin-form@6.2.2
Patch Changes
@object-ui/plugin-gantt@6.2.2
Patch Changes
@object-ui/plugin-grid@6.2.2
Patch Changes
@object-ui/plugin-kanban@6.2.2
Patch Changes
@object-ui/plugin-map@6.2.2
Patch Changes
@object-ui/plugin-markdown@6.2.2
Patch Changes
@object-ui/plugin-report@6.2.2
Patch Changes
@object-ui/plugin-timeline@6.2.2
Patch Changes
@object-ui/plugin-view@6.2.2
Patch Changes
@object-ui/plugin-workflow@6.2.2
Patch Changes
@object-ui/providers@6.2.2
Patch Changes
@object-ui/react@6.2.2
Patch Changes
a66f788: fix(react): preserve
data-obj-schema-invalidflag across re-rendersSchemaRendererruns a post-mountforceUpdateto pick up lazy pluginregistrations. The dev-mode validator was deduping via a
WeakSetthatalways returned
valid: trueon the second call, which stripped thedata-obj-schema-invalidattribute on the immediate re-render. Theresult and the "warn-once" tracking are now stored separately: a
WeakMapcaches the validation outcome (so the visual flag is stable),while a
WeakSetcontinues to dedupeconsole.warnoutput.@object-ui/runner@6.2.2
Patch Changes
@object-ui/tenant@6.2.2
Patch Changes
@object-ui/console@6.2.2
@object-ui/studio@6.2.2
@object-ui/create-plugin@6.2.2
@object-ui/i18n@6.2.2
@object-ui/plugin-detail@6.2.2
@object-ui/plugin-list@6.2.2
@object-ui/types@6.2.2
object-ui@6.2.2
Patch Changes