Skip to content

chore: release v0.8.0 #16

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
thomasjsk merged 1 commit into from
Sep 11, 2026
Merged

chore: release v0.8.0 #16

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 9 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/).

## [Unreleased]

## [0.8.0] - 2026-09-11

### Changed

- **BREAKING** `Agent.For` (`for`) is enforced on the blockchain-address roles
Expand All @@ -33,6 +35,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
implementation, so these messages were silently ignored by conformant peers.
Inbound bodies still accept `role` as a fallback.

### Fixed

- An agent with no owner no longer serialises `"for": null`: `omitempty` has no
effect on a struct field, so the key was always written. `Agent.For` is now
tagged `omitzero` and the key is omitted. Unmarshalling `null` also stopped
producing a single empty DID.

### Added

- `Agent.Validate()` and `ValidateAgents()` report TAIP-5 violations.
Expand Down
Loading