Uh oh!
There was an error while loading. Please reload this page.
chore: version packages - #1270
Closed
github-actions[bot] wants to merge 1 commit into
Closed
Conversation
github-actionsBotforce-pushed
the
changeset-release/main
branch
from
May 22, 2026 15:51
4451c28 to
3bd20c5CompareThe 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 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
@objectstack/metadata-core@5.1.0
Minor Changes
75f4ee6: feat(metadata): introduce
executionPinnedcapability for runtime version pinning (ADR-0009)Adds a new capability flag on the metadata type registry so that types whose runtime
transaction rows reference a specific historical version (flow, workflow, approval)
get unified pinning behavior — instead of every business table re-implementing its
own snapshot column.
MetadataTypeRegistryEntrySchemagainsexecutionPinned: boolean, enforcedinvariant
executionPinned ⇒ supportsVersioning.flow,workflow,approvalflipped toexecutionPinned: true.approvalalso corrected to
supportsVersioning: true(it was wronglyfalse).MetadataRepository.getByHash(ref, hash)added to the interface. Productionimplementation in
SysMetadataRepositoryresolves historical bodies throughsys_metadata_historykeyed by(organization_id, type, name, checksum).In-memory and FS repositories serve HEAD-only matches.
sys_metadata_historygains an index on(organization_id, type, name, checksum)to keep hash lookups O(log n).
HistoryCleanupManagerskips pinned types entirely (both age-based andcount-based retention) — pinned-type history must never be GC'd.
See
docs/adr/0009-execution-pinned-metadata.mdfor full rationale and thelist of rejected alternatives (no shared snapshot table, no inlined snapshot column).
@objectstack/platform-objects@5.1.0
Minor Changes
75f4ee6: feat(metadata): introduce
executionPinnedcapability for runtime version pinning (ADR-0009)Adds a new capability flag on the metadata type registry so that types whose runtime
transaction rows reference a specific historical version (flow, workflow, approval)
get unified pinning behavior — instead of every business table re-implementing its
own snapshot column.
MetadataTypeRegistryEntrySchemagainsexecutionPinned: boolean, enforcedinvariant
executionPinned ⇒ supportsVersioning.flow,workflow,approvalflipped toexecutionPinned: true.approvalalso corrected to
supportsVersioning: true(it was wronglyfalse).MetadataRepository.getByHash(ref, hash)added to the interface. Productionimplementation in
SysMetadataRepositoryresolves historical bodies throughsys_metadata_historykeyed by(organization_id, type, name, checksum).In-memory and FS repositories serve HEAD-only matches.
sys_metadata_historygains an index on(organization_id, type, name, checksum)to keep hash lookups O(log n).
HistoryCleanupManagerskips pinned types entirely (both age-based andcount-based retention) — pinned-type history must never be GC'd.
See
docs/adr/0009-execution-pinned-metadata.mdfor full rationale and thelist of rejected alternatives (no shared snapshot table, no inlined snapshot column).
823d559: Remove
sys_metadata_history.metadata_idcolumn.The column was originally a
Field.lookupFK intosys_metadata.id,then downgraded to plain
textduring the M1 history-writes work sothat DELETE tombstones could keep an orphaned ref. After M1 we
concluded the column carries no business value:
Audit-time joins use
(organization_id, type, name, version),which is already a UNIQUE composite key.
The physical row id is a database-internal detail with no logical
identity — it cannot follow an item through delete + recreate.
No code reader was ever added.
This release removes the column outright:
Dropped
metadata_idfromSysMetadataHistoryObject(
@objectstack/platform-objects).Dropped
metadataIdfromMetadataHistoryRecordSchema(
@objectstack/spec).SysMetadataRepository.put/deleteno longer write the column.Legacy
DatabaseLoader.createHistoryRecordno longer writes it;getHistoryRecord/queryHistoryfilter by(type, name)directly(no parent-row lookup needed).
MetadataHistoryCleanupmaxVersionspolicy groups by(type, name)instead ofmetadata_id.Migration: Drop the column from existing
sys_metadata_historytables in a follow-up SQL migration. Existing history rows remain
queryable since
(organization_id, type, name, version)is alreadythe canonical lookup key. No consumer code should be reading
metadata_id— if you are, switch to(organization_id, type, name, version).See ADR-0008 §14 for the full rationale.
Patch Changes
@objectstack/spec@5.1.0
Minor Changes
75f4ee6: feat(metadata): introduce
executionPinnedcapability for runtime version pinning (ADR-0009)Adds a new capability flag on the metadata type registry so that types whose runtime
transaction rows reference a specific historical version (flow, workflow, approval)
get unified pinning behavior — instead of every business table re-implementing its
own snapshot column.
MetadataTypeRegistryEntrySchemagainsexecutionPinned: boolean, enforcedinvariant
executionPinned ⇒ supportsVersioning.flow,workflow,approvalflipped toexecutionPinned: true.approvalalso corrected to
supportsVersioning: true(it was wronglyfalse).MetadataRepository.getByHash(ref, hash)added to the interface. Productionimplementation in
SysMetadataRepositoryresolves historical bodies throughsys_metadata_historykeyed by(organization_id, type, name, checksum).In-memory and FS repositories serve HEAD-only matches.
sys_metadata_historygains an index on(organization_id, type, name, checksum)to keep hash lookups O(log n).
HistoryCleanupManagerskips pinned types entirely (both age-based andcount-based retention) — pinned-type history must never be GC'd.
See
docs/adr/0009-execution-pinned-metadata.mdfor full rationale and thelist of rejected alternatives (no shared snapshot table, no inlined snapshot column).
823d559: Remove
sys_metadata_history.metadata_idcolumn.The column was originally a
Field.lookupFK intosys_metadata.id,then downgraded to plain
textduring the M1 history-writes work sothat DELETE tombstones could keep an orphaned ref. After M1 we
concluded the column carries no business value:
Audit-time joins use
(organization_id, type, name, version),which is already a UNIQUE composite key.
The physical row id is a database-internal detail with no logical
identity — it cannot follow an item through delete + recreate.
No code reader was ever added.
This release removes the column outright:
Dropped
metadata_idfromSysMetadataHistoryObject(
@objectstack/platform-objects).Dropped
metadataIdfromMetadataHistoryRecordSchema(
@objectstack/spec).SysMetadataRepository.put/deleteno longer write the column.Legacy
DatabaseLoader.createHistoryRecordno longer writes it;getHistoryRecord/queryHistoryfilter by(type, name)directly(no parent-row lookup needed).
MetadataHistoryCleanupmaxVersionspolicy groups by(type, name)instead ofmetadata_id.Migration: Drop the column from existing
sys_metadata_historytables in a follow-up SQL migration. Existing history rows remain
queryable since
(organization_id, type, name, version)is alreadythe canonical lookup key. No consumer code should be reading
metadata_id— if you are, switch to(organization_id, type, name, version).See ADR-0008 §14 for the full rationale.
@objectstack/account@5.1.0
Patch Changes
@objectstack/studio@5.1.0
Patch Changes
@objectstack/hono@5.1.0
Patch Changes
@objectstack/cli@5.1.0
Patch Changes
@objectstack/client@5.1.0
Patch Changes
@objectstack/client-react@5.1.0
Patch Changes
@objectstack/core@5.1.0
Patch Changes
@objectstack/formula@5.1.0
Patch Changes
@objectstack/metadata@5.1.0
Patch Changes
75f4ee6: feat(metadata): introduce
executionPinnedcapability for runtime version pinning (ADR-0009)Adds a new capability flag on the metadata type registry so that types whose runtime
transaction rows reference a specific historical version (flow, workflow, approval)
get unified pinning behavior — instead of every business table re-implementing its
own snapshot column.
MetadataTypeRegistryEntrySchemagainsexecutionPinned: boolean, enforcedinvariant
executionPinned ⇒ supportsVersioning.flow,workflow,approvalflipped toexecutionPinned: true.approvalalso corrected to
supportsVersioning: true(it was wronglyfalse).MetadataRepository.getByHash(ref, hash)added to the interface. Productionimplementation in
SysMetadataRepositoryresolves historical bodies throughsys_metadata_historykeyed by(organization_id, type, name, checksum).In-memory and FS repositories serve HEAD-only matches.
sys_metadata_historygains an index on(organization_id, type, name, checksum)to keep hash lookups O(log n).
HistoryCleanupManagerskips pinned types entirely (both age-based andcount-based retention) — pinned-type history must never be GC'd.
See
docs/adr/0009-execution-pinned-metadata.mdfor full rationale and thelist of rejected alternatives (no shared snapshot table, no inlined snapshot column).
823d559: Remove
sys_metadata_history.metadata_idcolumn.The column was originally a
Field.lookupFK intosys_metadata.id,then downgraded to plain
textduring the M1 history-writes work sothat DELETE tombstones could keep an orphaned ref. After M1 we
concluded the column carries no business value:
Audit-time joins use
(organization_id, type, name, version),which is already a UNIQUE composite key.
The physical row id is a database-internal detail with no logical
identity — it cannot follow an item through delete + recreate.
No code reader was ever added.
This release removes the column outright:
Dropped
metadata_idfromSysMetadataHistoryObject(
@objectstack/platform-objects).Dropped
metadataIdfromMetadataHistoryRecordSchema(
@objectstack/spec).SysMetadataRepository.put/deleteno longer write the column.Legacy
DatabaseLoader.createHistoryRecordno longer writes it;getHistoryRecord/queryHistoryfilter by(type, name)directly(no parent-row lookup needed).
MetadataHistoryCleanupmaxVersionspolicy groups by(type, name)instead ofmetadata_id.Migration: Drop the column from existing
sys_metadata_historytables in a follow-up SQL migration. Existing history rows remain
queryable since
(organization_id, type, name, version)is alreadythe canonical lookup key. No consumer code should be reading
metadata_id— if you are, switch to(organization_id, type, name, version).See ADR-0008 §14 for the full rationale.
Updated dependencies [75f4ee6]
Updated dependencies [823d559]
@objectstack/metadata-fs@5.1.0
Patch Changes
75f4ee6: feat(metadata): introduce
executionPinnedcapability for runtime version pinning (ADR-0009)Adds a new capability flag on the metadata type registry so that types whose runtime
transaction rows reference a specific historical version (flow, workflow, approval)
get unified pinning behavior — instead of every business table re-implementing its
own snapshot column.
MetadataTypeRegistryEntrySchemagainsexecutionPinned: boolean, enforcedinvariant
executionPinned ⇒ supportsVersioning.flow,workflow,approvalflipped toexecutionPinned: true.approvalalso corrected to
supportsVersioning: true(it was wronglyfalse).MetadataRepository.getByHash(ref, hash)added to the interface. Productionimplementation in
SysMetadataRepositoryresolves historical bodies throughsys_metadata_historykeyed by(organization_id, type, name, checksum).In-memory and FS repositories serve HEAD-only matches.
sys_metadata_historygains an index on(organization_id, type, name, checksum)to keep hash lookups O(log n).
HistoryCleanupManagerskips pinned types entirely (both age-based andcount-based retention) — pinned-type history must never be GC'd.
See
docs/adr/0009-execution-pinned-metadata.mdfor full rationale and thelist of rejected alternatives (no shared snapshot table, no inlined snapshot column).
Updated dependencies [75f4ee6]
@objectstack/objectql@5.1.0
Patch Changes
75f4ee6: feat(metadata): introduce
executionPinnedcapability for runtime version pinning (ADR-0009)Adds a new capability flag on the metadata type registry so that types whose runtime
transaction rows reference a specific historical version (flow, workflow, approval)
get unified pinning behavior — instead of every business table re-implementing its
own snapshot column.
MetadataTypeRegistryEntrySchemagainsexecutionPinned: boolean, enforcedinvariant
executionPinned ⇒ supportsVersioning.flow,workflow,approvalflipped toexecutionPinned: true.approvalalso corrected to
supportsVersioning: true(it was wronglyfalse).MetadataRepository.getByHash(ref, hash)added to the interface. Productionimplementation in
SysMetadataRepositoryresolves historical bodies throughsys_metadata_historykeyed by(organization_id, type, name, checksum).In-memory and FS repositories serve HEAD-only matches.
sys_metadata_historygains an index on(organization_id, type, name, checksum)to keep hash lookups O(log n).
HistoryCleanupManagerskips pinned types entirely (both age-based andcount-based retention) — pinned-type history must never be GC'd.
See
docs/adr/0009-execution-pinned-metadata.mdfor full rationale and thelist of rejected alternatives (no shared snapshot table, no inlined snapshot column).
823d559: Remove
sys_metadata_history.metadata_idcolumn.The column was originally a
Field.lookupFK intosys_metadata.id,then downgraded to plain
textduring the M1 history-writes work sothat DELETE tombstones could keep an orphaned ref. After M1 we
concluded the column carries no business value:
Audit-time joins use
(organization_id, type, name, version),which is already a UNIQUE composite key.
The physical row id is a database-internal detail with no logical
identity — it cannot follow an item through delete + recreate.
No code reader was ever added.
This release removes the column outright:
Dropped
metadata_idfromSysMetadataHistoryObject(
@objectstack/platform-objects).Dropped
metadataIdfromMetadataHistoryRecordSchema(
@objectstack/spec).SysMetadataRepository.put/deleteno longer write the column.Legacy
DatabaseLoader.createHistoryRecordno longer writes it;getHistoryRecord/queryHistoryfilter by(type, name)directly(no parent-row lookup needed).
MetadataHistoryCleanupmaxVersionspolicy groups by(type, name)instead ofmetadata_id.Migration: Drop the column from existing
sys_metadata_historytables in a follow-up SQL migration. Existing history rows remain
queryable since
(organization_id, type, name, version)is alreadythe canonical lookup key. No consumer code should be reading
metadata_id— if you are, switch to(organization_id, type, name, version).See ADR-0008 §14 for the full rationale.
Updated dependencies [75f4ee6]
Updated dependencies [823d559]
@objectstack/observability@5.1.0
Patch Changes
@objectstack/driver-memory@5.1.0
Patch Changes
@objectstack/driver-mongodb@5.1.0
Patch Changes
@objectstack/driver-sql@5.1.0
Patch Changes
@objectstack/driver-turso@5.1.0
Patch Changes
@objectstack/plugin-approvals@5.1.0
Patch Changes
@objectstack/plugin-audit@5.1.0
Patch Changes
@objectstack/plugin-auth@5.1.0
Patch Changes
@objectstack/plugin-dev@5.1.0
Patch Changes
@objectstack/plugin-email@5.1.0
Patch Changes
@objectstack/plugin-hono-server@5.1.0
Patch Changes
@objectstack/plugin-mcp-server@5.1.0
Patch Changes
@objectstack/plugin-msw@5.1.0
Patch Changes
@objectstack/plugin-reports@5.1.0
Patch Changes
@objectstack/plugin-security@5.1.0
Patch Changes
@objectstack/plugin-sharing@5.1.0
Patch Changes
@objectstack/plugin-webhooks@5.1.0
Patch Changes
@objectstack/rest@5.1.0
Patch Changes
@objectstack/runtime@5.1.0
Patch Changes
@objectstack/service-ai@5.1.0
Patch Changes
@objectstack/service-analytics@5.1.0
Patch Changes
@objectstack/service-automation@5.1.0
Patch Changes
@objectstack/service-cache@5.1.0
Patch Changes
@objectstack/service-feed@5.1.0
Patch Changes
@objectstack/service-i18n@5.1.0
Patch Changes
@objectstack/service-job@5.1.0
Patch Changes
@objectstack/service-package@5.1.0
Patch Changes
@objectstack/service-queue@5.1.0
Patch Changes
@objectstack/service-realtime@5.1.0
Patch Changes
@objectstack/service-settings@5.1.0
Patch Changes
@objectstack/service-storage@5.1.0
Patch Changes
@objectstack/types@5.1.0
Patch Changes
@objectstack/console@5.1.0
@objectstack/express@5.1.0
@objectstack/fastify@5.1.0
@objectstack/nestjs@5.1.0
@objectstack/nextjs@5.1.0
@objectstack/nuxt@5.1.0
@objectstack/sveltekit@5.1.0
create-objectstack@5.1.0
objectstack-vscode@5.1.0
@objectstack/example-crm@4.0.10
Patch Changes
@example/app-todo@4.0.10
Patch Changes