Skip to content

docs(agents): v0.1.1 verification notes and a deterministic PGX version check for the Skill - #33

Merged
alexshapalov merged 1 commit into
mainfrom
docs/release-0.1.1-verification
Oct 26, 2026
Merged

alexshapalov merged 1 commit into
mainfrom
docs/release-0.1.1-verification

Conversation

@alexshapalov

Copy link
Copy Markdown
Contributor

Follow-up to #31/#32 after the v0.1.1 release:

  • The Claude Code validation note gains the three runs made after the review fixes: fail-closed live ($0.75), re-validation on the release code ($1.05), and the final run with the public v0.1.1 darwin-arm64 artifact and the Skill installed from public main ($0.80, 7 turns, 53 s): branch created by the hook, migration and tests green, template and developer PostgreSQL unchanged.
  • skills/pgx/scripts/check-pgx.sh: the Skill's version gate as a script. One JSON line; exit 0 compatible, 2 too old, 3 missing, 4 malformed; reads pgx --json version only. Tests cover missing, 0.1.0, 0.1.1, 0.2.0, a CI build string, garbage and empty output. SKILL.md and installation.md point at it; the skill test suite runs it.
  • agents.md and README state the PGX 0.1.1 floor with the release link.

No code changes to the CLI.

🤖 Generated with Claude Code

…on check for the Skill

- validation note: the fail-closed live run, the re-validation on the release
  code, and the final run with the public v0.1.1 artifact (costs recorded)
- skills/pgx/scripts/check-pgx.sh: one JSON line and exit 0/2/3/4 for
  compatible/too old/missing/malformed, from pgx --json version (never from
  pgx agent --help, which exits 0 on every version); tests for all four
- SKILL.md, installation.md, agents.md, README: PGX 0.1.1 or newer, with the
  release link

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@alexshapalov
alexshapalov merged commit 2ba260e into main Oct 26, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant