Version Packages

[github-actions]

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

@ts-safeql/eslint-plugin@5.0.0

Major Changes

• 00b9904: BREAKING: Add ESLint 10 support to SafeQL.

Minor Changes

• acd33af: Add experimental plugin API and AWS auth plugin

  • Experimental plugin system for extending SafeQL with custom behavior
  • First official plugin: @ts-safeql/plugin-auth-aws for AWS RDS IAM authentication

Patch Changes

• Updated dependencies [00b9904]
• Updated dependencies [acd33af]
  • @ts-safeql/plugin-utils@5.0.0
  • @ts-safeql/connection-manager@4.2.1

@ts-safeql/plugin-utils@5.0.0

Major Changes

• 00b9904: BREAKING: Add ESLint 10 support to SafeQL.

Minor Changes

• acd33af: Add experimental plugin API and AWS auth plugin

  • Experimental plugin system for extending SafeQL with custom behavior
  • First official plugin: @ts-safeql/plugin-auth-aws for AWS RDS IAM authentication

@ts-safeql/zod-annotator@5.0.0

Major Changes

• 00b9904: BREAKING: Add ESLint 10 support to SafeQL.

Patch Changes

• Updated dependencies [00b9904]
• Updated dependencies [acd33af]
  • @ts-safeql/plugin-utils@5.0.0

@ts-safeql/plugin-auth-aws@4.3.0

Minor Changes

• acd33af: Add experimental plugin API and AWS auth plugin

  • Experimental plugin system for extending SafeQL with custom behavior
  • First official plugin: @ts-safeql/plugin-auth-aws for AWS RDS IAM authentication

Patch Changes

• Updated dependencies [00b9904]
• Updated dependencies [acd33af]
  • @ts-safeql/plugin-utils@5.0.0

@ts-safeql/shared@5.0.0

Minor Changes

• acd33af: Add experimental plugin API and AWS auth plugin

  • Experimental plugin system for extending SafeQL with custom behavior
  • First official plugin: @ts-safeql/plugin-auth-aws for AWS RDS IAM authentication

@ts-safeql/generate@5.0.0

Patch Changes

• Updated dependencies [acd33af]
  • @ts-safeql/shared@5.0.0
  • @ts-safeql/test-utils@0.0.61
  • @ts-safeql/sql-ast@5.0.0

@ts-safeql/test-utils@0.0.61

Patch Changes

• Updated dependencies [acd33af]
  • @ts-safeql/shared@5.0.0

@ts-safeql/sql-ast@5.0.0

@ts-safeql/connection-manager@4.2.1

Patch Changes

• Updated dependencies [00b9904]
• Updated dependencies [acd33af]
  • @ts-safeql/plugin-utils@5.0.0
  • @ts-safeql/shared@5.0.0

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
safeql	Ignored	Preview	Mar 21, 2026 8:50pm

[greptile-apps]

Greptile Summary

This is an auto-generated Changesets release PR bumping nine packages to publish the experimental plugin API and the new @ts-safeql/plugin-auth-aws AWS RDS IAM authentication plugin. All version bumps and CHANGELOG entries are consistent with the consumed changeset (acd33af), and internal cross-package references continue to use the workspace:* protocol, which will be resolved to pinned versions at publish time.

Key observations:

• @ts-safeql/sql-ast is bumped to 4.3.0 with a completely empty CHANGELOG entry. It has no @ts-safeql/* dependencies, so the bump is purely a version-sync artefact of the Changesets "linked" configuration — worth noting in the entry to avoid user confusion.
• @ts-safeql/connection-manager is marked "private": true, so its version bump and CHANGELOG update have no effect on npm consumers; they are harmless bookkeeping within the monorepo.
• @ts-safeql/test-utils appears as a tracked runtime dependency of @ts-safeql/generate (listed under dependencies, not devDependencies), which is pre-existing and outside the scope of this release PR but worth addressing separately.

Confidence Score: 5/5

• This PR is safe to merge — it is entirely auto-generated version and changelog bookkeeping with no logic changes.
• All changes are version bumps and CHANGELOG updates produced by the Changesets action. No source code is modified. The one minor observation (empty @ts-safeql/sql-ast changelog entry) is cosmetic and does not affect correctness or publishability.
• packages/ast-types/CHANGELOG.md — empty 4.3.0 entry may confuse consumers; consider adding a sync note.

Important Files Changed

Filename	Overview
packages/ast-types/CHANGELOG.md	4.3.0 entry is completely empty — no changes listed. The package has no internal dependencies that bumped, which suggests it is version-linked to the rest of the monorepo but the changelog gives no indication of why it was bumped.
packages/ast-types/package.json	Version bumped 4.2.0 → 4.3.0. No dependency changes; bump is version-synchronization only.
packages/connection-manager/package.json	Patch bump 4.2.0 → 4.2.1. Package is marked private so it won't be published to npm.
packages/eslint-plugin/CHANGELOG.md	Minor bump to 4.3.0 with correct entries for the experimental plugin system and AWS auth plugin.
packages/eslint-plugin/package.json	Minor bump to 4.3.0; internal dependencies use workspace:* protocol as expected.
packages/generate/CHANGELOG.md	Bumped to 4.3.0 (minor) despite only patch-level dependency updates; this is a side-effect of linked versioning. Also lists @ts-safeql/test-utils as a tracked dependency even though test utilities are runtime dependencies rather than devDependencies.
packages/plugin-utils/CHANGELOG.md	New CHANGELOG created for 4.3.0 minor; correctly describes the experimental plugin API introduction.
packages/plugins/auth-aws/CHANGELOG.md	New CHANGELOG created for 4.3.0 minor; correctly describes both the new plugin feature and the plugin-utils dependency bump.
packages/plugins/auth-aws/package.json	Minor bump to 4.3.0; uses workspace:* for plugin-utils as expected.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    CS[".changeset/plugin-system.md\n(deleted after consume)"]

    CS --> |"minor bump"| SHARED["@ts-safeql/shared\n4.2.0 → 4.3.0"]
    CS --> |"minor bump"| PLUGIN_UTILS["@ts-safeql/plugin-utils\n4.2.0 → 4.3.0"]
    CS --> |"minor bump"| AUTH_AWS["@ts-safeql/plugin-auth-aws\n4.2.0 → 4.3.0"]
    CS --> |"minor bump"| ESLINT["@ts-safeql/eslint-plugin\n4.2.0 → 4.3.0"]

    PLUGIN_UTILS --> |"patch (dep update)"| CONN_MGR["@ts-safeql/connection-manager\n4.2.0 → 4.2.1\n(private)"]
    PLUGIN_UTILS --> |"patch (dep update)"| ZOD_ANN["@ts-safeql/zod-annotator\n4.2.0 → 4.2.1"]

    SHARED --> |"patch (dep update)"| TEST_UTILS["@ts-safeql/test-utils\n0.0.60 → 0.0.61"]
    SHARED --> |"patch (dep update)"| CONN_MGR
    SHARED --> |"linked sync"| GENERATE["@ts-safeql/generate\n4.2.0 → 4.3.0"]

    LINKED_SYNC["Changesets 'linked' config\n(version sync)"] --> |"minor sync"| AST["@ts-safeql/sql-ast\n4.2.0 → 4.3.0\n⚠️ empty changelog"]

Loading

Prompt To Fix All With AI

This is a comment left during a code review.
Path: packages/ast-types/CHANGELOG.md
Line: 3-4

Comment:
**Empty changelog entry for `@ts-safeql/sql-ast@4.3.0`**

The `4.3.0` entry is completely empty — no changes or dependency updates are listed. Inspecting `packages/ast-types/package.json`, this package has no dependencies on any other `@ts-safeql/*` package, so the bump appears to be purely a version-synchronisation side effect of the Changesets "linked" configuration.

This is not incorrect, but it may be worth adding a note (e.g. `- Synchronized version with the rest of the @ts-safeql packages`) so consumers consulting the changelog understand why a new version was published with no observable changes.

How can I resolve this? If you propose a fix, please make it concise.

_{Last reviewed commit: "Version Packages"}

[greptile-apps]

Empty changelog entry for @ts-safeql/sql-ast@4.3.0

The 4.3.0 entry is completely empty — no changes or dependency updates are listed. Inspecting packages/ast-types/package.json, this package has no dependencies on any other @ts-safeql/* package, so the bump appears to be purely a version-synchronisation side effect of the Changesets "linked" configuration.

This is not incorrect, but it may be worth adding a note (e.g. - Synchronized version with the rest of the @ts-safeql packages) so consumers consulting the changelog understand why a new version was published with no observable changes.

Prompt To Fix With AI

This is a comment left during a code review.
Path: packages/ast-types/CHANGELOG.md
Line: 3-4

Comment:
**Empty changelog entry for `@ts-safeql/sql-ast@4.3.0`**

The `4.3.0` entry is completely empty — no changes or dependency updates are listed. Inspecting `packages/ast-types/package.json`, this package has no dependencies on any other `@ts-safeql/*` package, so the bump appears to be purely a version-synchronisation side effect of the Changesets "linked" configuration.

This is not incorrect, but it may be worth adding a note (e.g. `- Synchronized version with the rest of the @ts-safeql packages`) so consumers consulting the changelog understand why a new version was published with no observable changes.

How can I resolve this? If you propose a fix, please make it concise.

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}