@objectql/core 4.2.0 → 4.2.2

package/.turbo/turbo-build.log

@@ -1,4 +1,4 @@
 
-> @objectql/core@4.2.0 build /home/runner/work/objectql/objectql/packages/foundation/core
+> @objectql/core@4.2.2 build /home/runner/work/objectql/objectql/packages/foundation/core
 > tsc
 

package/CHANGELOG.md

@@ -1,5 +1,28 @@
 # @objectql/core
 
+## 4.2.2
+
+### Patch Changes
+
+- 9a30c50: Patch release for all packages
+  - @objectql/plugin-formula@4.2.2
+  - @objectql/plugin-optimizations@4.2.2
+  - @objectql/plugin-query@4.2.2
+  - @objectql/plugin-validator@4.2.2
+  - @objectql/types@4.2.2
+
+## 4.2.1
+
+### Patch Changes
+
+- a0aa26a: Unify all package versions and release a patch
+- Updated dependencies [a0aa26a]
+  - @objectql/types@4.2.1
+  - @objectql/plugin-formula@4.2.1
+  - @objectql/plugin-optimizations@4.2.1
+  - @objectql/plugin-query@4.2.1
+  - @objectql/plugin-validator@4.2.1
+
 ## 4.2.0
 
 ### Minor Changes
@@ -47,6 +70,7 @@
   This patch release includes bug fixes, driver improvements, and enhanced test coverage:
 
   ### Driver Improvements
+
   - **MongoDB Driver**: Fixed bulk operations, transaction support, and type safety improvements
   - **FileSystem Driver**: Fixed TCK test compatibility with dataDir parameter
   - **SQL Driver**: Enhanced TCK test compatibility and fixed test failures
@@ -54,22 +78,26 @@
   - **Driver Utils**: Added shared utilities package for cross-driver functionality
 
   ### Testing & Quality
+
   - Added comprehensive TCK (Technology Compatibility Kit) compliance tests for all drivers
   - Expanded TCK test suite to 30+ comprehensive tests
   - Enhanced test infrastructure with better error handling
   - Added --passWithNoTests flag for packages without tests
 
   ### Type Safety
+
   - Improved type safety in MongoDB driver update methods
   - Better handling of atomic operators in MongoDB driver
   - Enhanced type definitions across driver layer
 
   ### Documentation
+
   - Added comprehensive driver documentation
   - Enhanced official documentation with Phase 2 implementation summaries
   - Improved protocol layer documentation
 
   ### Infrastructure
+
   - Standardized driver layer implementation
   - Enhanced protocol layer with better abstraction
   - Improved GitHub Actions workflow configurations
@@ -89,6 +117,7 @@
 - **Patch Release v4.0.3**
 
   This patch release includes infrastructure improvements and development experience enhancements:
+
   - Refactored dev server setup for improved configuration handling
   - Enhanced example scripts and development workflow
   - Updated build and test infrastructure
@@ -107,6 +136,7 @@
 - **Patch Release v4.0.2**
 
   This patch release includes:
+
   - Infrastructure improvements and maintenance updates
   - Enhanced stability and reliability
   - Bug fixes and performance optimizations
@@ -121,6 +151,7 @@
 - **Release Version 4.0.1**
 
   This patch release includes the latest repository improvements and infrastructure updates:
+
   - Added comprehensive GitHub workflows for CI/CD, testing, and quality assurance
   - Enhanced documentation and developer experience
   - Improved build and release processes with Changesets
@@ -138,6 +169,7 @@
 - 79d04e1: Patch release for January 2026 updates
 
   This patch includes minor improvements and maintenance updates:
+
   - Enhanced type safety across core packages
   - Improved error handling in drivers
   - Documentation updates
@@ -160,6 +192,7 @@
   This is a coordinated major release that unifies all ObjectQL packages to version 2.0.0, establishing a synchronized versioning strategy across the entire ecosystem.
 
   ### 🎯 Key Changes
+
   - **Unified Versioning**: All core packages now share the same version number (2.0.0)
   - **Fixed Group Management**: Updated changeset configuration to include all @objectql packages in the fixed versioning group
   - **Simplified Maintenance**: Future releases will automatically maintain version consistency across the entire monorepo
@@ -167,6 +200,7 @@
   ### 📦 Packages Included
 
   All ObjectQL packages are now synchronized at version 2.0.0:
+
   - Foundation: `@objectql/types`, `@objectql/core`, `@objectql/platform-node`
   - Drivers: `@objectql/driver-sql`, `@objectql/driver-mongo`, `@objectql/driver-redis`, `@objectql/driver-fs`, `@objectql/driver-memory`, `@objectql/driver-localstorage`, `@objectql/driver-excel`, `@objectql/sdk`
   - Runtime: `@objectql/server`

package/README.md

@@ -1,8 +1,11 @@
 # @objectql/core
 
-> **Implementation Status**: ✅ **Production Ready** - All core features fully implemented and tested. See [Implementation Status](https://github.com/objectstack-ai/objectql/blob/main/IMPLEMENTATION_STATUS.md) for complete details.
+> ⚠️ **DEPRECATED**: This package is deprecated. Use [`@objectstack/objectql`](https://www.npmjs.com/package/@objectstack/objectql) instead.
+> See the [Migration Guide](https://github.com/objectstack-ai/spec/blob/main/content/docs/guides/objectql-migration.mdx) for step-by-step instructions.
 
-The core ORM and runtime engine for ObjectQL. This package handles object querying, CRUD operations, database driver coordination, transaction management, and **metadata-driven validation**. As of version 4.0.0, it wraps the **ObjectKernel** for plugin architecture and lifecycle management.
+The core ORM and runtime engine for ObjectQL. All core functionality (ObjectQL engine, SchemaRegistry, createObjectQLKernel, utilities) is now available directly from `@objectstack/objectql`.
+
+The `ObjectQLPlugin` (orchestrator composing sub-plugins like ValidatorPlugin, FormulaPlugin, QueryPlugin) remains in this package as it is specific to the `@objectql` ecosystem.
 
 ## Features
 

package/dist/app.d.ts

@@ -1,66 +1,75 @@
 /**
- * ObjectQL
+ * ObjectQL Bridge Class
  * Copyright (c) 2026-present ObjectStack Inc.
  *
- * This source code is licensed under the MIT license found in the
- * LICENSE file in the root directory of this source tree.
+ * Extends the upstream @objectstack/objectql.ObjectQL engine with:
+ *  - Legacy constructor config (datasources map)
+ *  - MetadataRegistry integration (for ObjectLoader filesystem loading)
+ *
+ * This allows existing consumers to keep using:
+ *   const app = new ObjectQL({ datasources: { default: driver } });
+ *   const loader = new ObjectLoader(app.metadata);
+ *   await loader.load(dir);
+ *   await app.init();
  */
-import { MetadataRegistry, Driver, ObjectConfig, ObjectQLContext, ObjectQLContextOptions, IObjectQL, ObjectQLConfig, HookName, HookHandler, HookContext, ActionHandler, ActionContext } from '@objectql/types';
-import { ObjectKernel, type Plugin } from '@objectstack/runtime';
+import { ObjectQL as UpstreamObjectQL } from '@objectstack/objectql';
+import type { ServiceObject } from '@objectstack/spec/data';
+import type { DriverInterface } from '@objectstack/core';
+import { MetadataRegistry } from '@objectql/types';
+import type { Driver } from '@objectql/types';
 /**
- * ObjectQL
- *
- * ObjectQL implementation that wraps ObjectKernel
- * to provide the plugin architecture.
+ * Legacy config shape accepted by the ObjectQL bridge constructor.
+ */
+export interface ObjectQLConfig {
+    datasources?: Record<string, Driver | DriverInterface>;
+    [key: string]: unknown;
+}
+/**
+ * ObjectQL — drop-in replacement that bridges the upstream engine
+ * with the @objectql/types MetadataRegistry used by ObjectLoader.
  */
-export declare class ObjectQL implements IObjectQL {
-    get metadata(): MetadataRegistry;
-    private datasources;
-    private remotes;
-    private kernel;
-    private ql;
-    private kernelPlugins;
-    private hookManager;
-    private localActions;
-    private logger;
-    private config;
-    constructor(config: ObjectQLConfig);
-    use(plugin: Plugin): void;
-    removePackage(name: string): void;
-    on(event: HookName, objectName: string, handler: HookHandler, packageName?: string): void;
-    triggerHook(event: HookName, objectName: string, ctx: HookContext): Promise<void>;
-    registerAction(objectName: string, actionName: string, handler: ActionHandler, packageName?: string): void;
-    executeAction(objectName: string, actionName: string, ctx: ActionContext): Promise<any>;
-    createContext(options: ObjectQLContextOptions): ObjectQLContext;
+export declare class ObjectQL extends UpstreamObjectQL {
+    /**
+     * Filesystem metadata registry populated by ObjectLoader.
+     * After calling loader.load(), call app.init() to sync these
+     * entries into the upstream SchemaRegistry & driver layer.
+     */
+    readonly metadata: MetadataRegistry;
+    /** Typed self-reference for compat methods */
+    private get compat();
+    private pendingDrivers;
+    registerObject: (schema: ServiceObject, packageId?: string, namespace?: string) => string;
+    constructor(config?: ObjectQLConfig);
     /**
-     * Get the underlying ObjectKernel instance
+     * Initialize the engine.
      *
-     * This provides access to the kernel for advanced usage scenarios
-     * where you need direct access to the plugin architecture.
+     * Before calling the upstream init (which connects drivers and syncs schemas),
+     * bridge all objects loaded via ObjectLoader into the upstream SchemaRegistry.
+     */
+    init(): Promise<void>;
+    /**
+     * Sync all filesystem-loaded metadata into the upstream SchemaRegistry.
+     * Called automatically by init(), but can also be called manually.
+     */
+    private syncMetadataToRegistry;
+    /**
+     * Get an object definition by name.
      *
-     * @returns The ObjectKernel instance
-     * @throws Error if called before init()
+     * Checks the upstream SchemaRegistry first, then falls back to the
+     * local MetadataRegistry for objects loaded via ObjectLoader but
+     * not yet synced (i.e., init() hasn't been called yet).
      */
-    getKernel(): ObjectKernel;
-    registerObject(object: ObjectConfig): void;
-    unregisterObject(name: string): void;
-    getObject(name: string): ObjectConfig | undefined;
-    getConfigs(): Record<string, ObjectConfig>;
-    datasource(name: string): Driver;
+    getObject(name: string): ServiceObject | undefined;
     /**
-     * Introspect the database schema and automatically register objects.
-     * This allows connecting to an existing database without defining metadata.
+     * Get all registered object configs as a name→config map.
      *
-     * @param datasourceName - The name of the datasource to introspect (default: 'default')
-     * @param options - Optional configuration for schema conversion
-     * @returns Array of registered ObjectConfig
+     * Merges results from the upstream SchemaRegistry with the
+     * local MetadataRegistry (for pre-init objects).
      */
-    introspectAndRegister(datasourceName?: string, options?: {
-        excludeTables?: string[];
-        includeTables?: string[];
-        skipSystemColumns?: boolean;
-    }): Promise<ObjectConfig[]>;
-    close(): Promise<void>;
-    init(): Promise<void>;
-    private processInitialData;
+    getConfigs(): Record<string, ServiceObject>;
+    /**
+     * Remove all hooks, actions, and objects contributed by a package.
+     * Also cleans up the local MetadataRegistry.
+     */
+    removePackage(packageId: string): void;
 }