Skip to content

fix: push git tags and create GitHub Release after npm publish #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ignromanov merged 4 commits into from
Jun 4, 2026
Merged

fix: push git tags and create GitHub Release after npm publish #47

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
83c9d79
ci(release): push tags and create GitHub Release after publish
ignromanov Jun 4, 2026
8c93e5a
docs(readme): reflect npm publish done, remove "not yet published" no…
ignromanov Jun 4, 2026
239f146
ci(release): publish void-layer-codec to crates.io via OIDC trusted p…
ignromanov Jun 4, 2026
f151b8a
fix(release): correct tag push and GitHub Release on workflow_dispatch
ignromanov Jun 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,3 +23,20 @@ jobs:
- run: pnpm changeset publish
env:
NPM_CONFIG_PROVENANCE: true
- name: Push git tags
run: git push origin --tags
- name: Derive version
id: ver
run: echo "v=v$(node -p "require('./packages/codec/package.json').version")" >> "$GITHUB_OUTPUT"
- name: Create GitHub Release
uses: softprops/action-gh-release@b4309332981a82ec1c5618f44dd2e27cc8bfbfda # v3.0.0
with:
tag_name: ${{ steps.ver.outputs.v }}
generate_release_notes: true
- name: Obtain crates.io OIDC token
uses: rust-lang/crates-io-auth-action@bbd81622f20ce9e2dd9622e3218b975523e45bbe # v1.0.4
id: crates-io-auth
- name: Publish to crates.io
run: cargo publish -p void-layer-codec --manifest-path packages/codec/Cargo.toml
env:
CARGO_REGISTRY_TOKEN: ${{ steps.crates-io-auth.outputs.token }}
10 changes: 4 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,24 +6,22 @@ Canonical Invoice codec — TLV + Brotli wire format. v1 schema LOCKED forever.

## Status

Phase 2 complete — Rust + WASM codec shipped (0.1.0). Phase 3: npm publish + voidpay.xyz cutover.
Phase 2 complete — Rust + WASM codec shipped. Phase 3: npm publish done (0.1.0 live). Remaining: voidpay.xyz cutover (C1 / vl-app #120).

## Packages

| Package | Status | Description |
|---------|--------|-------------|
| `@void-layer/codec` | 0.1.0 ready | Rust + WASM canonical TLV codec |
| `@void-layer/types` | 0.1.0 ready | Manual TypeScript types (zero runtime deps) |
| `@void-layer/networks` | 0.1.0 ready | EVM chain configs + token list (no RPC keys) |
| `@void-layer/codec` | 0.1.0 — live on npm | Rust + WASM canonical TLV codec |
| `@void-layer/types` | 0.1.0 — live on npm | Manual TypeScript types (zero runtime deps) |
| `@void-layer/networks` | 0.1.0 — live on npm | EVM chain configs + token list (no RPC keys) |

## Quick Install

```bash
pnpm add @void-layer/codec
```

> Not yet published — Phase 3

## Why

- Third-party developers building on top of VoidPay need a stable, versioned codec they can depend on
Expand Down