mirror of https://github.com/zap-proto/spec.git synced 2026-10-30 15:04:03 +00:00

Files

T

History

zeekay 5a7ec0cf9b publish: stop dual-publishing zapc (npm) and zap-proto (PyPI); one owner each

Enforce a single canonical publisher per package name. spec/ was racing two
other repos for the same registry names; last-tagger-wins or 403.

npm @zap-proto/zapc -> owned by zap-proto/rust (live 1.0.0, `npx @zap-proto/zapc`).
  spec's npm-packages job published a DIFFERENT @zap-proto/zapc (optionalDeps on
  5 @zap-proto/zapc-<plat> packages — none of which ever made it to the registry).
  Removed the npm-packages job and deleted the dead npm/ dir so spec can no longer
  collide with rust's package.

PyPI zap-proto -> owned by zap-proto/py (live 1.2.0). spec's reserve/zap-proto-py
  publish step (1.0.0, continue-on-error) could clobber py's real package on a
  future spec bump. Removed it (and the reserve/zap-protocol-py step) — spec's
  pypi job now publishes only its own zap-schema.

Metadata: fix wrong-org Go import in schema/zap.capnp
  (github.com/zap-protocol/zap-go -> github.com/zap-proto/go, matching go/go.mod).

Hygiene: untrack 3876 committed reserve/*/target build artifacts (these stale
  snapshots were the only place the wrong-org github.com/zap-protocol/zap URL
  survived) and add **/target/ to .gitignore so they can't return.

Ownership rules documented in a banner at the top of release.yml.

2026-06-21 01:09:17 -07:00

src

feat: major v0.2.1 refactoring with .zap schema format

2026-03-12 23:21:05 -07:00

Cargo.toml

feat: major v0.2.1 refactoring with .zap schema format

2026-03-12 23:21:05 -07:00

README.md

feat: major v0.2.1 refactoring with .zap schema format

2026-03-12 23:21:05 -07:00