release: pin sub-modules to v0.5.0 - #88
Conversation
The eight satellites required v0.4.0, so a consumer building one without this repo's go.work compiled it against the published 0.4 core — which analyzes a query before the base driver answers, so every integration built on middleware.Guard still double-counted N+1 on MySQL, the bug v0.5.0 fixes. pgparser and mysqlparser also needed the core's row-inserting keyword support for their parity corpus. Verified with GOWORK=off, the only run that resolves the satellites against the real published tag rather than this tree: all 14 packages pass, and the go.sum entries confirm the proxy served v0.5.0 rather than a cached 0.4.
|
Skipping CodeAnt AI review — this PR is a back-merge between long-lived branches ( If you want to analyze this anyway (e.g. you resolved conflicts with new logic), comment |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Repository: KARTIKrocks/sqlguard/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🏁 CodeAnt Quality Gate ResultsCommit: ✅ Overall Status: PASSEDQuality Gate Details
|
Second of the two release PRs.
v0.5.0is tagged and pushed (5b7e8f8), sothe eight satellites can now point at it.
Why it matters this release
They required
v0.4.0, so a consumer building one without this repo'sgo.workcompiled it against the published 0.4 core — which analyzes a querybefore the base driver answers. Every integration is built on
middleware.Guard, so all six still double-counted N+1 on MySQL: exactly thebug
v0.5.0fixes.pgparserandmysqlparseralso need the core'srow-inserting keyword support for their parity corpus, which otherwise skips
rows rather than asserting them.
Verification
GOWORK=off make test— the only run that resolves the satellites against thereal published tag instead of this working tree:
All 14 packages pass. The
go.sumentries confirm the module proxy servedv0.5.0rather than a cached 0.4:After this merges
The eight
<mod>/v0.5.0tags, which is the last step of the release.