chore(ci)(deps): bump actions/labeler from 5 to 6 - #17
Merged
mmacedoeu merged 2 commits intoFeb 25, 2026
Merged
Conversation
Bumps [actions/labeler](https://github.com/actions/labeler) from 5 to 6. - [Release notes](https://github.com/actions/labeler/releases) - [Commits](actions/labeler@v5...v6) --- updated-dependencies: - dependency-name: actions/labeler dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
dependabot
Bot
deleted the
dependabot/github_actions/next/actions/labeler-6
branch
February 25, 2026 16:49
mmacedoeu
added a commit
that referenced
this pull request
Aug 3, 2026
…liation Landing 0968a2 implementation. Closes 7 of 17 ACs directly; the remaining 10 are either pure verification (AC #1) or blocked by external dependencies (AC #7-8 chain-substrate selection, AC #9-11 live anchor plumbing, AC #13 config crate path, AC #16 0855p-b successor). Direct closes: - AC #2 (governance fields on ReputationAnchorBatch): added governance_snapshot, governance_proof, governance_set_hash fields to crates/octo-reputation/src/anchor.rs:140 with full digest folding. The 3 governance types live at auth.rs as AnchorGovernanceSnapshot / AnchorGovernanceSigner / AnchorGovernanceProof (path (a) mandated; preserves existing GovernanceSnapshot/GovernanceProof at auth.rs:21-25/113+). - AC #3 (batch_size: u32): RFC-0955-R1 line 173 mandate. Added batch_size field; within_leaf_cap() now requires batch_size == leaves.len(). - AC #4 (chain_block_height: Option<u64>): RFC-0955-R1 line 170 mandate. None at submission, Some(h) after MIN_FINALITY_BLOCKS finality. Digest uses Option tag encoding (0x00 None, 0x01 || 8 bytes BE Some). - AC #5 (AnchorLeaf::digest field order): per RFC-0955-R1 lines 420-422, score_ewma_raw now at position 5 (between last_event_id and last_event_unix). The previous last-position was a cross-implementation interoperability bug. - AC #6 (v012 migration): new crates/octo-reputation/migrations/v012__reputation_anchors_governance.sql extending reputation_anchors with governance_snapshot BLOB, governance_proof BLOB, governance_set_hash BLOB + lookup index on governance_set_hash. BUILTIN_MIGRATIONS bumped. - AC #12 (anchor-specific verifier types): path (a) types defined in crates/octo-reputation/src/auth.rs. meets_quorum() enforces exactly GOVERNANCE_QUORUM (3) distinct signers. - AC #17 (canonical test vector re-pinning): the 3 pinned vectors in tests/canonical_blobs.rs re-pinned to the new canonical serialisation. An independent Python implementation using hashlib.blake3 MUST reproduce these bytes byte-identically per RFC-0955-R1 line 422. Verification: cargo fmt + clippy -D warnings clean; cargo test --lib 197 passed; canonical_blobs 5/5 passed; stoolap_integration 47/48 passed (1 pre-existing flaky K=2 race test — fails before this commit too, acknowledged in the test's R22 comment as non-deterministic). External blockers remaining for 0968a2 closure: - AC #7/8 live ChainAnchorSubmitter (chain-substrate selection RFC) - AC #9/10 reorg + DID-rotation finality handlers (need AC #7) - AC #11 governance signature verification (needs governance key infra) - AC #13 per-deployment config plumbing (config crate path TBD) - AC #16 gossip cross-reference (needs 0855p-b successor mission) Implementation pattern: anchor_job.rs::plan_batches returns batches with placeholder governance fields (None chain height, zero snapshot/proof/set_hash, leaves.len() batch_size). Runtime populates them with active snapshot + 3-of-3 quorum proof before calling ChainAnchorSubmitter::submit. Keeps plan_batches chain-substrate-agnostic.
mmacedoeu
added a commit
that referenced
this pull request
Aug 7, 2026
… AC grounding
R7 review findings closed:
MAJOR (governance type collision): mandate path (a) — new anchor-specific types in same module — verified against current IMPL at crates/octo-reputation/src/{auth.rs:399-603, anchor.rs:174-208, anchor.rs:233+}; existing auth.rs::GovernanceSnapshot (L21-25) + GovernanceProof (L113+) preserved unchanged as RFC-0968 authorization envelopes (slash/suspension flows); new AnchorGovernanceSnapshot/AnchorGovernanceSigner/AnchorGovernanceProof/AnchorSignature types + 5 unit tests cover the anchor binding schema.
NIT (duplicate sentence): file no longer contains duplicate (prior edits removed it).
AC grounding updates — 7 ACs flipped to [x]:
- AC #2 governance fields (72bf19d + 48cf997 + b0660c3)
- AC #3 batch_size: u32 (same)
- AC #4 chain_block_height: Option<u64> (same)
- AC #5 AnchorLeaf::digest field order (b0660c3)
- AC #6 v012 migration (file shipped)
- AC #12 anchor-specific verifier types (72bf19d)
- AC #1 StakeBelowMinimum 0x2D verification (013a567)
10 ACs deferred per [[deferred-vs-unspecified]] named-owner rule to chain-substrate selection RFC + 0855p-b successor: #7/#8 live ChainAnchorSubmitter + rotation_receipt_id wire-through, #9/#10 reorg + DID-rotation finality handlers, #11 governance signature verification runtime hook (meets_quorum helper landed), #13 per-deployment config plumbing, #14/#15 idempotency + failure isolation tests, #16 gossip cross-reference, #17 canonical test vector re-pinning.
Version History v0.2 added; mission text no longer contradicts IMPL state.
63 insertions, 78 deletions.
mmacedoeu
added a commit
that referenced
this pull request
Aug 25, 2026
… F-P6.7-1: plan v1.5 → v1.6 local edit (step 3 removed; verification rewritten; session count 27-46 → 26-44; §Risks #17 HIGH → LOW). F-P6.7-2: corpus STATE post-R6 verification (176 raw STALE = 0 effective per F-P6.6-1 re-classification). F-P6.7-3: Phase 6.1 scope reduced 16-21 → 5 commits (62.5-95.2% reduction). R7 = FIRST 0-NEW of round 3. R5 closure superseded by R7 (plan v1.6 reflects F-P6.6-3 correction). R8 plan: final post-correction verification + re-DRY closure.
mmacedoeu
added a commit
that referenced
this pull request
Aug 25, 2026
…cker) Unblocks RFC-0968-A2 v0.8.1 AC #17 (gossip consumer rejects stale anchor_tx_hash: None events) + AC #18 (3 canonical test vector re-pinning coordination). Mission owns filter_stale_anchor_events function in crates/octo-network/src/gossip/reputation.rs + 7 TV fixtures in tests/canonical_blobs.rs. This is the smaller of 2 external blockers blocking RFC-0968-A2 substrate (19 of 27 ACs DEFERRED). Larger blocker = chain-substrate selection RFC (separate work; unblocks 0968a2 ACs #9-#16). Per RFC-0968-A2 v0.8.1 freshness gate mandate: MAX_ANCHOR_STALENESS_BLOCKS = 256; drops GossipEnvelope with anchor_tx_hash: None + chain_block_height older than window. Preserves all anchor_tx_hash: Some(_) envelopes. Guard 2: 15/15 VALID. NO PUSH per feedback_initiation_user_only.
mmacedoeu
added a commit
that referenced
this pull request
Sep 8, 2026
…persession)
Mission status: OPEN -> CLOSED. 0 of 7 ACs landed. Drift audit findings:
(a) RFC citation drift (CRITICAL): cited RFC-0968-A2 v0.8.1 was the
Discriminant Stability Sub-amendment, NOT a freshness gate spec.
The MAX_ANCHOR_STALENESS_BLOCKS = 256 constant was undefined in any
RFC (closest analogue is RFC-0955-R1 §Finality MIN_FINALITY_BLOCKS = 12
— reorg-invalidation depth, semantically distinct).
(b) Substrate path drift (HIGH): claimed crates/octo-network/src/gossip/
reputation.rs is producer-side, not consumer-side ingress; canonical_blobs.rs
lives at crates/octo-reputation/tests/canonical_blobs.rs (NOT
crates/octo-network/tests/canonical_blobs.rs).
(c) Field path drift (HIGH): anchor_tx_hash lives on SignalEvent
(types.rs:289); chain_block_height lives on ReputationAnchorBatch
(anchor.rs:184); neither on GossipEnvelope.
(d) Layer drift (MEDIUM): octo-network is Layer C specialized network node,
not Layer B.
Predecessor chain (DELIVERED): 0855p-b-cross-mission-reputation Archived
Completed 2026-07-27 + 0968a2-reputation-anchoring-binding PARTIAL LANDED
2026-08-24 retro-supersession collectively delivered the anchor-event
freshness work; canonical_blobs.rs re-pinned 2026-07-30 under mission
0968a2 AC #17 annotation (L36-46).
0 external references verify: closing does NOT unblock or break any other
artifact. File retained in missions/claimed/ per R19 historical-mission-
preservation discipline. Per ciph Herocto Design Principles §Stable
Abstractions: no substrate code invented to match unbacked spec.
Audit closure: docs/audits/2026-09-03-0855p-b-gossip-successor-drift.md
(scratchpad, gitignored per docs-audits-scratchpad).
NO PUSH per feedback_initiation_user_only. Cross-RFC gaps (RFC-0855p-b
base CoordinatorRecord/Lifecycle/Source/Id substrate missing per upstream
investigation 2026-09-03) out of scope for this closure; documented in
the audit doc for follow-on.
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.
Bumps actions/labeler from 5 to 6.
Release notes
Sourced from actions/labeler's releases.
... (truncated)
Commits
634933epublish-action upgrade to 0.4.0 from 0.2.2 (#901)f1a63e8Update Node.js version to 24 in action and dependencies (#891)b0a1180Bump@octokit/request-errorfrom 5.0.1 to 5.1.1 (#846)110d441Update README.md (#871)bee50feBump undici from 5.28.4 to 5.28.5 (#842)6463cdbBump eslint-plugin-jest from 28.9.0 to 28.11.0 (#839)c209686Bump typescript from 5.7.2 to 5.7.3 (#835)5184940Bump@vercel/nccfrom 0.38.1 to 0.38.3 (#830)3629d55Document update - permission section (#840)d24f7f3Bump ts-jest from 29.1.2 to 29.2.5 (#831)Dependabot 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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)