Skip to content

jpdev v0.2.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 20 Oct 16:30
· 31 commits to main since this release
v0.2.0
ccecc76
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

jpdev v0.2.0

The second release of the development kit, the first through its release workflow, and the first public one.

What it holds

  • The kit is public. The repository carries the contributor files the other Judgment Pack repositories carry (CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, NOTICE, the pull-request template, Dependabot for the actions), the release workflow (an annotated tag on main, the CI jobs at the tag, a reproducible git archive tarball with checksums.txt, provenance attestations for both, a draft from the notes, publication behind the release environment), and docs/releasing.md with the verification form.
  • The kit on itself. dev.json, scripts/dev/check.sh, AGENTS.md and CLAUDE.md from its own templates; the lint and tests jobs run through the runner.
  • The manifest's venv applies to every step (#3): a node or go step that calls a python script now sees the venv's interpreter first on the PATH, as the python steps did; the toolchain still decides the cap. Found by the spec and gateway adoption reviews.
  • The runner template records its version (#3): templates/check.sh line 2 names the kit version; the release workflow asserts it matches the tag and that the kit's own vendored copy is byte-identical. Repositories that vendored the v0.1.0 template carry no such line until they re-vendor.
  • The go toolchain takes a version (#2): dev.json can name the Go release a repository is measured on; templates/ci-check.yml reads it and falls back to go-version-file; jpdev setup selects it where installed and says so where not.
  • The tarball holds examples/, which the shipped README.md and docs/adopting.md point to (from the v0.2.0 prep's review).

Adopting repositories

Re-vendor scripts/dev/check.sh from templates/check.sh at this tag so the line-2 version is present, and add go.version to dev.json where CI pins a Go release. Nothing else changes for an adopted repository.

Installing and verifying

Download the tarball and checksums.txt from this release, check the digest, and verify both attestations as docs/releasing.md describes before linking bin/jpdev into your PATH.

Assets 4
Loading