AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 15 Bitcoin

Introduce check to re-exports CI for error types

Public commit record

What the developer wrote

Authored by Mitchell Bagot

68/100 · Adequate
Introduce check to re-exports CI for error types

With the move to error submodules, we should move towards a policy for
error access. Specifically, for any foo::error::FooError, there should
also exist a foo::FooError. This has already been implemented in units
and primitives, but should also be enforced by CI in the case of new
errors.

Add check error reexport script and add to check re-exports CI action.

Assisted by Claude Opus 4.6.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit adds a new automated CI check (a shell script) that verifies every error type defined in a Rust submodule named `error` is also re-exported at the parent module level. It is a code-quality and API-consistency enforcement tool, not a security patch. It does not change any library code that handles Bitcoin data, cryptography, or network messages.

Recommended action

No security action required. Review as a normal CI/infrastructure change.

Security signals we found

No strong security signals were identified.

Risk score

Why this scored 15/100

Our methodology →
Potential impact 0/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 0/15
Confidence 10/10
Evidence quality 5/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.