chore(deps): bump wire-mesh-core from 1.13.0 to 1.30.0 - #133
Merged
Merged
Conversation
Brings in every domain primitive the P5 (core/data message history) and Section H (generic capability request/grant) work landed upstream since agent-comms last updated: listKnownDevices' DirectoryEntry/sendGossipUpdate wiring already in use, plus createRoomNotice, the data-have/data-request/data-entries sync protocol, and createNodeFsStorage, none of which existed in the previously-pinned version. Adds a pnpm-workspace.yaml override pinning trilean-regex to its own real published version: trilean@1.6.1's published package.json still declares that sibling dependency as an unrewritten workspace:^ range, which breaks resolution for every external installer (filed upstream as ExaDev/trilean#46, not yet fixed there). Fixes the one real breaking change this bump surfaces: RevocationCheck's contract changed from a boolean isRevoked(tokenId, issuer) to entriesFor(tokenId) returning every recorded entry (wire-mesh#84), which the one hand-built fake in this repo's own test suite still used.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
🎉 This PR is included in version 2.24.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings in every domain primitive P5's own investigation (agent-comms#50) and Section H's capability request/grant work landed upstream since this pin was last updated: createRoomNotice, the core/data sync protocol (data-have/data-request/data-entries), createNodeFsStorage, and the DirectoryEntry/sendGossipUpdate surface #130/#131 already depend on -- none of which existed in 1.13.0.
Adds a pnpm-workspace.yaml override pinning trilean-regex to its own real published version, since trilean@1.6.1's published package.json still declares it as an unrewritten workspace:^ range (ExaDev/trilean#46, filed but not yet fixed upstream) -- without it, pnpm add fails outright.
One real breaking change surfaced and fixed: RevocationCheck's contract changed from a boolean isRevoked(tokenId, issuer) to entriesFor(tokenId) (wire-mesh#84), which the one hand-built fake revocation check in this repo's own test suite still used.
Refs #50.