What the developer wrote
Authored by elnosh
Remove taproot build check
What changed, and why it matters
This commit removes a separate CI build step that tested the project with a special 'taproot' compiler flag. It is a workflow cleanup change, not a code change. There is no indication of a security vulnerability.
No security action needed. Review whether taproot-specific coverage is still required elsewhere in CI, but this is a normal maintenance decision.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch deletes the ‘Run cargo check for Taproot build’ job step in .forgejo/workflows/build.yml and merges its commands into the general release cargo check step. The removed step set RUSTFLAGS and RUSTDOCFLAGS to ‘–cfg=taproot’. This is purely a CI configuration simplification; no source code is modified.
Changed components
.forgejo/workflows/build.ymlInspect captured patch +0 / −8
diff --git a/.forgejo/workflows/build.yml b/.forgejo/workflows/build.yml
index 2a0d917..d58d014 100644
--- a/.forgejo/workflows/build.yml
+++ b/.forgejo/workflows/build.yml
@@ -218,20 +218,12 @@ jobs:
run: |
rustup default stable
- name: Run cargo check for release build.
- run: |
- cargo check --release
- cargo check --no-default-features --features=std --release
- cargo doc --release
- - name: Run cargo check for Taproot build.
run: |
cargo check --release
cargo check --no-default-features --release
cargo check --no-default-features --features=std --release
cargo doc --release
cargo doc --no-default-features --release
- env:
- RUSTFLAGS: '--cfg=taproot'
- RUSTDOCFLAGS: '--cfg=taproot'
check_docs:
runs-on: debian-trixie
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.