chore: version packages#2825
Closed
github-actions[bot] wants to merge 1 commit into
Closed
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 11, 2026 03:39
139828f to
c0bb489
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 11, 2026 03:54
c0bb489 to
6179547
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 11, 2026 05:07
6179547 to
7fc4939
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 11, 2026 07:39
7fc4939 to
7d4a83a
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 11, 2026 07:59
7d4a83a to
2109b0e
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 11, 2026 09:18
2109b0e to
142bf59
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 11, 2026 09:26
142bf59 to
09a401c
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 11, 2026 10:39
09a401c to
922adb1
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 11, 2026 12:29
922adb1 to
a65f7fb
Compare
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
@objectstack/cli@14.5.0
Minor Changes
526805e: ADR-0057 data-lifecycle follow-ups (ADR-0057 data lifecycle follow-ups: retire per-plugin sweepers, dev telemetry datasource + db:clean, Studio surface, PG rotation (tracking) #2834): the per-plugin retention sweepers are retired, telemetry separation goes live in dev, and the lifecycle contract reaches the Studio.
JobRunRetention/NotificationRetentionand theretentionDays/retentionSweepMsoptions onJobServicePlugin/MessagingServicePluginare removed. The platform LifecycleService enforces the same windows from thelifecycledeclarations (sys_job_run30d, notification pipeline 90d); tune them at runtime via thelifecyclesettings namespace (retention_overrides, tenant-scoped).sys_automation_runno longer declares a blanket 30d lifecycle retention — that table interleaves live SUSPENDED runs (an approval may stay paused for months) with terminal history, and a blanket age reap could strand in-flight approvals. Bounding stays with the automation store's terminal-only sweep.objectstack devnow provisions a dedicatedtelemetrydatasource (<primary>.telemetry.db) for file-backed SQLite primaries, so lifecycle-classed system data stops sharing the business dev DB (OS_TELEMETRY_DB=0opts out;OS_TELEMETRY_DB=<path>opts in anywhere). Newos db cleanruns the one-timeVACUUMthat lets legacy files adoptauto_vacuum=INCREMENTALand reports reclaimed bytes.lifecycleblock (class + retention/TTL/rotation/archive/reclaim); metadata-forms i18n bundles regenerated with curated zh-CN translations.Patch Changes
@objectstack/objectql@14.5.0
Minor Changes
33ebd34: ADR-0057 (ADR-0057 data lifecycle follow-ups: retire per-plugin sweepers, dev telemetry datasource + db:clean, Studio surface, PG rotation (tracking) #2834):
retention.onlyWhenstatus predicate — mixed tables can scope the age reap.lifecycle.retention.onlyWhen— a row filter (per-field equality or{ $in: [...] }) the retention window applies to; rows outside it are retained regardless of age. Rejected when combined with rotationstorage(shard DROPs ignore filters) orarchive(the Archiver moves rows by age alone).onlyWheninto every retention delete, including tenant-override passes.sys_automation_rundeclaresretention: { maxAge: '30d', onlyWhen: { status: { $in: ['completed', 'failed'] } } }and the platform Reaper owns it; suspended (paused) runs never match. The plugin's own sweep loop is retired:ObjectStoreSuspendedRunStore.pruneHistory, theDEFAULT_RUN_HISTORY_RETENTION_DAYSexport, and therunHistoryRetentionDays/runHistorySweepMsplugin options are removed (launch-window breaking-as-minor). The write-time per-flow overflow cap (runHistoryMaxPerFlow) stays.Patch Changes
@objectstack/platform-objects@14.5.0
Minor Changes
6da03ee: feat(identity): open the standard Edit affordance on sys_user for profile fields (ADR-0092 D4)
sys_usernow setsuserActions: { edit: true }, so the generic row-editform is available (create / import / delete stay off). The two profile fields
(
name,image) are editable; every other column —email,role, banstate, phone, and all system-managed stamps — is marked
readonlyso thestandard edit form renders it non-editable.
This is safe because the server boundary is the identity write guard shipped
in the previous change (ADR-0092 D2): a user-context update to
sys_usermayonly touch
{name, image}regardless of what any form submits; everythingelse is stripped or rejected. The
readonlyflags here are UX only.The dedicated action dialogs are unaffected —
create_user/invite_user/set_user_rolereferenceemailandroleas action params (their owninputs), which do not inherit the field-level
readonlyand stay editable(verified in the running Console).
Note: the Console's record-form renderer must honor
userActions.edit+per-field
readonlyonmanagedBy:'better-auth'objects for the edit form tobe functional; that is an objectui-side change vendored via
objectui:refreshand tracked separately.
Patch Changes
526805e: ADR-0057 data-lifecycle follow-ups (ADR-0057 data lifecycle follow-ups: retire per-plugin sweepers, dev telemetry datasource + db:clean, Studio surface, PG rotation (tracking) #2834): the per-plugin retention sweepers are retired, telemetry separation goes live in dev, and the lifecycle contract reaches the Studio.
JobRunRetention/NotificationRetentionand theretentionDays/retentionSweepMsoptions onJobServicePlugin/MessagingServicePluginare removed. The platform LifecycleService enforces the same windows from thelifecycledeclarations (sys_job_run30d, notification pipeline 90d); tune them at runtime via thelifecyclesettings namespace (retention_overrides, tenant-scoped).sys_automation_runno longer declares a blanket 30d lifecycle retention — that table interleaves live SUSPENDED runs (an approval may stay paused for months) with terminal history, and a blanket age reap could strand in-flight approvals. Bounding stays with the automation store's terminal-only sweep.objectstack devnow provisions a dedicatedtelemetrydatasource (<primary>.telemetry.db) for file-backed SQLite primaries, so lifecycle-classed system data stops sharing the business dev DB (OS_TELEMETRY_DB=0opts out;OS_TELEMETRY_DB=<path>opts in anywhere). Newos db cleanruns the one-timeVACUUMthat lets legacy files adoptauto_vacuum=INCREMENTALand reports reclaimed bytes.lifecycleblock (class + retention/TTL/rotation/archive/reclaim); metadata-forms i18n bundles regenerated with curated zh-CN translations.Updated dependencies [526805e]
Updated dependencies [33ebd34]
@objectstack/plugin-auth@14.5.0
Minor Changes
a348394: feat(auth): identity write guard —
managedBy: 'better-auth'is now enforced at the engine (ADR-0092 D2/D3/D6)Every object whose schema declares
managedBy: 'better-auth'(sys_user,sys_member,sys_session,sys_api_key, …) is now protected by enginebeforeInsert/beforeUpdate/beforeDeletehooks registered byplugin-auth: user-context writes through the generic data path are
rejected fail-closed with
403 PERMISSION_DENIED, closing the hole where awildcard admin permission set could raw-write any identity column (including
emailand credential stamps) via the data API. Internal writes areunaffected — the better-auth adapter,
isSystemplugin/system contexts, andthe identity import keep working unchanged.
The only opening is a per-object update whitelist
(
registerManagedUpdateWhitelist(object, fields)): non-whitelisted fields arestripped from the payload, and a payload that strips to nothing throws. The
first registration ships here:
sys_user → { name, image }(pure profilefields), backed by the new shared
SYS_USER_PROFILE_EDIT_FIELDS/SYS_USER_IMPORT_UPDATE_FIELDSconstants — the import upsert's fielddiscipline is now derived from the same module (subset-by-construction, no
drift).
After a guarded profile edit, an
afterUpdatecompanion hook re-writes theuser's cached
{session, user}snapshots in better-auth's secondary storage(same TTL, mirror of better-auth's own
refreshUserSessions) so sessionreads stay coherent; it rewrites rather than deletes, and no-ops when no
secondary storage is wired.
Migration note: server-side scripts that previously updated identity tables
with a user execution context must either run with a system context
(
{ isSystem: true }) if they are genuinely internal, or move to thededicated auth endpoints (invite / create-user / set-user-password / ban /
better-auth APIs). Flows and automations that wrote non-profile
sys_usercolumns under a user identity are now filtered the same way.
5bced2f: feat(auth):
passwordPolicy: 'none'is the identity import's new default — import provisions identity, not credentialsPOST /api/v1/auth/admin/import-usersnow supports (and defaults to)passwordPolicy: 'none': accounts are created without a credential record(better-auth's optional-password create), so no password material is
generated, returned, or distributed at all. Users first sign in through a
channel — phone OTP, magic link, or a password-reset link — and the Console's
existing credential-less detection (
hasLocalPassword()→ set-initial-password)nudges them to set a password afterwards.
The
invitepolicy also no longer mints a throwaway password: it creates thesame credential-less account and sends the set-your-password invitation
(better-auth's reset flow creates the credential record on first set).
temporaryis unchanged and remains the fallback for deployments withoutemail/SMS infrastructure.
Breaking-ish note:
passwordPolicywas previously required — requests thatomitted it got a 400. They now succeed with the
nonebehavior.e2c05d6: feat(auth/i18n): localised, tenant-customisable phone SMS texts (feat(sms/i18n): 邀请/OTP 短信文案国际化（按用户 locale 渲染） #2815)
The OTP and invitation SMS bodies were hard-coded English. They now resolve
in two layers: a
sys_notification_templaterow for(auth.phone_otp | auth.phone_invite, channel 'sms', locale)— editable inSetup, seeded once with built-in en/zh rows, tenant edits never overwritten —
falling back to the bundled bilingual texts. The locale follows the
deployment default (
localization.localesetting, live-rebound); per-userlocale is deferred until
sys_usergrows a locale column. The OTP wordingis purpose-neutral (one provider template covers sign-in and reset, and the
SMS reveals nothing about what the code unlocks). Template lookups are
best-effort — an outage never blocks an OTP send — and the no-OTP-in-logs
red line is unchanged.
Patch Changes
@objectstack/service-automation@14.5.0
Minor Changes
33ebd34: ADR-0057 (ADR-0057 data lifecycle follow-ups: retire per-plugin sweepers, dev telemetry datasource + db:clean, Studio surface, PG rotation (tracking) #2834):
retention.onlyWhenstatus predicate — mixed tables can scope the age reap.lifecycle.retention.onlyWhen— a row filter (per-field equality or{ $in: [...] }) the retention window applies to; rows outside it are retained regardless of age. Rejected when combined with rotationstorage(shard DROPs ignore filters) orarchive(the Archiver moves rows by age alone).onlyWheninto every retention delete, including tenant-override passes.sys_automation_rundeclaresretention: { maxAge: '30d', onlyWhen: { status: { $in: ['completed', 'failed'] } } }and the platform Reaper owns it; suspended (paused) runs never match. The plugin's own sweep loop is retired:ObjectStoreSuspendedRunStore.pruneHistory, theDEFAULT_RUN_HISTORY_RETENTION_DAYSexport, and therunHistoryRetentionDays/runHistorySweepMsplugin options are removed (launch-window breaking-as-minor). The write-time per-flow overflow cap (runHistoryMaxPerFlow) stays.Patch Changes
526805e: ADR-0057 data-lifecycle follow-ups (ADR-0057 data lifecycle follow-ups: retire per-plugin sweepers, dev telemetry datasource + db:clean, Studio surface, PG rotation (tracking) #2834): the per-plugin retention sweepers are retired, telemetry separation goes live in dev, and the lifecycle contract reaches the Studio.
JobRunRetention/NotificationRetentionand theretentionDays/retentionSweepMsoptions onJobServicePlugin/MessagingServicePluginare removed. The platform LifecycleService enforces the same windows from thelifecycledeclarations (sys_job_run30d, notification pipeline 90d); tune them at runtime via thelifecyclesettings namespace (retention_overrides, tenant-scoped).sys_automation_runno longer declares a blanket 30d lifecycle retention — that table interleaves live SUSPENDED runs (an approval may stay paused for months) with terminal history, and a blanket age reap could strand in-flight approvals. Bounding stays with the automation store's terminal-only sweep.objectstack devnow provisions a dedicatedtelemetrydatasource (<primary>.telemetry.db) for file-backed SQLite primaries, so lifecycle-classed system data stops sharing the business dev DB (OS_TELEMETRY_DB=0opts out;OS_TELEMETRY_DB=<path>opts in anywhere). Newos db cleanruns the one-timeVACUUMthat lets legacy files adoptauto_vacuum=INCREMENTALand reports reclaimed bytes.lifecycleblock (class + retention/TTL/rotation/archive/reclaim); metadata-forms i18n bundles regenerated with curated zh-CN translations.Updated dependencies [526805e]
Updated dependencies [33ebd34]
@objectstack/service-job@14.5.0
Minor Changes
526805e: ADR-0057 data-lifecycle follow-ups (ADR-0057 data lifecycle follow-ups: retire per-plugin sweepers, dev telemetry datasource + db:clean, Studio surface, PG rotation (tracking) #2834): the per-plugin retention sweepers are retired, telemetry separation goes live in dev, and the lifecycle contract reaches the Studio.
JobRunRetention/NotificationRetentionand theretentionDays/retentionSweepMsoptions onJobServicePlugin/MessagingServicePluginare removed. The platform LifecycleService enforces the same windows from thelifecycledeclarations (sys_job_run30d, notification pipeline 90d); tune them at runtime via thelifecyclesettings namespace (retention_overrides, tenant-scoped).sys_automation_runno longer declares a blanket 30d lifecycle retention — that table interleaves live SUSPENDED runs (an approval may stay paused for months) with terminal history, and a blanket age reap could strand in-flight approvals. Bounding stays with the automation store's terminal-only sweep.objectstack devnow provisions a dedicatedtelemetrydatasource (<primary>.telemetry.db) for file-backed SQLite primaries, so lifecycle-classed system data stops sharing the business dev DB (OS_TELEMETRY_DB=0opts out;OS_TELEMETRY_DB=<path>opts in anywhere). Newos db cleanruns the one-timeVACUUMthat lets legacy files adoptauto_vacuum=INCREMENTALand reports reclaimed bytes.lifecycleblock (class + retention/TTL/rotation/archive/reclaim); metadata-forms i18n bundles regenerated with curated zh-CN translations.Patch Changes
@objectstack/service-messaging@14.5.0
Minor Changes
526805e: ADR-0057 data-lifecycle follow-ups (ADR-0057 data lifecycle follow-ups: retire per-plugin sweepers, dev telemetry datasource + db:clean, Studio surface, PG rotation (tracking) #2834): the per-plugin retention sweepers are retired, telemetry separation goes live in dev, and the lifecycle contract reaches the Studio.
JobRunRetention/NotificationRetentionand theretentionDays/retentionSweepMsoptions onJobServicePlugin/MessagingServicePluginare removed. The platform LifecycleService enforces the same windows from thelifecycledeclarations (sys_job_run30d, notification pipeline 90d); tune them at runtime via thelifecyclesettings namespace (retention_overrides, tenant-scoped).sys_automation_runno longer declares a blanket 30d lifecycle retention — that table interleaves live SUSPENDED runs (an approval may stay paused for months) with terminal history, and a blanket age reap could strand in-flight approvals. Bounding stays with the automation store's terminal-only sweep.objectstack devnow provisions a dedicatedtelemetrydatasource (<primary>.telemetry.db) for file-backed SQLite primaries, so lifecycle-classed system data stops sharing the business dev DB (OS_TELEMETRY_DB=0opts out;OS_TELEMETRY_DB=<path>opts in anywhere). Newos db cleanruns the one-timeVACUUMthat lets legacy files adoptauto_vacuum=INCREMENTALand reports reclaimed bytes.lifecycleblock (class + retention/TTL/rotation/archive/reclaim); metadata-forms i18n bundles regenerated with curated zh-CN translations.Patch Changes
@objectstack/spec@14.5.0
Minor Changes
526805e: ADR-0057 data-lifecycle follow-ups (ADR-0057 data lifecycle follow-ups: retire per-plugin sweepers, dev telemetry datasource + db:clean, Studio surface, PG rotation (tracking) #2834): the per-plugin retention sweepers are retired, telemetry separation goes live in dev, and the lifecycle contract reaches the Studio.
JobRunRetention/NotificationRetentionand theretentionDays/retentionSweepMsoptions onJobServicePlugin/MessagingServicePluginare removed. The platform LifecycleService enforces the same windows from thelifecycledeclarations (sys_job_run30d, notification pipeline 90d); tune them at runtime via thelifecyclesettings namespace (retention_overrides, tenant-scoped).sys_automation_runno longer declares a blanket 30d lifecycle retention — that table interleaves live SUSPENDED runs (an approval may stay paused for months) with terminal history, and a blanket age reap could strand in-flight approvals. Bounding stays with the automation store's terminal-only sweep.objectstack devnow provisions a dedicatedtelemetrydatasource (<primary>.telemetry.db) for file-backed SQLite primaries, so lifecycle-classed system data stops sharing the business dev DB (OS_TELEMETRY_DB=0opts out;OS_TELEMETRY_DB=<path>opts in anywhere). Newos db cleanruns the one-timeVACUUMthat lets legacy files adoptauto_vacuum=INCREMENTALand reports reclaimed bytes.lifecycleblock (class + retention/TTL/rotation/archive/reclaim); metadata-forms i18n bundles regenerated with curated zh-CN translations.33ebd34: ADR-0057 (ADR-0057 data lifecycle follow-ups: retire per-plugin sweepers, dev telemetry datasource + db:clean, Studio surface, PG rotation (tracking) #2834):
retention.onlyWhenstatus predicate — mixed tables can scope the age reap.lifecycle.retention.onlyWhen— a row filter (per-field equality or{ $in: [...] }) the retention window applies to; rows outside it are retained regardless of age. Rejected when combined with rotationstorage(shard DROPs ignore filters) orarchive(the Archiver moves rows by age alone).onlyWheninto every retention delete, including tenant-override passes.sys_automation_rundeclaresretention: { maxAge: '30d', onlyWhen: { status: { $in: ['completed', 'failed'] } } }and the platform Reaper owns it; suspended (paused) runs never match. The plugin's own sweep loop is retired:ObjectStoreSuspendedRunStore.pruneHistory, theDEFAULT_RUN_HISTORY_RETENTION_DAYSexport, and therunHistoryRetentionDays/runHistorySweepMsplugin options are removed (launch-window breaking-as-minor). The write-time per-flow overflow cap (runHistoryMaxPerFlow) stays.@objectstack/hono@14.5.0
Patch Changes
@objectstack/account@14.5.0
Patch Changes
@objectstack/setup@14.5.0
Patch Changes
@objectstack/studio@14.5.0
Patch Changes
@objectstack/client@14.5.0
Patch Changes
@objectstack/client-react@14.5.0
Patch Changes
@objectstack/cloud-connection@14.5.0
Patch Changes
@objectstack/connector-mcp@14.5.0
Patch Changes
@objectstack/connector-openapi@14.5.0
Patch Changes
@objectstack/connector-rest@14.5.0
Patch Changes
@objectstack/connector-slack@14.5.0
Patch Changes
@objectstack/console@14.5.0
Patch Changes
6da03ee: Console (objectui) refreshed to
5da9905b30fc. Frontend changes in this range:objectui range:
6fa8e6aeb67c...5da9905b30fc@objectstack/core@14.5.0
Patch Changes
@objectstack/formula@14.5.0
Patch Changes
@objectstack/lint@14.5.0
Patch Changes
@objectstack/mcp@14.5.0
Patch Changes
@objectstack/metadata@14.5.0
Patch Changes
@objectstack/metadata-core@14.5.0
Patch Changes
@objectstack/metadata-fs@14.5.0
Patch Changes
@objectstack/metadata-protocol@14.5.0
Patch Changes
@objectstack/observability@14.5.0
Patch Changes
@objectstack/driver-memory@14.5.0
Patch Changes
@objectstack/driver-mongodb@14.5.0
Patch Changes
@objectstack/driver-sql@14.5.0
Patch Changes
@objectstack/driver-sqlite-wasm@14.5.0
Patch Changes
@objectstack/embedder-openai@14.5.0
Patch Changes
@objectstack/knowledge-memory@14.5.0
Patch Changes
@objectstack/knowledge-ragflow@14.5.0
Patch Changes
@objectstack/plugin-approvals@14.5.0
Patch Changes
@objectstack/plugin-audit@14.5.0
Patch Changes
@objectstack/plugin-dev@14.5.0
Patch Changes
@objectstack/plugin-email@14.5.0
Patch Changes
@objectstack/plugin-hono-server@14.5.0
Patch Changes
6da03ee: fix(security):
/me/permissionsnow reflects permission-set ∩ identity-write-guard, matching real server enforcement (ADR-0057 D10)The
/api/v1/auth/me/permissionsper-object map merged each permission set'sexplicit
objectsentries most-permissively per key, but treated'*'andnamed objects as independent keys — so a wildcard "Modify/View All Data" grant
was never propagated into a per-object entry another set explicitly denied.
That made the client's field-level security STRICTER than the server's actual
enforcement (
PermissionEvaluator.checkObjectPermissionallows as soon as anyset grants, including via the
'*'modifyAll/viewAll super-user bypass, withno deny-wins).
The real effective answer for a user-context caller is
permission-set grant ∩ identity-write-guard policy, and the payload now computes both:foldWildcardSuperUserlifts each per-object entry's read/write bits whenthe merged
'*'is a super-user grant — fixing the false-NEGATIVE where aplatform admin (
admin_full_access'*': {modifyAllRecords}) who also holdsorganization_admin(explicit identity denies) resolved tosys_user.allowEdit:falseand a disabled edit form, though the serveraccepts the write (
PATCH /data/sys_user {name}→ 200).clampManagedObjectWritesre-clampsmanagedBy: 'better-auth'objects bytheir write affordance — fixing the false-POSITIVE the fold would otherwise
introduce: the identity write guard (ADR-0092 D2) blocks user-context writes
on identity tables except where the object opted in (
userActions.edit), sosys_member/sys_account/sys_sessionstayallowEdit:falsefor theadmin (read stays granted). Only
better-authobjects are clamped — theguard covers only them;
system/config/append-onlyobjects have no suchguard and their permission-set result stands.
Net: the Console's per-object FLS now equals real server enforcement — the
ADR-0092 D4
sys_userprofile-edit affordance is unblocked for platform admins(the guard still narrows the write to
{name, image}), and no other identitytable is shown as editable when the guard would reject it.
Updated dependencies [526805e]
Updated dependencies [33ebd34]
@objectstack/plugin-reports@14.5.0
Patch Changes
@objectstack/plugin-security@14.5.0
Patch Changes
@objectstack/plugin-sharing@14.5.0
Patch Changes
@objectstack/plugin-webhooks@14.5.0
Patch Changes
@objectstack/rest@14.5.0
Patch Changes
@objectstack/runtime@14.5.0
Patch Changes
@objectstack/service-analytics@14.5.0
Patch Changes
@objectstack/service-cache@14.5.0
Patch Changes
@objectstack/service-cluster@14.5.0
Patch Changes
@objectstack/service-cluster-redis@14.5.0
Patch Changes
@objectstack/service-datasource@14.5.0
Patch Changes
@objectstack/service-i18n@14.5.0
Patch Changes
@objectstack/service-knowledge@14.5.0
Patch Changes
@objectstack/service-package@14.5.0
Patch Changes
@objectstack/service-queue@14.5.0
Patch Changes
@objectstack/service-realtime@14.5.0
Patch Changes
@objectstack/service-settings@14.5.0
Patch Changes
@objectstack/service-sms@14.5.0
Patch Changes
@objectstack/service-storage@14.5.0
Patch Changes
@objectstack/trigger-api@14.5.0
Patch Changes
@objectstack/trigger-record-change@14.5.0
Patch Changes
@objectstack/trigger-schedule@14.5.0
Patch Changes
@objectstack/types@14.5.0
Patch Changes
@objectstack/verify@14.5.0
Patch Changes
create-objectstack@14.5.0
@objectstack/sdui-parser@14.5.0
objectstack-vscode@14.5.0
@objectstack/example-crm@4.0.83
Patch Changes
@objectstack/example-showcase@0.3.5
Patch Changes
@objectstack/example-todo@4.0.83
Patch Changes
@objectstack/example-embed-objectql@0.0.23
Patch Changes
@objectstack/dogfood@0.0.31
Patch Changes
@objectstack/downstream-contract@0.0.29
Patch Changes