-
Notifications
You must be signed in to change notification settings - Fork 0
Release v1.9.1 - Patch version bump across packages #111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: huangyiirene <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR performs a synchronized patch version bump across the ObjectQL monorepo, incrementing all packages from version 1.9.0 to 1.9.1 (for core packages) and applying corresponding patch increments to driver and example packages. The changes are purely version-related, updating package.json version fields and adding standardized CHANGELOG.md entries documenting the release.
Changes:
- Core foundation packages (@objectql/types, @objectql/core, @objectql/platform-node) bumped from 1.9.0 to 1.9.1
- Runtime and tool packages (@objectql/cli, @objectql/server) bumped from 1.9.0 to 1.9.1
- Primary driver packages (@objectql/driver-sql, @objectql/driver-mongo, @objectql/driver-redis, @objectql/sdk) bumped from 1.9.0 to 1.9.1
- Secondary driver packages receive patch increments (e.g., driver-fs: 0.1.0 → 0.1.1)
- All example projects updated to reflect new dependency versions
- CHANGELOG.md files updated with standardized release notes across all modified packages
Reviewed changes
Copilot reviewed 42 out of 42 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| packages/foundation/types/package.json | Core types package version bump to 1.9.1 |
| packages/foundation/core/package.json | Runtime engine version bump to 1.9.1 |
| packages/foundation/platform-node/package.json | Node.js platform utilities version bump to 1.9.1 |
| packages/tools/cli/package.json | CLI tools version bump to 1.9.1 |
| packages/tools/create/package.json | Project creation tool version bump to 1.0.2 |
| packages/runtime/server/package.json | HTTP server adapter version bump to 1.9.1 |
| packages/drivers/sql/package.json | SQL driver version bump to 1.9.1 |
| packages/drivers/mongo/package.json | MongoDB driver version bump to 1.9.1 |
| packages/drivers/redis/package.json | Redis driver version bump to 1.9.1 |
| packages/drivers/sdk/package.json | Remote HTTP client version bump to 1.9.1 |
| packages/drivers/memory/package.json | In-memory driver version bump to 0.1.2 |
| packages/drivers/localstorage/package.json | LocalStorage driver version bump to 0.1.2 |
| packages/drivers/fs/package.json | Filesystem driver version bump to 0.1.1 |
| packages/drivers/excel/package.json | Excel driver version bump to 0.2.1 |
| All CHANGELOG.md files | Standardized patch release entries documenting version bump |
| Example package.json files | Updated dependency versions to reference new package versions |
|
@copilot 是否应该统一版本号。 |
Currently, the monorepo uses a "fixed group" versioning strategy where 9 core packages are synchronized at v1.9.1 (types, core, platform-node, cli, server, driver-sql, driver-mongo, driver-redis, sdk), as defined in Other packages (driver-fs, driver-localstorage, driver-memory, driver-excel, create, vscode-objectql) have independent versions because they were added later or are experimental. Would you like me to:
Please clarify which approach you prefer. |
Bumps all ObjectQL packages to v1.9.1 using the changesets workflow.
Changes
Core packages (synchronized group):
1.9.0→1.9.1Driver packages: patch version increments
0.1.0→0.1.10.1.1→0.1.20.1.1→0.1.20.2.0→0.2.11.0.1→1.0.2CHANGELOG.md files updated for all packages and examples
Publishing
After merge, run:
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
fastdl.mongodb.org/usr/local/bin/node /usr/local/bin/node /home/REDACTED/work/objectql/objectql/node_modules/.pnpm/[email protected]/node_modules/jest-worker/build/processChild.js(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.