Repository navigation
build(deps): bump hakoniwa from d92991c to 31cb127 in the cargo group - #22
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the cargo group with 1 update: [hakoniwa](https://github.com/souk4711/hakoniwa). Updates `hakoniwa` from `d92991c` to `31cb127` - [Release notes](https://github.com/souk4711/hakoniwa/releases) - [Commits](souk4711/hakoniwa@d92991c...31cb127) --- updated-dependencies: - dependency-name: hakoniwa dependency-version: 31cb127620797a8dd7ba408620ac99e0b310d38f dependency-type: direct:production dependency-group: cargo ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
|
@dependabot rebase |
Contributor
Author
|
Looks like hakoniwa is no longer updatable, so this is no longer needed. |
8000
mitodrummer
added a commit
that referenced
this pull request
Sep 8, 2026
The arch stack that closed gominimal/arch#16 to #22 landed on main on 2026-09-07. Bind MCC to the sections instead of the issues: the `public` client kind and certify for it (§6.1.7, §5.7, §6.6), `GET /v1/nodes` with the liveness working values (§8.2, `ReadNode` §7.4), relay tickets and peer documents (§6.9, D7, T29), the mesh-attach host principal (§5.3), and the sessions-are-boxes decision mapping (§7.4). Liveness now comes from the node listing, not the peer document (MCC-015, MCC-070); the peer document gains its `seq` and staleness rule; the expected principal for a tunnel-addressed host is the node's canonical name (MCC-032); presence at the chain cap is a user gesture, never a fresh sign-in (MCC-040); the relay ticket is the arch's claim set with the §6.9 binding presented beside it for the mesh key (MCC-071). Remove the seven resolved open questions and add two the landed text raises: one key or two for DPoP and SSH, and the ticket's missing mesh-key claim. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019SN7GPDMfE3DbTayuqfnQG
mitodrummer
added a commit
that referenced
this pull request
Sep 8, 2026
The arch stack that closed gominimal/arch#16 to #22 landed on main on 2026-09-07. Bind MMI to the sections instead of the issues: the relay tier as architecture D7 with `sshpop-host` registration against the `relays` member of `gatehouse_node_endpoints` and the ticket's claim set (§6.9, T29), the daemon's mirror view of the peer document (§6.9 v1.14, MMI-010), `POST /v1/nodes/heartbeat` with the 60 s cadence, 30 s floor, monotonic `seq` and `reachability` shape (§8.2, MMI-060, MMI-061), sessions as boxes with the ownership interim ratified (§7.4, MMI-025 to MMI-028), host-cert principals as the canonical name and wildcard only, never the tunnel address (§5.3, MMI-029), and the §5.7 wall-warning rule (MMI-031). The ticket carries no mesh key, so MMI-071 takes it from the §6.9 binding the client presents beside the ticket. Remove the seven resolved open questions, keep the Unit 4 amendment as this repo's own, and add two: a `wg_pub` claim in the ticket, and the heartbeat payload superset. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019SN7GPDMfE3DbTayuqfnQG
This was referenced Sep 8, 2026
mitodrummer
added a commit
that referenced
this pull request
Sep 8, 2026
The arch stack that closed gominimal/arch#16 to #22 landed on main on 2026-09-07. Bind MCC to the sections instead of the issues: the `public` client kind and certify for it (§6.1.7, §5.7, §6.6), `GET /v1/nodes` with the liveness working values (§8.2, `ReadNode` §7.4), relay tickets and peer documents (§6.9, D7, T29), the mesh-attach host principal (§5.3), and the sessions-are-boxes decision mapping (§7.4). Liveness now comes from the node listing, not the peer document (MCC-015, MCC-070); the peer document gains its `seq` and staleness rule; the expected principal for a tunnel-addressed host is the node's canonical name (MCC-032); presence at the chain cap is a user gesture, never a fre 8000 sh sign-in (MCC-040); the relay ticket is the arch's claim set with the §6.9 binding presented beside it for the mesh key (MCC-071). Remove the seven resolved open questions and add two the landed text raises: one key or two for DPoP and SSH, and the ticket's missing mesh-key claim. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019SN7GPDMfE3DbTayuqfnQG
mitodrummer
added a commit
that referenced
this pull request
Sep 8, 2026
The arch stack that closed gominimal/arch#16 to #22 landed on main on 2026-09-07. Bind MMI to the sections instead of the issues: the relay tier as architecture D7 with `sshpop-host` registration against the `relays` member of `gatehouse_node_endpoints` and the ticket's claim set (§6.9, T29), the daemon's mirror view of the peer document (§6.9 v1.14, MMI-010), `POST /v1/nodes/heartbeat` with the 60 s cadence, 30 s floor, monotonic `seq` and `reachability` shape (§8.2, MMI-060, MMI-061), sessions as boxes with the ownership interim ratified (§7.4, MMI-025 to MMI-028), host-cert principals as the canonical name and wildcard only, never the tunnel address (§5.3, MMI-029), and the §5.7 wall-warning rule (MMI-031). The ticket carries no mesh key, so MMI-071 takes it from the §6.9 binding the client presents beside the ticket. Remove the seven resolved open questions, keep the Unit 4 amendment as this repo's own, and add two: a `wg_pub` claim in the ticket, and the heartbeat payload superset. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019SN7GPDMfE3DbTayuqfnQG
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
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.
Bumps the cargo group with 1 update: hakoniwa.
Updates
hakoniwafromd92991cto31cb127Commits
31cb127Merge pull request #114 from souk4711/dependabot/cargo/rust-dependencies-fd3f...07fb57cchore(deps): bump the rust-dependencies group with 3 updatesf67e9b3chore(deps): bump actions/checkout from 5 to 61074d1dMerge pull request #113 from souk4711/dependabot/cargo/rust-dependencies-2dc8...bcf87b4chore(deps): bump the rust-dependencies group with 9 updatesDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop 8000 Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions