Repository navigation
chore: align sqb with the Panates repository standards - #121
Merged
Merged
Conversation
The version bump, the source stamps and the changelog entry are written on 'main' by `rman version`. Merging them back keeps this branch reporting the version that actually shipped, and keeps the next pull request carrying only its own work. [skip ci]
SECURITY.md and CODE_OF_CONDUCT.md come from the panates plugin templates (repository-setup). The issue templates ask for the package, the database and driver, the Node.js version and the generated SQL.
Version updates come from rman deps (ai-harness #5); Renovate never opened a pull request here.
The same root scripts as every repository (ai-harness #3): rman lint, rman check, rman format.
GitHub strips style attributes, so style="text-align: center" did not center the logo. align="center" does (ai-harness #6).
build/, .env.* (except .env.example) in .gitignore; /.claude and /graphify-out in .prettierignore.
The shared settings offer the panates plugin from panates/ai-harness and turn off the Co-Authored-By trailer. .gitignore now ignores only .claude/settings.local.json and .claude/worktrees/, so machine-local hooks stay out of the repository.
Node.js 20 is end of life and CI tests on 22 and later. Older versions may still work; they are no longer tested. The sqlite package keeps >=22.5.0, the first release with node:sqlite.
private: true in each source manifest stops a publish from the source directory (ai-harness #1). rman writes the published manifest into build/ without it; checked with rman build.
@nestjs/common, @nestjs/core, @nestjs/platform-express and @nestjs/testing ^12.3.3, @panates/eslint-config and @panates/eslint-config-ts ^2.3.5, @panates/rman-preset ^2.2.2, @swc/core ^1.16.21, @swc/helpers ^0.5.24, globals ^17.14.0, tslib ^2.9.1, valgen ^7.0.7, and the lockfile. Lint, check and build pass; tests as on dev (789 passing, 8 that need a database server).
One sentence under the logo and the documentation link line under the badges (ai-harness #6). Node Compatibility says 22 or later, as the manifests do now. The license is BSD 3-Clause, as LICENSE and every package.json say, not MIT. Links point to panates/sqb, and the coverage link to dev.
Every package README now has the package name as H1 and one sentence under the logo (ai-harness #6), says Node.js 22 or later, and names the BSD 3-Clause license with an absolute link, since npm shows these files without the repository. The oracle, postgres and sqljs sentences say they are adapters: their package.json descriptions call them serialization extensions.
CLAUDE.md held only the shared sections. ai-harness #7 asks for a project summary, the directory layout and repository-specific traps; the trap here is that database suites need the servers CI starts.
No code reads INIT_POSTGRES, INIT_MONGODB or INIT_SQB, which .mocharc.cjs set, and packages/common no longer exists. Lint passes; tests as on dev (789 passing, 8 that need a database server).
chore: align sqb with the repository standards
main takes pull requests from dev only (ai-harness git-workflow). The main-from-dev workflow is the panates plugin template: it reads nothing and passes the branch names through env.
Their package.json descriptions said serialization extension, which is what the -dialect packages are. npm shows the description on the package page.
chore: finish aligning sqb with the repository standards
rman finds workspace members in pnpm-workspace.yaml since 2.39.0, so the comment saying it still reads package.json's workspaces was out of date (panates/ai-harness#9), and the workspaces field only repeated the list. rman build still builds all 18 projects.
chore: read the workspace from pnpm-workspace.yaml only
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Releases #118, #119 and #120: sqb now follows the Panates repository standards (panates/ai-harness #1 to #9). Only
chore:,docs:andci:commits, so this is a patch release.engines.nodeis>=22(the sqlite package keeps>=22.5.0, the first release withnode:sqlite). Package sources areprivate: true;rman buildwritesbuild/package.jsonwithout it, so the published manifests do not change in that respect. Dependencies upgraded withrman deps -u. The oracle, postgres and sqljs descriptions say adapter.CODE_OF_CONDUCT.md,SECURITY.md, issue templates, a committed.claude/settings.json, project notes in CLAUDE.md;renovate.jsonand unused test variables removed; the workspace is read frompnpm-workspace.yamlonly.main-from-devfails a pull request into main from any branch but dev; this pull request is its first run here.Release note
Node.js 22 or later is now the declared minimum (
@sqb/sqlite: 22.5). Older versions are no longer tested. No API changes.Test plan
rman ci,rman check,rman lint,rman buildpnpm testlocally: 789 passing; the 8 suites that need a database server failed for lack of one, the same as beforemain-from-dev