chore: version packages#2768
Merged
Merged
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 10, 2026 10:06
92c8353 to
33cea37
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 10, 2026 10:33
33cea37 to
10141bf
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 10, 2026 10:45
10141bf to
d28ce76
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/lint@14.1.0
Minor Changes
5a8465f: SLA escalation
escalateTois position-first (ADR-0090 D3 follow-up to thepositionapprover type).ApprovalEscalationSchema.escalateTois documented as a position machine name or aspecific user id (was "User id, role, or manager level" — the same pre-D3 'role' trap the
positionapprover type fixed); the Studio xRef picker kind movesrole→position.escalateTonow expands position holders viasys_user_position∪ thesys_member.roletransition source (ADR-0057 D4) for both thereassignapprover hand-off and thenotifyaudience. An empty expansion falls back totreating the value as a literal user id, so configs naming a specific user keep working
unchanged. The audit trail keeps the authored target.
approval-escalation-reassign-no-targetwarning —escalation.action: 'reassign'with no
escalateTosilently degrades to a notify at runtime; the fix-it prescribes a positionor user id target (or
action: 'notify').Patch Changes
@objectstack/plugin-approvals@14.1.0
Minor Changes
5a8465f: SLA escalation
escalateTois position-first (ADR-0090 D3 follow-up to thepositionapprover type).ApprovalEscalationSchema.escalateTois documented as a position machine name or aspecific user id (was "User id, role, or manager level" — the same pre-D3 'role' trap the
positionapprover type fixed); the Studio xRef picker kind movesrole→position.escalateTonow expands position holders viasys_user_position∪ thesys_member.roletransition source (ADR-0057 D4) for both thereassignapprover hand-off and thenotifyaudience. An empty expansion falls back totreating the value as a literal user id, so configs naming a specific user keep working
unchanged. The audit trail keeps the authored target.
approval-escalation-reassign-no-targetwarning —escalation.action: 'reassign'with no
escalateTosilently degrades to a notify at runtime; the fix-it prescribes a positionor user id target (or
action: 'notify').Patch Changes
@objectstack/hono@14.1.0
Patch Changes
@objectstack/account@14.1.0
Patch Changes
@objectstack/setup@14.1.0
Patch Changes
@objectstack/studio@14.1.0
Patch Changes
@objectstack/cli@14.1.0
Patch Changes
@objectstack/client@14.1.0
Patch Changes
@objectstack/client-react@14.1.0
Patch Changes
@objectstack/cloud-connection@14.1.0
Patch Changes
@objectstack/connector-mcp@14.1.0
Patch Changes
@objectstack/connector-openapi@14.1.0
Patch Changes
@objectstack/connector-rest@14.1.0
Patch Changes
@objectstack/connector-slack@14.1.0
Patch Changes
@objectstack/core@14.1.0
Patch Changes
@objectstack/formula@14.1.0
Patch Changes
@objectstack/mcp@14.1.0
Patch Changes
@objectstack/metadata@14.1.0
Patch Changes
@objectstack/metadata-core@14.1.0
Patch Changes
@objectstack/metadata-fs@14.1.0
Patch Changes
@objectstack/metadata-protocol@14.1.0
Patch Changes
@objectstack/objectql@14.1.0
Patch Changes
@objectstack/observability@14.1.0
Patch Changes
@objectstack/platform-objects@14.1.0
Patch Changes
@objectstack/driver-memory@14.1.0
Patch Changes
@objectstack/driver-mongodb@14.1.0
Patch Changes
@objectstack/driver-sql@14.1.0
Patch Changes
@objectstack/driver-sqlite-wasm@14.1.0
Patch Changes
@objectstack/embedder-openai@14.1.0
Patch Changes
@objectstack/knowledge-memory@14.1.0
Patch Changes
@objectstack/knowledge-ragflow@14.1.0
Patch Changes
@objectstack/plugin-audit@14.1.0
Patch Changes
@objectstack/plugin-auth@14.1.0
Patch Changes
@objectstack/plugin-dev@14.1.0
Patch Changes
@objectstack/plugin-email@14.1.0
Patch Changes
@objectstack/plugin-hono-server@14.1.0
Patch Changes
@objectstack/plugin-reports@14.1.0
Patch Changes
@objectstack/plugin-security@14.1.0
Patch Changes
@objectstack/plugin-sharing@14.1.0
Patch Changes
@objectstack/plugin-webhooks@14.1.0
Patch Changes
@objectstack/rest@14.1.0
Patch Changes
@objectstack/runtime@14.1.0
Patch Changes
@objectstack/service-analytics@14.1.0
Patch Changes
@objectstack/service-automation@14.1.0
Patch Changes
@objectstack/service-cache@14.1.0
Patch Changes
@objectstack/service-cluster@14.1.0
Patch Changes
@objectstack/service-cluster-redis@14.1.0
Patch Changes
@objectstack/service-datasource@14.1.0
Patch Changes
@objectstack/service-i18n@14.1.0
Patch Changes
@objectstack/service-job@14.1.0
Patch Changes
@objectstack/service-knowledge@14.1.0
Patch Changes
@objectstack/service-messaging@14.1.0
Patch Changes
@objectstack/service-package@14.1.0
Patch Changes
@objectstack/service-queue@14.1.0
Patch Changes
@objectstack/service-realtime@14.1.0
Patch Changes
@objectstack/service-settings@14.1.0
Patch Changes
@objectstack/service-storage@14.1.0
Patch Changes
@objectstack/spec@14.1.0
Patch Changes
5a8465f: SLA escalation
escalateTois position-first (ADR-0090 D3 follow-up to thepositionapprover type).ApprovalEscalationSchema.escalateTois documented as a position machine name or aspecific user id (was "User id, role, or manager level" — the same pre-D3 'role' trap the
positionapprover type fixed); the Studio xRef picker kind movesrole→position.escalateTonow expands position holders viasys_user_position∪ thesys_member.roletransition source (ADR-0057 D4) for both thereassignapprover hand-off and thenotifyaudience. An empty expansion falls back totreating the value as a literal user id, so configs naming a specific user keep working
unchanged. The audit trail keeps the authored target.
approval-escalation-reassign-no-targetwarning —escalation.action: 'reassign'with no
escalateTosilently degrades to a notify at runtime; the fix-it prescribes a positionor user id target (or
action: 'notify').7f8620b: Sync
PROTOCOL_VERSIONto14.0.0— the 14.0.0 release bumpedpackage.jsonbut the handshake constant still said 13, soprotocol-version.test.tsfailed on main for every PR. (Process note: the changesets Version PR cannot bump source constants; the protocol bump must accompany each major.)82ba3a6: docs(liveness): record the tenancy.strategy / crossTenantAccess removal decision ([spec] Remove tenancy.strategy + tenancy.crossTenantAccess at the next major — no requirement (owner decision) #2763)
Owner decision 2026-07-10: the platform has exactly two multi-tenancy
modes — per-tenant database (environment-level, zero object config) and
shared-DB organization row isolation (
tenancy.enabled+tenantField).Object-level isolation strategy has no requirement, so
strategyandcrossTenantAccessare slated for removal at the next spec major.Ledger notes + compile-time authorHints now state the decision and point
authors at the two real mechanisms.
@objectstack/trigger-api@14.1.0
Patch Changes
@objectstack/trigger-record-change@14.1.0
Patch Changes
@objectstack/trigger-schedule@14.1.0
Patch Changes
@objectstack/types@14.1.0
Patch Changes
@objectstack/verify@14.1.0
Patch Changes
@objectstack/console@14.1.0
create-objectstack@14.1.0
@objectstack/sdui-parser@14.1.0
objectstack-vscode@14.1.0
@objectstack/example-crm@4.0.79
Patch Changes
@objectstack/example-showcase@0.3.1
Patch Changes
@objectstack/example-todo@4.0.79
Patch Changes
@objectstack/example-embed-objectql@0.0.19
Patch Changes
@objectstack/dogfood@0.0.27
Patch Changes
@objectstack/downstream-contract@0.0.25
Patch Changes