fix(agents): the addressed-proposal example uses a substrate-neutral scheme #83
peersky
commented
Owner
- Fixed Bug example URI in the proposal-type test named a specific hosting substrate, which the enum's own docs say is expected to change and which the SDK should not pin
- Fixed Bug example URI in the proposal-type test named a specific hosting substrate, which the enum's own docs say is expected to change and which the SDK should not pin
peersky
added 1 commit 2026-08-26 15:32:09 +00:00
fix(agents): the addressed-proposal example uses a substrate-neutral scheme
All checks were successful
Publish Release / Create Tag & Sync (pull_request) Has been skipped
Details
Publish Release / Publish to crates.io (pull_request) Has been skipped
Details
Publish Release / Publish dry-run (no side effects) (pull_request) Has been skipped
Details
Publish Release / Create GitHub Release (pull_request) Has been skipped
Details
CI / Lint & Audit (pull_request) Successful in 1m11s
Details
CI / Dependency Age Check (pull_request) Successful in 3s
Details
CI / Spell Check (pull_request) Successful in 5s
Details
Commit Lint / Validate PR Title (pull_request) Successful in 3s
Details
CI / Test (pull_request) Successful in 5m6s
Details
peersky
merged commit 07356dbe2d into dev
peersky
deleted branch fix/proposal-uri-example-scheme
peersky
referenced this pull request from a commit
Merge pull request 'fix(agents): the addressed-proposal example uses a substrate-neutral scheme' (#83) from fix/proposal-uri-example-scheme into dev
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/proposal-uri-example-scheme"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?