Conversation
NikolayS
force-pushed
the
chore/stamp-v0.2.0-dev1
branch
from
3f3c9b0 to
5ef3724
Compare
This was referenced May 7, 2026
Bump client + SQL versions in lockstep: - pgque-py: 0.2.0 -> 0.2.0.dev1 - pgque-ts: 0.2.0 -> 0.2.0-dev.1 - pgque.version() / -- Version header / pg_tle wrapper: 0.2.0-dev -> 0.2.0-dev1 - regenerated sql/pgque.sql + sql/pgque-tle.sql via build/transform.sh Pre-release audit (#211): all four scoped audits green -- 67/67 Python, 69/69 TypeScript, 93/93 Go, 8/8 cross-client smoke. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Per advisor feedback for first public client distribution: rc reads
more cleanly across Python/npm/Go than dev, and dev -> rc is a normal
progression. PEP 440 accepts both .devN and rcN; we land on rc1.
- pgque-py: 0.2.0.dev1 -> 0.2.0rc1 (PEP 440 canonical)
- pgque-ts: 0.2.0-dev.1 -> 0.2.0-rc.1 (semver)
- pgque.version() / -- Version: header / pg_tle wrapper:
0.2.0-dev1 -> 0.2.0-rc.1
- regenerated sql/pgque.sql + sql/pgque-tle.sql via build/transform.sh
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
NikolayS
force-pushed
the
chore/stamp-v0.2.0-dev1
branch
from
5ef3724 to
ec04c37
Compare
36 tasks
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
1 participant
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
Pre-release dev drop stamp. Bumps client + SQL versions in lockstep to the first public client RC:
pgque-py:0.2.0→0.2.0rc1(PEP 440 canonical)pgque(npm):0.2.0→0.2.0-rc.1(semver)pgque.version()SQL +-- Version:header + pg_tle wrapper:0.2.0-dev→0.2.0-rc.1sql/pgque.sqlandsql/pgque-tle.sqlviabash build/transform.shCloses the audit phase of #211. The original audit targeted
dev1; we pivoted torc1per advisor feedback (cleaner mapping across Python/npm/Go for first public library distribution;dev → rcis a normal progression). The audit findings carry over unchanged — no SQL surface or client API differences between dev1 and rc1.Audit evidence (#211)
All four scoped audits ran against isolated PG 18 databases on a prior
main(b7ede47) and posted evidence comments on #211:pgque-py)pgque)pgque-go)Local re-verification on the rebased branch (origin/main + this PR, includes #219 pg_timetable scheduler + #222 release-workflow split):
bash build/transform.sh: clean assembly, all sanity checks PASSpsql -f sql/pgque.sqlon a fresh DB: install OK,pgque.version()returns0.2.0-rc.1psql -f tests/run_all.sql: 138 PASS, exit 0,=== ALL TESTS PASSED ===Test plan
v0.2.0-rc.1on the squash-merge commit after merge🤖 Generated with Claude Code