Skip to content

Conversation

@beonde
Copy link
Member

@beonde beonde commented Dec 19, 2025

Summary

Updates the GitHub Action to use capiscio-core v2.2.0, bringing it in sync with the latest release.

Changes

Version Update

  • Update CAPISCIO_VERSION from 1.0.2 to 2.2.0 in src/index.ts
  • Update README documentation to reference v2.2.0

Rebuild

  • Rebuild dist bundle with updated version using npm run build
  • Updated compiled JavaScript with new version constant

What's New in capiscio-core v2.2.0

The GitHub Action now downloads and uses capiscio-core v2.2.0, which includes:

  • RFC-003 Support: Key Ownership Proof (PoP) protocol with IAL-1 badges
  • Enhanced Badge Schema: Support for cnf, ial, nbf claims
  • Improved Scoring: Updated scoring algorithms
  • gRPC Server: Auto-starting gRPC server for SDK integration
  • New CLI Commands: badge keep, gateway start, rpc, key gen

Benefits

✅ Access to latest validation features
✅ RFC-003 PoP protocol support
✅ Improved badge verification with IAL claims
✅ Enhanced security with key binding validation
✅ Compatibility with v2.2.0 agent cards

Testing

  • Action installs correct binary version (v2.2.0)
  • Validation still works with existing agent cards
  • JSON output parsing works with new scoring format
  • All inputs/outputs function correctly

Breaking Changes

None - the action API remains unchanged. This is a transparent upgrade to the underlying binary.

- Update CAPISCIO_VERSION from 1.0.2 to 2.2.0
- Rebuild dist bundle with new version
- Update README to reflect v2.2.0 in documentation

This brings the GitHub Action in sync with the latest capiscio-core
release which includes RFC-003 PoP support and improved scoring.
@beonde beonde merged commit 91f0d14 into main Dec 22, 2025
1 of 2 checks passed
@beonde beonde deleted the feat/update-capiscio-core-v2.2.0 branch December 22, 2025 17:27
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