fix: change objectql changeset from minor to patch to prevent unintended 4.0.0 bump

[Copilot]

changeset version bumps all packages from 3.0.3 → 4.0.0 instead of a patch release. Root cause: upgrade-objectql-core.md specifies minor for @objectstack/objectql, which in the fixed version group triggers a major bump across all 21 packages.

• Changed '@objectstack/objectql': minor → '@objectstack/objectql': patch in .changeset/upgrade-objectql-core.md

Verified pnpm exec changeset version now correctly produces 3.0.4 for all packages.

Original prompt

我只是想发一个补丁，为什么changeset的帮我升级到了4.0

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
objectstack-play	Ready	Preview, Comment	Feb 14, 2026 8:55am
spec	Ready	Preview, Comment	Feb 14, 2026 8:55am

[Copilot]

Pull request overview

Adjusts the Changesets bump level for @objectstack/objectql to avoid an unintended repo-wide major version bump caused by the fixed versioning group configuration.

Changes:

• Updated .changeset/upgrade-objectql-core.md to bump @objectstack/objectql as patch instead of minor.

[Copilot]

Switching this changeset to a patch avoids the fixed-group major bump, but it also means the release will be published as a patch even though the changeset text describes new features (new exports like utility functions / kernel factory). If these are public API additions, consider whether the team still wants a patch (and update the release note wording accordingly), or alternatively adjust the versioning strategy (e.g., accept a minor/major bump) to keep SemVer expectations aligned.

Suggested change

	'@objectstack/objectql': patch
	'@objectstack/objectql': minor