Uh oh!
There was an error while loading. Please reload this page.
chore: version packages - #1274
Closed
github-actions[bot] wants to merge 1 commit into
Closed
Conversation
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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@6.0.0
Major Changes
944f187: # v5.0 —
project→environmenthard renameThe runtime concept previously called "project" (per-tenant business
workspace; Org → Project → Branch hierarchy; per-project ObjectKernel,
per-project DB, per-project artifact) is now uniformly called
"environment".
This is a hard rename with no aliases, deprecation shims, or compatibility
layer. Upgrade requires a coordinated update of CLI, runtime, server, and any
clients calling the REST API.
Breaking changes
CLI
--project/-p→--environment/-e(os publish,os rollback)--project-id→--environment-id(os dev)proj_local→env_local.OS_PROJECT_ID→OS_ENVIRONMENT_ID.os projects ...→os environments ...(
bind,create,list,show,switch).activeProjectId→activeEnvironmentId.HTTP / REST
/api/v1/projects/:projectId/...→/api/v1/environments/:environmentId/..../api/v1/cloud/projects/...→/api/v1/cloud/environments/...(including
/cloud/environments/:id/artifact,/cloud/environments/:id/metadata,/cloud/environments/:id/credentials/rotate, etc.).X-Project-Id(and lowercasex-project-id) →X-Environment-Id(
x-environment-id).req.params.projectId→req.params.environmentId.environmentIdend-to-end.Runtime / spec
createSystemProjectPlugin→createSystemEnvironmentPluginSYSTEM_PROJECT_ID→SYSTEM_ENVIRONMENT_IDProjectArtifactSchema→EnvironmentArtifactSchemaPROJECT_ARTIFACT_SCHEMA_VERSION→ENVIRONMENT_ARTIFACT_SCHEMA_VERSIONObjectOSProjectPlugin→ObjectOSEnvironmentPlugincreateSingleProjectPlugin→createSingleEnvironmentPlugincom.objectstack.runtime.objectos-project→objectos-environmentcom.objectstack.studio.single-project→single-environmentcom.objectstack.multi-project→multi-environmentcom.objectstack.runtime.system-project→system-environmentprovisionSystemProject→provisionSystemEnvironment.Database / schemas
sys_metadataandsys_metadata_history:project_id→environment_id.sys_activity:project_id→environment_id(plus index).sys_project→sys_environment(lookup targets),
sys_project_member→sys_environment_member,sys_project_credential→sys_environment_credential.active_project_id→active_environment_id.packages/spec/json-schema/system/:ProjectArtifact*.json→EnvironmentArtifact*.json(regenerated at build).Automatic forward migration
A new migration
migrateProjectIdToEnvironmentId(
packages/metadata/src/migrations/migrate-project-id-to-environment-id.ts)auto-runs from
DatabaseLoader.ensureSchema()on bootstrap and rewrites anyexisting
project_idcolumn onsys_metadata/sys_metadata_historytoenvironment_id(idempotent, best-effort). Existing rows are preserved.The legacy reverse migration
migrateEnvIdToProjectIdis retained verbatimfor historical / disaster-recovery use; it is not auto-run.
Migration guide
If you maintain a Cloud control-plane deployment, the
cloudrepository mustbe updated in lockstep to pick up the new plugin identifier strings
(
single-environment,multi-environment,objectos-environment).Patch Changes
@objectstack/client@6.0.0
Major Changes
944f187: # v5.0 —
project→environmenthard renameThe runtime concept previously called "project" (per-tenant business
workspace; Org → Project → Branch hierarchy; per-project ObjectKernel,
per-project DB, per-project artifact) is now uniformly called
"environment".
This is a hard rename with no aliases, deprecation shims, or compatibility
layer. Upgrade requires a coordinated update of CLI, runtime, server, and any
clients calling the REST API.
Breaking changes
CLI
--project/-p→--environment/-e(os publish,os rollback)--project-id→--environment-id(os dev)proj_local→env_local.OS_PROJECT_ID→OS_ENVIRONMENT_ID.os projects ...→os environments ...(
bind,create,list,show,switch).activeProjectId→activeEnvironmentId.HTTP / REST
/api/v1/projects/:projectId/...→/api/v1/environments/:environmentId/..../api/v1/cloud/projects/...→/api/v1/cloud/environments/...(including
/cloud/environments/:id/artifact,/cloud/environments/:id/metadata,/cloud/environments/:id/credentials/rotate, etc.).X-Project-Id(and lowercasex-project-id) →X-Environment-Id(
x-environment-id).req.params.projectId→req.params.environmentId.environmentIdend-to-end.Runtime / spec
createSystemProjectPlugin→createSystemEnvironmentPluginSYSTEM_PROJECT_ID→SYSTEM_ENVIRONMENT_IDProjectArtifactSchema→EnvironmentArtifactSchemaPROJECT_ARTIFACT_SCHEMA_VERSION→ENVIRONMENT_ARTIFACT_SCHEMA_VERSIONObjectOSProjectPlugin→ObjectOSEnvironmentPlugincreateSingleProjectPlugin→createSingleEnvironmentPlugincom.objectstack.runtime.objectos-project→objectos-environmentcom.objectstack.studio.single-project→single-environmentcom.objectstack.multi-project→multi-environmentcom.objectstack.runtime.system-project→system-environmentprovisionSystemProject→provisionSystemEnvironment.Database / schemas
sys_metadataandsys_metadata_history:project_id→environment_id.sys_activity:project_id→environment_id(plus index).sys_project→sys_environment(lookup targets),
sys_project_member→sys_environment_member,sys_project_credential→sys_environment_credential.active_project_id→active_environment_id.packages/spec/json-schema/system/:ProjectArtifact*.json→EnvironmentArtifact*.json(regenerated at build).Automatic forward migration
A new migration
migrateProjectIdToEnvironmentId(
packages/metadata/src/migrations/migrate-project-id-to-environment-id.ts)auto-runs from
DatabaseLoader.ensureSchema()on bootstrap and rewrites anyexisting
project_idcolumn onsys_metadata/sys_metadata_historytoenvironment_id(idempotent, best-effort). Existing rows are preserved.The legacy reverse migration
migrateEnvIdToProjectIdis retained verbatimfor historical / disaster-recovery use; it is not auto-run.
Migration guide
If you maintain a Cloud control-plane deployment, the
cloudrepository mustbe updated in lockstep to pick up the new plugin identifier strings
(
single-environment,multi-environment,objectos-environment).Patch Changes
@objectstack/metadata@6.0.0
Major Changes
944f187: # v5.0 —
project→environmenthard renameThe runtime concept previously called "project" (per-tenant business
workspace; Org → Project → Branch hierarchy; per-project ObjectKernel,
per-project DB, per-project artifact) is now uniformly called
"environment".
This is a hard rename with no aliases, deprecation shims, or compatibility
layer. Upgrade requires a coordinated update of CLI, runtime, server, and any
clients calling the REST API.
Breaking changes
CLI
--project/-p→--environment/-e(os publish,os rollback)--project-id→--environment-id(os dev)proj_local→env_local.OS_PROJECT_ID→OS_ENVIRONMENT_ID.os projects ...→os environments ...(
bind,create,list,show,switch).activeProjectId→activeEnvironmentId.HTTP / REST
/api/v1/projects/:projectId/...→/api/v1/environments/:environmentId/..../api/v1/cloud/projects/...→/api/v1/cloud/environments/...(including
/cloud/environments/:id/artifact,/cloud/environments/:id/metadata,/cloud/environments/:id/credentials/rotate, etc.).X-Project-Id(and lowercasex-project-id) →X-Environment-Id(
x-environment-id).req.params.projectId→req.params.environmentId.environmentIdend-to-end.Runtime / spec
createSystemProjectPlugin→createSystemEnvironmentPluginSYSTEM_PROJECT_ID→SYSTEM_ENVIRONMENT_IDProjectArtifactSchema→EnvironmentArtifactSchemaPROJECT_ARTIFACT_SCHEMA_VERSION→ENVIRONMENT_ARTIFACT_SCHEMA_VERSIONObjectOSProjectPlugin→ObjectOSEnvironmentPlugincreateSingleProjectPlugin→createSingleEnvironmentPlugincom.objectstack.runtime.objectos-project→objectos-environmentcom.objectstack.studio.single-project→single-environmentcom.objectstack.multi-project→multi-environmentcom.objectstack.runtime.system-project→system-environmentprovisionSystemProject→provisionSystemEnvironment.Database / schemas
sys_metadataandsys_metadata_history:project_id→environment_id.sys_activity:project_id→environment_id(plus index).sys_project→sys_environment(lookup targets),
sys_project_member→sys_environment_member,sys_project_credential→sys_environment_credential.active_project_id→active_environment_id.packages/spec/json-schema/system/:ProjectArtifact*.json→EnvironmentArtifact*.json(regenerated at build).Automatic forward migration
A new migration
migrateProjectIdToEnvironmentId(
packages/metadata/src/migrations/migrate-project-id-to-environment-id.ts)auto-runs from
DatabaseLoader.ensureSchema()on bootstrap and rewrites anyexisting
project_idcolumn onsys_metadata/sys_metadata_historytoenvironment_id(idempotent, best-effort). Existing rows are preserved.The legacy reverse migration
migrateEnvIdToProjectIdis retained verbatimfor historical / disaster-recovery use; it is not auto-run.
Migration guide
If you maintain a Cloud control-plane deployment, the
cloudrepository mustbe updated in lockstep to pick up the new plugin identifier strings
(
single-environment,multi-environment,objectos-environment).Patch Changes
@objectstack/platform-objects@6.0.0
Major Changes
944f187: # v5.0 —
project→environmenthard renameThe runtime concept previously called "project" (per-tenant business
workspace; Org → Project → Branch hierarchy; per-project ObjectKernel,
per-project DB, per-project artifact) is now uniformly called
"environment".
This is a hard rename with no aliases, deprecation shims, or compatibility
layer. Upgrade requires a coordinated update of CLI, runtime, server, and any
clients calling the REST API.
Breaking changes
CLI
--project/-p→--environment/-e(os publish,os rollback)--project-id→--environment-id(os dev)proj_local→env_local.OS_PROJECT_ID→OS_ENVIRONMENT_ID.os projects ...→os environments ...(
bind,create,list,show,switch).activeProjectId→activeEnvironmentId.HTTP / REST
/api/v1/projects/:projectId/...→/api/v1/environments/:environmentId/..../api/v1/cloud/projects/...→/api/v1/cloud/environments/...(including
/cloud/environments/:id/artifact,/cloud/environments/:id/metadata,/cloud/environments/:id/credentials/rotate, etc.).X-Project-Id(and lowercasex-project-id) →X-Environment-Id(
x-environment-id).req.params.projectId→req.params.environmentId.environmentIdend-to-end.Runtime / spec
createSystemProjectPlugin→createSystemEnvironmentPluginSYSTEM_PROJECT_ID→SYSTEM_ENVIRONMENT_IDProjectArtifactSchema→EnvironmentArtifactSchemaPROJECT_ARTIFACT_SCHEMA_VERSION→ENVIRONMENT_ARTIFACT_SCHEMA_VERSIONObjectOSProjectPlugin→ObjectOSEnvironmentPlugincreateSingleProjectPlugin→createSingleEnvironmentPlugincom.objectstack.runtime.objectos-project→objectos-environmentcom.objectstack.studio.single-project→single-environmentcom.objectstack.multi-project→multi-environmentcom.objectstack.runtime.system-project→system-environmentprovisionSystemProject→provisionSystemEnvironment.Database / schemas
sys_metadataandsys_metadata_history:project_id→environment_id.sys_activity:project_id→environment_id(plus index).sys_project→sys_environment(lookup targets),
sys_project_member→sys_environment_member,sys_project_credential→sys_environment_credential.active_project_id→active_environment_id.packages/spec/json-schema/system/:ProjectArtifact*.json→EnvironmentArtifact*.json(regenerated at build).Automatic forward migration
A new migration
migrateProjectIdToEnvironmentId(
packages/metadata/src/migrations/migrate-project-id-to-environment-id.ts)auto-runs from
DatabaseLoader.ensureSchema()on bootstrap and rewrites anyexisting
project_idcolumn onsys_metadata/sys_metadata_historytoenvironment_id(idempotent, best-effort). Existing rows are preserved.The legacy reverse migration
migrateEnvIdToProjectIdis retained verbatimfor historical / disaster-recovery use; it is not auto-run.
Migration guide
If you maintain a Cloud control-plane deployment, the
cloudrepository mustbe updated in lockstep to pick up the new plugin identifier strings
(
single-environment,multi-environment,objectos-environment).Patch Changes
@objectstack/rest@6.0.0
Major Changes
944f187: # v5.0 —
project→environmenthard renameThe runtime concept previously called "project" (per-tenant business
workspace; Org → Project → Branch hierarchy; per-project ObjectKernel,
per-project DB, per-project artifact) is now uniformly called
"environment".
This is a hard rename with no aliases, deprecation shims, or compatibility
layer. Upgrade requires a coordinated update of CLI, runtime, server, and any
clients calling the REST API.
Breaking changes
CLI
--project/-p→--environment/-e(os publish,os rollback)--project-id→--environment-id(os dev)proj_local→env_local.OS_PROJECT_ID→OS_ENVIRONMENT_ID.os projects ...→os environments ...(
bind,create,list,show,switch).activeProjectId→activeEnvironmentId.HTTP / REST
/api/v1/projects/:projectId/...→/api/v1/environments/:environmentId/..../api/v1/cloud/projects/...→/api/v1/cloud/environments/...(including
/cloud/environments/:id/artifact,/cloud/environments/:id/metadata,/cloud/environments/:id/credentials/rotate, etc.).X-Project-Id(and lowercasex-project-id) →X-Environment-Id(
x-environment-id).req.params.projectId→req.params.environmentId.environmentIdend-to-end.Runtime / spec
createSystemProjectPlugin→createSystemEnvironmentPluginSYSTEM_PROJECT_ID→SYSTEM_ENVIRONMENT_IDProjectArtifactSchema→EnvironmentArtifactSchemaPROJECT_ARTIFACT_SCHEMA_VERSION→ENVIRONMENT_ARTIFACT_SCHEMA_VERSIONObjectOSProjectPlugin→ObjectOSEnvironmentPlugincreateSingleProjectPlugin→createSingleEnvironmentPlugincom.objectstack.runtime.objectos-project→objectos-environmentcom.objectstack.studio.single-project→single-environmentcom.objectstack.multi-project→multi-environmentcom.objectstack.runtime.system-project→system-environmentprovisionSystemProject→provisionSystemEnvironment.Database / schemas
sys_metadataandsys_metadata_history:project_id→environment_id.sys_activity:project_id→environment_id(plus index).sys_project→sys_environment(lookup targets),
sys_project_member→sys_environment_member,sys_project_credential→sys_environment_credential.active_project_id→active_environment_id.packages/spec/json-schema/system/:ProjectArtifact*.json→EnvironmentArtifact*.json(regenerated at build).Automatic forward migration
A new migration
migrateProjectIdToEnvironmentId(
packages/metadata/src/migrations/migrate-project-id-to-environment-id.ts)auto-runs from
DatabaseLoader.ensureSchema()on bootstrap and rewrites anyexisting
project_idcolumn onsys_metadata/sys_metadata_historytoenvironment_id(idempotent, best-effort). Existing rows are preserved.The legacy reverse migration
migrateEnvIdToProjectIdis retained verbatimfor historical / disaster-recovery use; it is not auto-run.
Migration guide
If you maintain a Cloud control-plane deployment, the
cloudrepository mustbe updated in lockstep to pick up the new plugin identifier strings
(
single-environment,multi-environment,objectos-environment).Patch Changes
@objectstack/runtime@6.0.0
Major Changes
944f187: # v5.0 —
project→environmenthard renameThe runtime concept previously called "project" (per-tenant business
workspace; Org → Project → Branch hierarchy; per-project ObjectKernel,
per-project DB, per-project artifact) is now uniformly called
"environment".
This is a hard rename with no aliases, deprecation shims, or compatibility
layer. Upgrade requires a coordinated update of CLI, runtime, server, and any
clients calling the REST API.
Breaking changes
CLI
--project/-p→--environment/-e(os publish,os rollback)--project-id→--environment-id(os dev)proj_local→env_local.OS_PROJECT_ID→OS_ENVIRONMENT_ID.os projects ...→os environments ...(
bind,create,list,show,switch).activeProjectId→activeEnvironmentId.HTTP / REST
/api/v1/projects/:projectId/...→/api/v1/environments/:environmentId/..../api/v1/cloud/projects/...→/api/v1/cloud/environments/...(including
/cloud/environments/:id/artifact,/cloud/environments/:id/metadata,/cloud/environments/:id/credentials/rotate, etc.).X-Project-Id(and lowercasex-project-id) →X-Environment-Id(
x-environment-id).req.params.projectId→req.params.environmentId.environmentIdend-to-end.Runtime / spec
createSystemProjectPlugin→createSystemEnvironmentPluginSYSTEM_PROJECT_ID→SYSTEM_ENVIRONMENT_IDProjectArtifactSchema→EnvironmentArtifactSchemaPROJECT_ARTIFACT_SCHEMA_VERSION→ENVIRONMENT_ARTIFACT_SCHEMA_VERSIONObjectOSProjectPlugin→ObjectOSEnvironmentPlugincreateSingleProjectPlugin→createSingleEnvironmentPlugincom.objectstack.runtime.objectos-project→objectos-environmentcom.objectstack.studio.single-project→single-environmentcom.objectstack.multi-project→multi-environmentcom.objectstack.runtime.system-project→system-environmentprovisionSystemProject→provisionSystemEnvironment.Database / schemas
sys_metadataandsys_metadata_history:project_id→environment_id.sys_activity:project_id→environment_id(plus index).sys_project→sys_environment(lookup targets),
sys_project_member→sys_environment_member,sys_project_credential→sys_environment_credential.active_project_id→active_environment_id.packages/spec/json-schema/system/:ProjectArtifact*.json→EnvironmentArtifact*.json(regenerated at build).Automatic forward migration
A new migration
migrateProjectIdToEnvironmentId(
packages/metadata/src/migrations/migrate-project-id-to-environment-id.ts)auto-runs from
DatabaseLoader.ensureSchema()on bootstrap and rewrites anyexisting
project_idcolumn onsys_metadata/sys_metadata_historytoenvironment_id(idempotent, best-effort). Existing rows are preserved.The legacy reverse migration
migrateEnvIdToProjectIdis retained verbatimfor historical / disaster-recovery use; it is not auto-run.
Migration guide
If you maintain a Cloud control-plane deployment, the
cloudrepository mustbe updated in lockstep to pick up the new plugin identifier strings
(
single-environment,multi-environment,objectos-environment).Patch Changes
@objectstack/spec@6.0.0
Major Changes
944f187: # v5.0 —
project→environmenthard renameThe runtime concept previously called "project" (per-tenant business
workspace; Org → Project → Branch hierarchy; per-project ObjectKernel,
per-project DB, per-project artifact) is now uniformly called
"environment".
This is a hard rename with no aliases, deprecation shims, or compatibility
layer. Upgrade requires a coordinated update of CLI, runtime, server, and any
clients calling the REST API.
Breaking changes
CLI
--project/-p→--environment/-e(os publish,os rollback)--project-id→--environment-id(os dev)proj_local→env_local.OS_PROJECT_ID→OS_ENVIRONMENT_ID.os projects ...→os environments ...(
bind,create,list,show,switch).activeProjectId→activeEnvironmentId.HTTP / REST
/api/v1/projects/:projectId/...→/api/v1/environments/:environmentId/..../api/v1/cloud/projects/...→/api/v1/cloud/environments/...(including
/cloud/environments/:id/artifact,/cloud/environments/:id/metadata,/cloud/environments/:id/credentials/rotate, etc.).X-Project-Id(and lowercasex-project-id) →X-Environment-Id(
x-environment-id).req.params.projectId→req.params.environmentId.environmentIdend-to-end.Runtime / spec
createSystemProjectPlugin→createSystemEnvironmentPluginSYSTEM_PROJECT_ID→SYSTEM_ENVIRONMENT_IDProjectArtifactSchema→EnvironmentArtifactSchemaPROJECT_ARTIFACT_SCHEMA_VERSION→ENVIRONMENT_ARTIFACT_SCHEMA_VERSIONObjectOSProjectPlugin→ObjectOSEnvironmentPlugincreateSingleProjectPlugin→createSingleEnvironmentPlugincom.objectstack.runtime.objectos-project→objectos-environmentcom.objectstack.studio.single-project→single-environmentcom.objectstack.multi-project→multi-environmentcom.objectstack.runtime.system-project→system-environmentprovisionSystemProject→provisionSystemEnvironment.Database / schemas
sys_metadataandsys_metadata_history:project_id→environment_id.sys_activity:project_id→environment_id(plus index).sys_project→sys_environment(lookup targets),
sys_project_member→sys_environment_member,sys_project_credential→sys_environment_credential.active_project_id→active_environment_id.packages/spec/json-schema/system/:ProjectArtifact*.json→EnvironmentArtifact*.json(regenerated at build).Automatic forward migration
A new migration
migrateProjectIdToEnvironmentId(
packages/metadata/src/migrations/migrate-project-id-to-environment-id.ts)auto-runs from
DatabaseLoader.ensureSchema()on bootstrap and rewrites anyexisting
project_idcolumn onsys_metadata/sys_metadata_historytoenvironment_id(idempotent, best-effort). Existing rows are preserved.The legacy reverse migration
migrateEnvIdToProjectIdis retained verbatimfor historical / disaster-recovery use; it is not auto-run.
Migration guide
If you maintain a Cloud control-plane deployment, the
cloudrepository mustbe updated in lockstep to pick up the new plugin identifier strings
(
single-environment,multi-environment,objectos-environment).@objectstack/account@6.0.0
Patch Changes
@objectstack/express@6.0.0
Patch Changes
@objectstack/fastify@6.0.0
Patch Changes
@objectstack/hono@6.0.0
Patch Changes
@objectstack/nestjs@6.0.0
Patch Changes
@objectstack/nextjs@6.0.0
Patch Changes
@objectstack/nuxt@6.0.0
Patch Changes
@objectstack/sveltekit@6.0.0
Patch Changes
@objectstack/client-react@6.0.0
Patch Changes
@objectstack/core@6.0.0
Patch Changes
@objectstack/formula@6.0.0
Patch Changes
@objectstack/metadata-fs@6.0.0
Patch Changes
@objectstack/objectql@6.0.0
Patch Changes
@objectstack/observability@6.0.0
Patch Changes
@objectstack/driver-memory@6.0.0
Patch Changes
@objectstack/driver-mongodb@6.0.0
Patch Changes
@objectstack/driver-sql@6.0.0
Patch Changes
@objectstack/driver-turso@6.0.0
Patch Changes
@objectstack/plugin-approvals@6.0.0
Patch Changes
@objectstack/plugin-audit@6.0.0
Patch Changes
@objectstack/plugin-auth@6.0.0
Patch Changes
@objectstack/plugin-dev@6.0.0
Patch Changes
@objectstack/plugin-email@6.0.0
Patch Changes
@objectstack/plugin-hono-server@6.0.0
Patch Changes
@objectstack/plugin-mcp-server@6.0.0
Patch Changes
@objectstack/plugin-msw@6.0.0
Patch Changes
@objectstack/plugin-reports@6.0.0
Patch Changes
@objectstack/plugin-security@6.0.0
Patch Changes
@objectstack/plugin-sharing@6.0.0
Patch Changes
@objectstack/plugin-webhooks@6.0.0
Patch Changes
@objectstack/service-ai@6.0.0
Patch Changes
@objectstack/service-analytics@6.0.0
Patch Changes
@objectstack/service-automation@6.0.0
Patch Changes
@objectstack/service-cache@6.0.0
Patch Changes
@objectstack/service-cluster@5.1.2
Patch Changes
@objectstack/service-cluster-redis@5.1.2
Patch Changes
@objectstack/service-feed@6.0.0
Patch Changes
@objectstack/service-i18n@6.0.0
Patch Changes
@objectstack/service-job@6.0.0
Patch Changes
@objectstack/service-package@6.0.0
Patch Changes
@objectstack/service-queue@6.0.0
Patch Changes
@objectstack/service-realtime@6.0.0
Patch Changes
@objectstack/service-settings@6.0.0
Patch Changes
@objectstack/service-storage@6.0.0
Patch Changes
@objectstack/types@6.0.0
Patch Changes
create-objectstack@6.0.0
@objectstack/metadata-core@6.0.0
objectstack-vscode@6.0.0
@objectstack/example-crm@4.0.12
Patch Changes
@example/app-todo@4.0.12
Patch Changes