Skip to content

chore: version packages - #1274

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Closed

chore: version packages#1274
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

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 — projectenvironment hard rename

    The 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.

    Note: "project" in the npm / monorepo sense (the framework itself, package.json,
    tsconfig project references, vitest projects config) is unchanged.

    Breaking changes

    CLI

    • Flags renamed:
      • --project / -p--environment / -e (os publish, os rollback)
      • --project-id--environment-id (os dev)
    • Default local env id: proj_localenv_local.
    • Env var: OS_PROJECT_IDOS_ENVIRONMENT_ID.
    • Command group renamed: os projects ...os environments ...
      (bind, create, list, show, switch).
    • Persisted auth-config key: activeProjectIdactiveEnvironmentId.

    HTTP / REST

    • Scoped routes: /api/v1/projects/:projectId/.../api/v1/environments/:environmentId/....
    • Cloud control-plane routes: /api/v1/cloud/projects/.../api/v1/cloud/environments/...
      (including /cloud/environments/:id/artifact, /cloud/environments/:id/metadata,
      /cloud/environments/:id/credentials/rotate, etc.).
    • Header: X-Project-Id (and lowercase x-project-id) → X-Environment-Id
      (x-environment-id).
    • Route param name in handlers: req.params.projectIdreq.params.environmentId.
    • Hostname-routing and tenant-resolution code-paths use environmentId end-to-end.

    Runtime / spec

    • Exported symbols (no aliases):
      • createSystemProjectPlugincreateSystemEnvironmentPlugin
      • SYSTEM_PROJECT_IDSYSTEM_ENVIRONMENT_ID
      • ProjectArtifactSchemaEnvironmentArtifactSchema
      • PROJECT_ARTIFACT_SCHEMA_VERSIONENVIRONMENT_ARTIFACT_SCHEMA_VERSION
      • ObjectOSProjectPluginObjectOSEnvironmentPlugin
      • createSingleProjectPlugincreateSingleEnvironmentPlugin
    • Plugin identifier strings:
      • com.objectstack.runtime.objectos-projectobjectos-environment
      • com.objectstack.studio.single-projectsingle-environment
      • com.objectstack.multi-projectmulti-environment
      • com.objectstack.runtime.system-projectsystem-environment
    • Provisioning hook: provisionSystemProjectprovisionSystemEnvironment.

    Database / schemas

    • Column renames on sys_metadata and sys_metadata_history:
      project_idenvironment_id.
    • Column renames on sys_activity: project_idenvironment_id (plus index).
    • Object renames in platform-objects metadata: sys_projectsys_environment
      (lookup targets), sys_project_membersys_environment_member,
      sys_project_credentialsys_environment_credential.
    • Auth-context field: active_project_idactive_environment_id.
    • JSON schemas under packages/spec/json-schema/system/:
      ProjectArtifact*.jsonEnvironmentArtifact*.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 any
    existing project_id column on sys_metadata / sys_metadata_history to
    environment_id (idempotent, best-effort). Existing rows are preserved.

    The legacy reverse migration migrateEnvIdToProjectId is retained verbatim
    for historical / disaster-recovery use; it is not auto-run.

    Migration guide

    -os publish --project proj_xyz+os publish --environment env_xyz-curl -H "X-Project-Id: env_xyz" https://api.example.com/api/v1/data/customer+curl -H "X-Environment-Id: env_xyz" https://api.example.com/api/v1/data/customer-OS_PROJECT_ID=env_xyz os dev+OS_ENVIRONMENT_ID=env_xyz os dev-import { createSystemProjectPlugin, SYSTEM_PROJECT_ID } from "@objectstack/runtime";+import { createSystemEnvironmentPlugin, SYSTEM_ENVIRONMENT_ID } from "@objectstack/runtime";-import { ProjectArtifactSchema } from "@objectstack/spec";+import { EnvironmentArtifactSchema } from "@objectstack/spec";

    If you maintain a Cloud control-plane deployment, the cloud repository must
    be updated in lockstep to pick up the new plugin identifier strings
    (single-environment, multi-environment, objectos-environment).

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/runtime@6.0.0
    • @objectstack/rest@6.0.0
    • @objectstack/client@6.0.0
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0
    • @objectstack/objectql@6.0.0
    • @objectstack/observability@6.0.0
    • @objectstack/driver-memory@6.0.0
    • @objectstack/driver-mongodb@6.0.0
    • @objectstack/driver-sql@6.0.0
    • @objectstack/driver-turso@6.0.0
    • @objectstack/plugin-approvals@6.0.0
    • @objectstack/plugin-audit@6.0.0
    • @objectstack/plugin-auth@6.0.0
    • @objectstack/plugin-email@6.0.0
    • @objectstack/plugin-hono-server@6.0.0
    • @objectstack/plugin-mcp-server@6.0.0
    • @objectstack/plugin-reports@6.0.0
    • @objectstack/plugin-security@6.0.0
    • @objectstack/plugin-sharing@6.0.0
    • @objectstack/plugin-webhooks@6.0.0
    • @objectstack/service-ai@6.0.0
    • @objectstack/service-analytics@6.0.0
    • @objectstack/service-automation@6.0.0
    • @objectstack/service-cache@6.0.0
    • @objectstack/service-feed@6.0.0
    • @objectstack/service-job@6.0.0
    • @objectstack/service-package@6.0.0
    • @objectstack/service-queue@6.0.0
    • @objectstack/service-realtime@6.0.0
    • @objectstack/service-settings@6.0.0
    • @objectstack/service-storage@6.0.0

@objectstack/client@6.0.0

Major Changes

  • 944f187: # v5.0 — projectenvironment hard rename

    The 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.

    Note: "project" in the npm / monorepo sense (the framework itself, package.json,
    tsconfig project references, vitest projects config) is unchanged.

    Breaking changes

    CLI

    • Flags renamed:
      • --project / -p--environment / -e (os publish, os rollback)
      • --project-id--environment-id (os dev)
    • Default local env id: proj_localenv_local.
    • Env var: OS_PROJECT_IDOS_ENVIRONMENT_ID.
    • Command group renamed: os projects ...os environments ...
      (bind, create, list, show, switch).
    • Persisted auth-config key: activeProjectIdactiveEnvironmentId.

    HTTP / REST

    • Scoped routes: /api/v1/projects/:projectId/.../api/v1/environments/:environmentId/....
    • Cloud control-plane routes: /api/v1/cloud/projects/.../api/v1/cloud/environments/...
      (including /cloud/environments/:id/artifact, /cloud/environments/:id/metadata,
      /cloud/environments/:id/credentials/rotate, etc.).
    • Header: X-Project-Id (and lowercase x-project-id) → X-Environment-Id
      (x-environment-id).
    • Route param name in handlers: req.params.projectIdreq.params.environmentId.
    • Hostname-routing and tenant-resolution code-paths use environmentId end-to-end.

    Runtime / spec

    • Exported symbols (no aliases):
      • createSystemProjectPlugincreateSystemEnvironmentPlugin
      • SYSTEM_PROJECT_IDSYSTEM_ENVIRONMENT_ID
      • ProjectArtifactSchemaEnvironmentArtifactSchema
      • PROJECT_ARTIFACT_SCHEMA_VERSIONENVIRONMENT_ARTIFACT_SCHEMA_VERSION
      • ObjectOSProjectPluginObjectOSEnvironmentPlugin
      • createSingleProjectPlugincreateSingleEnvironmentPlugin
    • Plugin identifier strings:
      • com.objectstack.runtime.objectos-projectobjectos-environment
      • com.objectstack.studio.single-projectsingle-environment
      • com.objectstack.multi-projectmulti-environment
      • com.objectstack.runtime.system-projectsystem-environment
    • Provisioning hook: provisionSystemProjectprovisionSystemEnvironment.

    Database / schemas

    • Column renames on sys_metadata and sys_metadata_history:
      project_idenvironment_id.
    • Column renames on sys_activity: project_idenvironment_id (plus index).
    • Object renames in platform-objects metadata: sys_projectsys_environment
      (lookup targets), sys_project_membersys_environment_member,
      sys_project_credentialsys_environment_credential.
    • Auth-context field: active_project_idactive_environment_id.
    • JSON schemas under packages/spec/json-schema/system/:
      ProjectArtifact*.jsonEnvironmentArtifact*.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 any
    existing project_id column on sys_metadata / sys_metadata_history to
    environment_id (idempotent, best-effort). Existing rows are preserved.

    The legacy reverse migration migrateEnvIdToProjectId is retained verbatim
    for historical / disaster-recovery use; it is not auto-run.

    Migration guide

    -os publish --project proj_xyz+os publish --environment env_xyz-curl -H "X-Project-Id: env_xyz" https://api.example.com/api/v1/data/customer+curl -H "X-Environment-Id: env_xyz" https://api.example.com/api/v1/data/customer-OS_PROJECT_ID=env_xyz os dev+OS_ENVIRONMENT_ID=env_xyz os dev-import { createSystemProjectPlugin, SYSTEM_PROJECT_ID } from "@objectstack/runtime";+import { createSystemEnvironmentPlugin, SYSTEM_ENVIRONMENT_ID } from "@objectstack/runtime";-import { ProjectArtifactSchema } from "@objectstack/spec";+import { EnvironmentArtifactSchema } from "@objectstack/spec";

    If you maintain a Cloud control-plane deployment, the cloud repository must
    be updated in lockstep to pick up the new plugin identifier strings
    (single-environment, multi-environment, objectos-environment).

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0

@objectstack/metadata@6.0.0

Major Changes

  • 944f187: # v5.0 — projectenvironment hard rename

    The 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.

    Note: "project" in the npm / monorepo sense (the framework itself, package.json,
    tsconfig project references, vitest projects config) is unchanged.

    Breaking changes

    CLI

    • Flags renamed:
      • --project / -p--environment / -e (os publish, os rollback)
      • --project-id--environment-id (os dev)
    • Default local env id: proj_localenv_local.
    • Env var: OS_PROJECT_IDOS_ENVIRONMENT_ID.
    • Command group renamed: os projects ...os environments ...
      (bind, create, list, show, switch).
    • Persisted auth-config key: activeProjectIdactiveEnvironmentId.

    HTTP / REST

    • Scoped routes: /api/v1/projects/:projectId/.../api/v1/environments/:environmentId/....
    • Cloud control-plane routes: /api/v1/cloud/projects/.../api/v1/cloud/environments/...
      (including /cloud/environments/:id/artifact, /cloud/environments/:id/metadata,
      /cloud/environments/:id/credentials/rotate, etc.).
    • Header: X-Project-Id (and lowercase x-project-id) → X-Environment-Id
      (x-environment-id).
    • Route param name in handlers: req.params.projectIdreq.params.environmentId.
    • Hostname-routing and tenant-resolution code-paths use environmentId end-to-end.

    Runtime / spec

    • Exported symbols (no aliases):
      • createSystemProjectPlugincreateSystemEnvironmentPlugin
      • SYSTEM_PROJECT_IDSYSTEM_ENVIRONMENT_ID
      • ProjectArtifactSchemaEnvironmentArtifactSchema
      • PROJECT_ARTIFACT_SCHEMA_VERSIONENVIRONMENT_ARTIFACT_SCHEMA_VERSION
      • ObjectOSProjectPluginObjectOSEnvironmentPlugin
      • createSingleProjectPlugincreateSingleEnvironmentPlugin
    • Plugin identifier strings:
      • com.objectstack.runtime.objectos-projectobjectos-environment
      • com.objectstack.studio.single-projectsingle-environment
      • com.objectstack.multi-projectmulti-environment
      • com.objectstack.runtime.system-projectsystem-environment
    • Provisioning hook: provisionSystemProjectprovisionSystemEnvironment.

    Database / schemas

    • Column renames on sys_metadata and sys_metadata_history:
      project_idenvironment_id.
    • Column renames on sys_activity: project_idenvironment_id (plus index).
    • Object renames in platform-objects metadata: sys_projectsys_environment
      (lookup targets), sys_project_membersys_environment_member,
      sys_project_credentialsys_environment_credential.
    • Auth-context field: active_project_idactive_environment_id.
    • JSON schemas under packages/spec/json-schema/system/:
      ProjectArtifact*.jsonEnvironmentArtifact*.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 any
    existing project_id column on sys_metadata / sys_metadata_history to
    environment_id (idempotent, best-effort). Existing rows are preserved.

    The legacy reverse migration migrateEnvIdToProjectId is retained verbatim
    for historical / disaster-recovery use; it is not auto-run.

    Migration guide

    -os publish --project proj_xyz+os publish --environment env_xyz-curl -H "X-Project-Id: env_xyz" https://api.example.com/api/v1/data/customer+curl -H "X-Environment-Id: env_xyz" https://api.example.com/api/v1/data/customer-OS_PROJECT_ID=env_xyz os dev+OS_ENVIRONMENT_ID=env_xyz os dev-import { createSystemProjectPlugin, SYSTEM_PROJECT_ID } from "@objectstack/runtime";+import { createSystemEnvironmentPlugin, SYSTEM_ENVIRONMENT_ID } from "@objectstack/runtime";-import { ProjectArtifactSchema } from "@objectstack/spec";+import { EnvironmentArtifactSchema } from "@objectstack/spec";

    If you maintain a Cloud control-plane deployment, the cloud repository must
    be updated in lockstep to pick up the new plugin identifier strings
    (single-environment, multi-environment, objectos-environment).

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/platform-objects@6.0.0
    • @objectstack/core@6.0.0
    • @objectstack/types@6.0.0
    • @objectstack/metadata-core@6.0.0
    • @objectstack/metadata-fs@6.0.0

@objectstack/platform-objects@6.0.0

Major Changes

  • 944f187: # v5.0 — projectenvironment hard rename

    The 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.

    Note: "project" in the npm / monorepo sense (the framework itself, package.json,
    tsconfig project references, vitest projects config) is unchanged.

    Breaking changes

    CLI

    • Flags renamed:
      • --project / -p--environment / -e (os publish, os rollback)
      • --project-id--environment-id (os dev)
    • Default local env id: proj_localenv_local.
    • Env var: OS_PROJECT_IDOS_ENVIRONMENT_ID.
    • Command group renamed: os projects ...os environments ...
      (bind, create, list, show, switch).
    • Persisted auth-config key: activeProjectIdactiveEnvironmentId.

    HTTP / REST

    • Scoped routes: /api/v1/projects/:projectId/.../api/v1/environments/:environmentId/....
    • Cloud control-plane routes: /api/v1/cloud/projects/.../api/v1/cloud/environments/...
      (including /cloud/environments/:id/artifact, /cloud/environments/:id/metadata,
      /cloud/environments/:id/credentials/rotate, etc.).
    • Header: X-Project-Id (and lowercase x-project-id) → X-Environment-Id
      (x-environment-id).
    • Route param name in handlers: req.params.projectIdreq.params.environmentId.
    • Hostname-routing and tenant-resolution code-paths use environmentId end-to-end.

    Runtime / spec

    • Exported symbols (no aliases):
      • createSystemProjectPlugincreateSystemEnvironmentPlugin
      • SYSTEM_PROJECT_IDSYSTEM_ENVIRONMENT_ID
      • ProjectArtifactSchemaEnvironmentArtifactSchema
      • PROJECT_ARTIFACT_SCHEMA_VERSIONENVIRONMENT_ARTIFACT_SCHEMA_VERSION
      • ObjectOSProjectPluginObjectOSEnvironmentPlugin
      • createSingleProjectPlugincreateSingleEnvironmentPlugin
    • Plugin identifier strings:
      • com.objectstack.runtime.objectos-projectobjectos-environment
      • com.objectstack.studio.single-projectsingle-environment
      • com.objectstack.multi-projectmulti-environment
      • com.objectstack.runtime.system-projectsystem-environment
    • Provisioning hook: provisionSystemProjectprovisionSystemEnvironment.

    Database / schemas

    • Column renames on sys_metadata and sys_metadata_history:
      project_idenvironment_id.
    • Column renames on sys_activity: project_idenvironment_id (plus index).
    • Object renames in platform-objects metadata: sys_projectsys_environment
      (lookup targets), sys_project_membersys_environment_member,
      sys_project_credentialsys_environment_credential.
    • Auth-context field: active_project_idactive_environment_id.
    • JSON schemas under packages/spec/json-schema/system/:
      ProjectArtifact*.jsonEnvironmentArtifact*.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 any
    existing project_id column on sys_metadata / sys_metadata_history to
    environment_id (idempotent, best-effort). Existing rows are preserved.

    The legacy reverse migration migrateEnvIdToProjectId is retained verbatim
    for historical / disaster-recovery use; it is not auto-run.

    Migration guide

    -os publish --project proj_xyz+os publish --environment env_xyz-curl -H "X-Project-Id: env_xyz" https://api.example.com/api/v1/data/customer+curl -H "X-Environment-Id: env_xyz" https://api.example.com/api/v1/data/customer-OS_PROJECT_ID=env_xyz os dev+OS_ENVIRONMENT_ID=env_xyz os dev-import { createSystemProjectPlugin, SYSTEM_PROJECT_ID } from "@objectstack/runtime";+import { createSystemEnvironmentPlugin, SYSTEM_ENVIRONMENT_ID } from "@objectstack/runtime";-import { ProjectArtifactSchema } from "@objectstack/spec";+import { EnvironmentArtifactSchema } from "@objectstack/spec";

    If you maintain a Cloud control-plane deployment, the cloud repository must
    be updated in lockstep to pick up the new plugin identifier strings
    (single-environment, multi-environment, objectos-environment).

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0

@objectstack/rest@6.0.0

Major Changes

  • 944f187: # v5.0 — projectenvironment hard rename

    The 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.

    Note: "project" in the npm / monorepo sense (the framework itself, package.json,
    tsconfig project references, vitest projects config) is unchanged.

    Breaking changes

    CLI

    • Flags renamed:
      • --project / -p--environment / -e (os publish, os rollback)
      • --project-id--environment-id (os dev)
    • Default local env id: proj_localenv_local.
    • Env var: OS_PROJECT_IDOS_ENVIRONMENT_ID.
    • Command group renamed: os projects ...os environments ...
      (bind, create, list, show, switch).
    • Persisted auth-config key: activeProjectIdactiveEnvironmentId.

    HTTP / REST

    • Scoped routes: /api/v1/projects/:projectId/.../api/v1/environments/:environmentId/....
    • Cloud control-plane routes: /api/v1/cloud/projects/.../api/v1/cloud/environments/...
      (including /cloud/environments/:id/artifact, /cloud/environments/:id/metadata,
      /cloud/environments/:id/credentials/rotate, etc.).
    • Header: X-Project-Id (and lowercase x-project-id) → X-Environment-Id
      (x-environment-id).
    • Route param name in handlers: req.params.projectIdreq.params.environmentId.
    • Hostname-routing and tenant-resolution code-paths use environmentId end-to-end.

    Runtime / spec

    • Exported symbols (no aliases):
      • createSystemProjectPlugincreateSystemEnvironmentPlugin
      • SYSTEM_PROJECT_IDSYSTEM_ENVIRONMENT_ID
      • ProjectArtifactSchemaEnvironmentArtifactSchema
      • PROJECT_ARTIFACT_SCHEMA_VERSIONENVIRONMENT_ARTIFACT_SCHEMA_VERSION
      • ObjectOSProjectPluginObjectOSEnvironmentPlugin
      • createSingleProjectPlugincreateSingleEnvironmentPlugin
    • Plugin identifier strings:
      • com.objectstack.runtime.objectos-projectobjectos-environment
      • com.objectstack.studio.single-projectsingle-environment
      • com.objectstack.multi-projectmulti-environment
      • com.objectstack.runtime.system-projectsystem-environment
    • Provisioning hook: provisionSystemProjectprovisionSystemEnvironment.

    Database / schemas

    • Column renames on sys_metadata and sys_metadata_history:
      project_idenvironment_id.
    • Column renames on sys_activity: project_idenvironment_id (plus index).
    • Object renames in platform-objects metadata: sys_projectsys_environment
      (lookup targets), sys_project_membersys_environment_member,
      sys_project_credentialsys_environment_credential.
    • Auth-context field: active_project_idactive_environment_id.
    • JSON schemas under packages/spec/json-schema/system/:
      ProjectArtifact*.jsonEnvironmentArtifact*.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 any
    existing project_id column on sys_metadata / sys_metadata_history to
    environment_id (idempotent, best-effort). Existing rows are preserved.

    The legacy reverse migration migrateEnvIdToProjectId is retained verbatim
    for historical / disaster-recovery use; it is not auto-run.

    Migration guide

    -os publish --project proj_xyz+os publish --environment env_xyz-curl -H "X-Project-Id: env_xyz" https://api.example.com/api/v1/data/customer+curl -H "X-Environment-Id: env_xyz" https://api.example.com/api/v1/data/customer-OS_PROJECT_ID=env_xyz os dev+OS_ENVIRONMENT_ID=env_xyz os dev-import { createSystemProjectPlugin, SYSTEM_PROJECT_ID } from "@objectstack/runtime";+import { createSystemEnvironmentPlugin, SYSTEM_ENVIRONMENT_ID } from "@objectstack/runtime";-import { ProjectArtifactSchema } from "@objectstack/spec";+import { EnvironmentArtifactSchema } from "@objectstack/spec";

    If you maintain a Cloud control-plane deployment, the cloud repository must
    be updated in lockstep to pick up the new plugin identifier strings
    (single-environment, multi-environment, objectos-environment).

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0
    • @objectstack/service-package@6.0.0

@objectstack/runtime@6.0.0

Major Changes

  • 944f187: # v5.0 — projectenvironment hard rename

    The 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.

    Note: "project" in the npm / monorepo sense (the framework itself, package.json,
    tsconfig project references, vitest projects config) is unchanged.

    Breaking changes

    CLI

    • Flags renamed:
      • --project / -p--environment / -e (os publish, os rollback)
      • --project-id--environment-id (os dev)
    • Default local env id: proj_localenv_local.
    • Env var: OS_PROJECT_IDOS_ENVIRONMENT_ID.
    • Command group renamed: os projects ...os environments ...
      (bind, create, list, show, switch).
    • Persisted auth-config key: activeProjectIdactiveEnvironmentId.

    HTTP / REST

    • Scoped routes: /api/v1/projects/:projectId/.../api/v1/environments/:environmentId/....
    • Cloud control-plane routes: /api/v1/cloud/projects/.../api/v1/cloud/environments/...
      (including /cloud/environments/:id/artifact, /cloud/environments/:id/metadata,
      /cloud/environments/:id/credentials/rotate, etc.).
    • Header: X-Project-Id (and lowercase x-project-id) → X-Environment-Id
      (x-environment-id).
    • Route param name in handlers: req.params.projectIdreq.params.environmentId.
    • Hostname-routing and tenant-resolution code-paths use environmentId end-to-end.

    Runtime / spec

    • Exported symbols (no aliases):
      • createSystemProjectPlugincreateSystemEnvironmentPlugin
      • SYSTEM_PROJECT_IDSYSTEM_ENVIRONMENT_ID
      • ProjectArtifactSchemaEnvironmentArtifactSchema
      • PROJECT_ARTIFACT_SCHEMA_VERSIONENVIRONMENT_ARTIFACT_SCHEMA_VERSION
      • ObjectOSProjectPluginObjectOSEnvironmentPlugin
      • createSingleProjectPlugincreateSingleEnvironmentPlugin
    • Plugin identifier strings:
      • com.objectstack.runtime.objectos-projectobjectos-environment
      • com.objectstack.studio.single-projectsingle-environment
      • com.objectstack.multi-projectmulti-environment
      • com.objectstack.runtime.system-projectsystem-environment
    • Provisioning hook: provisionSystemProjectprovisionSystemEnvironment.

    Database / schemas

    • Column renames on sys_metadata and sys_metadata_history:
      project_idenvironment_id.
    • Column renames on sys_activity: project_idenvironment_id (plus index).
    • Object renames in platform-objects metadata: sys_projectsys_environment
      (lookup targets), sys_project_membersys_environment_member,
      sys_project_credentialsys_environment_credential.
    • Auth-context field: active_project_idactive_environment_id.
    • JSON schemas under packages/spec/json-schema/system/:
      ProjectArtifact*.jsonEnvironmentArtifact*.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 any
    existing project_id column on sys_metadata / sys_metadata_history to
    environment_id (idempotent, best-effort). Existing rows are preserved.

    The legacy reverse migration migrateEnvIdToProjectId is retained verbatim
    for historical / disaster-recovery use; it is not auto-run.

    Migration guide

    -os publish --project proj_xyz+os publish --environment env_xyz-curl -H "X-Project-Id: env_xyz" https://api.example.com/api/v1/data/customer+curl -H "X-Environment-Id: env_xyz" https://api.example.com/api/v1/data/customer-OS_PROJECT_ID=env_xyz os dev+OS_ENVIRONMENT_ID=env_xyz os dev-import { createSystemProjectPlugin, SYSTEM_PROJECT_ID } from "@objectstack/runtime";+import { createSystemEnvironmentPlugin, SYSTEM_ENVIRONMENT_ID } from "@objectstack/runtime";-import { ProjectArtifactSchema } from "@objectstack/spec";+import { EnvironmentArtifactSchema } from "@objectstack/spec";

    If you maintain a Cloud control-plane deployment, the cloud repository must
    be updated in lockstep to pick up the new plugin identifier strings
    (single-environment, multi-environment, objectos-environment).

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/rest@6.0.0
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0
    • @objectstack/formula@6.0.0
    • @objectstack/observability@6.0.0
    • @objectstack/plugin-auth@6.0.0
    • @objectstack/plugin-security@6.0.0
    • @objectstack/service-cluster@5.1.2
    • @objectstack/service-i18n@6.0.0
    • @objectstack/types@6.0.0

@objectstack/spec@6.0.0

Major Changes

  • 944f187: # v5.0 — projectenvironment hard rename

    The 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.

    Note: "project" in the npm / monorepo sense (the framework itself, package.json,
    tsconfig project references, vitest projects config) is unchanged.

    Breaking changes

    CLI

    • Flags renamed:
      • --project / -p--environment / -e (os publish, os rollback)
      • --project-id--environment-id (os dev)
    • Default local env id: proj_localenv_local.
    • Env var: OS_PROJECT_IDOS_ENVIRONMENT_ID.
    • Command group renamed: os projects ...os environments ...
      (bind, create, list, show, switch).
    • Persisted auth-config key: activeProjectIdactiveEnvironmentId.

    HTTP / REST

    • Scoped routes: /api/v1/projects/:projectId/.../api/v1/environments/:environmentId/....
    • Cloud control-plane routes: /api/v1/cloud/projects/.../api/v1/cloud/environments/...
      (including /cloud/environments/:id/artifact, /cloud/environments/:id/metadata,
      /cloud/environments/:id/credentials/rotate, etc.).
    • Header: X-Project-Id (and lowercase x-project-id) → X-Environment-Id
      (x-environment-id).
    • Route param name in handlers: req.params.projectIdreq.params.environmentId.
    • Hostname-routing and tenant-resolution code-paths use environmentId end-to-end.

    Runtime / spec

    • Exported symbols (no aliases):
      • createSystemProjectPlugincreateSystemEnvironmentPlugin
      • SYSTEM_PROJECT_IDSYSTEM_ENVIRONMENT_ID
      • ProjectArtifactSchemaEnvironmentArtifactSchema
      • PROJECT_ARTIFACT_SCHEMA_VERSIONENVIRONMENT_ARTIFACT_SCHEMA_VERSION
      • ObjectOSProjectPluginObjectOSEnvironmentPlugin
      • createSingleProjectPlugincreateSingleEnvironmentPlugin
    • Plugin identifier strings:
      • com.objectstack.runtime.objectos-projectobjectos-environment
      • com.objectstack.studio.single-projectsingle-environment
      • com.objectstack.multi-projectmulti-environment
      • com.objectstack.runtime.system-projectsystem-environment
    • Provisioning hook: provisionSystemProjectprovisionSystemEnvironment.

    Database / schemas

    • Column renames on sys_metadata and sys_metadata_history:
      project_idenvironment_id.
    • Column renames on sys_activity: project_idenvironment_id (plus index).
    • Object renames in platform-objects metadata: sys_projectsys_environment
      (lookup targets), sys_project_membersys_environment_member,
      sys_project_credentialsys_environment_credential.
    • Auth-context field: active_project_idactive_environment_id.
    • JSON schemas under packages/spec/json-schema/system/:
      ProjectArtifact*.jsonEnvironmentArtifact*.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 any
    existing project_id column on sys_metadata / sys_metadata_history to
    environment_id (idempotent, best-effort). Existing rows are preserved.

    The legacy reverse migration migrateEnvIdToProjectId is retained verbatim
    for historical / disaster-recovery use; it is not auto-run.

    Migration guide

    -os publish --project proj_xyz+os publish --environment env_xyz-curl -H "X-Project-Id: env_xyz" https://api.example.com/api/v1/data/customer+curl -H "X-Environment-Id: env_xyz" https://api.example.com/api/v1/data/customer-OS_PROJECT_ID=env_xyz os dev+OS_ENVIRONMENT_ID=env_xyz os dev-import { createSystemProjectPlugin, SYSTEM_PROJECT_ID } from "@objectstack/runtime";+import { createSystemEnvironmentPlugin, SYSTEM_ENVIRONMENT_ID } from "@objectstack/runtime";-import { ProjectArtifactSchema } from "@objectstack/spec";+import { EnvironmentArtifactSchema } from "@objectstack/spec";

    If you maintain a Cloud control-plane deployment, the cloud repository must
    be updated in lockstep to pick up the new plugin identifier strings
    (single-environment, multi-environment, objectos-environment).

@objectstack/account@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/client@6.0.0
    • @objectstack/spec@6.0.0
    • @objectstack/client-react@6.0.0

@objectstack/express@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/runtime@6.0.0

@objectstack/fastify@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/runtime@6.0.0

@objectstack/hono@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/runtime@6.0.0
    • @objectstack/plugin-hono-server@6.0.0

@objectstack/nestjs@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/runtime@6.0.0

@objectstack/nextjs@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/runtime@6.0.0

@objectstack/nuxt@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/runtime@6.0.0

@objectstack/sveltekit@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/runtime@6.0.0

@objectstack/client-react@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/client@6.0.0
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0

@objectstack/core@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0

@objectstack/formula@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0

@objectstack/metadata-fs@6.0.0

Patch Changes

  • @objectstack/metadata-core@6.0.0

@objectstack/objectql@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0
    • @objectstack/formula@6.0.0
    • @objectstack/types@6.0.0
    • @objectstack/metadata-core@6.0.0

@objectstack/observability@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0

@objectstack/driver-memory@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0

@objectstack/driver-mongodb@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0

@objectstack/driver-sql@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0

@objectstack/driver-turso@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0
    • @objectstack/driver-sql@6.0.0

@objectstack/plugin-approvals@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/platform-objects@6.0.0
    • @objectstack/core@6.0.0
    • @objectstack/formula@6.0.0
    • @objectstack/metadata-core@6.0.0

@objectstack/plugin-audit@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/platform-objects@6.0.0
    • @objectstack/core@6.0.0

@objectstack/plugin-auth@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/platform-objects@6.0.0
    • @objectstack/core@6.0.0

@objectstack/plugin-dev@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/runtime@6.0.0
    • @objectstack/rest@6.0.0
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0
    • @objectstack/objectql@6.0.0
    • @objectstack/driver-memory@6.0.0
    • @objectstack/plugin-auth@6.0.0
    • @objectstack/plugin-hono-server@6.0.0
    • @objectstack/plugin-security@6.0.0
    • @objectstack/service-i18n@6.0.0

@objectstack/plugin-email@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/platform-objects@6.0.0
    • @objectstack/core@6.0.0

@objectstack/plugin-hono-server@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0

@objectstack/plugin-mcp-server@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0

@objectstack/plugin-msw@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/runtime@6.0.0
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0
    • @objectstack/objectql@6.0.0
    • @objectstack/types@6.0.0

@objectstack/plugin-reports@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/platform-objects@6.0.0
    • @objectstack/core@6.0.0

@objectstack/plugin-security@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/platform-objects@6.0.0
    • @objectstack/core@6.0.0

@objectstack/plugin-sharing@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/platform-objects@6.0.0
    • @objectstack/core@6.0.0
    • @objectstack/objectql@6.0.0

@objectstack/plugin-webhooks@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/platform-objects@6.0.0
    • @objectstack/core@6.0.0
    • @objectstack/service-cluster@5.1.2

@objectstack/service-ai@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0

@objectstack/service-analytics@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0

@objectstack/service-automation@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0
    • @objectstack/formula@6.0.0

@objectstack/service-cache@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0
    • @objectstack/observability@6.0.0

@objectstack/service-cluster@5.1.2

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0

@objectstack/service-cluster-redis@5.1.2

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/service-cluster@5.1.2

@objectstack/service-feed@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0

@objectstack/service-i18n@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0

@objectstack/service-job@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/platform-objects@6.0.0
    • @objectstack/core@6.0.0

@objectstack/service-package@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0

@objectstack/service-queue@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/platform-objects@6.0.0
    • @objectstack/core@6.0.0

@objectstack/service-realtime@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/platform-objects@6.0.0
    • @objectstack/core@6.0.0

@objectstack/service-settings@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/platform-objects@6.0.0
    • @objectstack/core@6.0.0

@objectstack/service-storage@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0
    • @objectstack/core@6.0.0
    • @objectstack/observability@6.0.0

@objectstack/types@6.0.0

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/spec@6.0.0

create-objectstack@6.0.0

@objectstack/metadata-core@6.0.0

objectstack-vscode@6.0.0

@objectstack/example-crm@4.0.12

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/runtime@6.0.0
    • @objectstack/spec@6.0.0

@example/app-todo@4.0.12

Patch Changes

  • Updated dependencies [944f187]
    • @objectstack/runtime@6.0.0
    • @objectstack/client@6.0.0
    • @objectstack/spec@6.0.0
    • @objectstack/objectql@6.0.0
    • @objectstack/driver-memory@6.0.0

@vercel

vercelBot commented May 24, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentActionsUpdated (UTC)
specReadyReadyPreview, CommentMay 24, 2026 5:28am

Request Review

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@hotlong