JSPM – @babylonlabs-io/babylon-proto-ts@0.0.3-canary.7

Package Exports

@babylonlabs-io/babylon-proto-ts
@babylonlabs-io/babylon-proto-ts/dist/generated/babylon/btcstaking/v1/pop
@babylonlabs-io/babylon-proto-ts/dist/generated/babylon/btcstaking/v1/pop.js
@babylonlabs-io/babylon-proto-ts/dist/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@babylonlabs-io/babylon-proto-ts) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Babylon Logo

@babylonlabs-io/babylon-proto-ts

Babylon Bitcoin Staking Protocol

TypeScript library

👨🏻‍💻 Installation

npm i @babylonlabs-io/babylon-proto-ts

📝 Commit Format & Automated Releases

This project uses Conventional Commits and semantic-release to automate versioning, changelog generation, and npm publishing.

✅ How It Works

All commits must follow the Conventional Commits format.
When changes are merged into the main branch:
- semantic-release analyzes commit messages
- Determines the appropriate semantic version bump (major, minor, patch)
- Updates the CHANGELOG.md
- Tags the release in Git
- Publishes the new version to npm (if configured)

🧱 Commit Message Examples

feat: add support for slashing script
fix: handle invalid staking tx gracefully
docs: update README with commit conventions
refactor!: remove deprecated method and cleanup types

Note: For breaking changes, add a ! after the type ( e.g. feat!: or refactor!:) and include a description of the breaking change in the commit body.

🚀 Releasing

Just commit your changes using the proper format and merge to main. The CI pipeline will handle versioning and releasing automatically — no manual tagging or version bumps needed.