chore(release): v4.0.0-beta.98

[relsunkaev]

Prepares effect-qb and effect-db 4.0.0-beta.98 against Effect 4.0.0-beta.98. Eleven tracked files change. Local build, unit, type, pack, and live database gates pass; after merge, the release tag will be pushed to trigger npm and GitHub publication.

Why

The packages are currently pinned to Effect 4.0.0-beta.92 while the maintained Effect beta line is 4.0.0-beta.98.

• Consumers cannot use the current Effect beta without overriding exact peer and runtime dependencies.
• The intervening upstream changes compile and behave correctly under the existing querybuilder and database coverage.
• Two database correctness fixes and the repaired npm publishing path have landed since the beta.92 tag and need a published package version.

Key Changes

Effect compatibility:

• Align Effect core, Platform, PostgreSQL, MySQL, and Bun SQLite packages on beta.98.
• Update both public peer dependency declarations to require Effect beta.98.
• Refresh transitive lockfile resolutions from the beta.98 package graph.

Release payload:

• Set workspace, querybuilder, database, and CLI versions to 4.0.0-beta.98.
• Generate release notes from commits landed after beta.92.
• Keep the npm beta channel aligned across both packages.

Release correctness:

• Consume the Unreleased changelog body when a version section is generated.
• Prevent stale or already-shipped entries from being duplicated into future release notes.
• Add executable regression coverage for changelog generation.
• Make the packed-package smoke consumer install the Effect peer declared by effect-qb, preventing release fixtures from silently testing an older beta.

Mechanical changes:

• Update package and lockfile version metadata.
• Mark the tracked beta.98 release issue in progress.

Risks & Testing Needed

npm trusted publishing: The first new upload requires effect-qb and effect-db to trust repository workflow publish.yml.
→ Confirm both npm package settings before pushing the release tag.

Effect behavior: beta.98 changes Schema union dispatch and JSON classification behavior while removing unrelated Schedule and unstable HttpApi APIs.
→ Existing schema, JSON, executor, and type suites pass unchanged.

Packed consumer: A stale beta.92 literal originally produced peer warnings while the smoke script still exited successfully.
→ The script now derives Effect from the package peer declaration, and the rerun installs beta.98 without warnings.

Live databases: Driver dependency updates include newer PostgreSQL and MySQL client packages.
→ PostgreSQL, MySQL, SQLite, CLI, and datatype-matrix integration gates pass.

Not tested:

• Publishing a new immutable npm version remains intentionally deferred until this PR merges and npm trust is confirmed.

Build status: pass

Test Plan

bun install --frozen-lockfile
bun run build
bun test
bun run test:types
bunx npm pack --dry-run
bun run test:pack
bun run test:integration
bun run test:integration:datatypes

Release-specific regression:

bun test test/internal/behavior/release-script.behavior.test.ts

After merge:

git push origin v4.0.0-beta.98
gh run watch --exit-status

Rollback

git revert a136b10 aa335d6 cfff382 9b11c79 6bb2a5d

Rollback restores beta.92 dependency and package metadata. Published npm versions are immutable, so a post-publication rollback would require a new package version rather than moving beta.98.