Skip to content

[Sync] Update project files from source repository (1299e85)#270

Merged
mrz1836 merged 1 commit intomasterfrom
chore/sync-files-bitcoin-schema-20260205-153011-1299e85
Feb 5, 2026
Merged

[Sync] Update project files from source repository (1299e85)#270
mrz1836 merged 1 commit intomasterfrom
chore/sync-files-bitcoin-schema-20260205-153011-1299e85

Conversation

@mrz1836
Copy link
Member

@mrz1836 mrz1836 commented Feb 5, 2026

What Changed

  • Updated GOVULNCHECK_GO_VERSION from 1.25.6 to 1.25.7 in .github/.env.base
  • Updated GO_COVERAGE_VERSION from v1.1.17 to v1.2.0 in .github/.env.base
  • Updated MAGE_X_VERSION from v1.18.7 to v1.19.2 in .github/.env.base
  • Added copying of raw coverage.out file to output directories in both main and branch-specific coverage processing steps in fortress-coverage.yml

Why It Was Necessary

  • Newer versions of tooling dependencies provide bug fixes, security patches, and improved functionality
  • The raw coverage.out file needs to be included in coverage artifacts for downstream consumption and debugging
  • Keeping govulncheck updated ensures accurate vulnerability detection against the latest Go standard library

Testing Performed

  • Version updates are published releases from upstream tool repositories
  • Coverage file copying logic can be validated through CI workflow execution
  • Existing CI checks will verify compatibility of updated tool versions

Impact / Risk

  • Low Risk: Version bumps are minor/patch updates that should maintain backward compatibility
  • Improved Functionality: Raw coverage data will now be available in both main and branch-specific artifact downloads
  • No Breaking Changes: Configuration changes are additive and don't modify existing behavior

Copilot AI review requested due to automatic review settings February 5, 2026 20:30
@mrz1836 mrz1836 self-assigned this Feb 5, 2026
@mrz1836 mrz1836 added automated-sync Automated sync PR, e.g. from a fork or external repo automerge Label to automatically merge pull requests that meet all required conditions chore Simple dependency updates or version bumps labels Feb 5, 2026
@github-actions github-actions bot added update General updates size/M Medium change (51–200 lines) labels Feb 5, 2026
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR syncs workflow and configuration updates from the mrz1836/go-broadcast repository (commit 1299e85) to BitcoinSchema/go-bitcoin. The changes primarily update tool versions and enhance coverage reporting capabilities by including raw coverage data files in artifacts.

Changes:

  • Updated three tool versions: GOVULNCHECK (1.25.6→1.25.7), GO_COVERAGE (v1.1.17→v1.2.0), and MAGE_X (v1.18.7→v1.19.2)
  • Added raw coverage.out file to coverage artifacts for both main and branch-specific outputs
  • Added coverage threshold enforcement step to fail builds when coverage drops below configured thresholds
  • Optimized base64 decoding in completion workflow to avoid redundant decode operations

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File Description
.github/.env.base Updates versions for govulncheck, go-coverage, and mage-x tools
.github/workflows/fortress.yml Updates repository comment reference (has issue - points to wrong repo)
.github/workflows/fortress-coverage.yml Adds coverage.out file copying, threshold enforcement step, and includes coverage.out in all file lists
.github/workflows/fortress-completion-finalize.yml Refactors base64 decoding to use intermediate variable for performance

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@mrz1836 mrz1836 merged commit 95b98fc into master Feb 5, 2026
53 checks passed
@github-actions github-actions bot deleted the chore/sync-files-bitcoin-schema-20260205-153011-1299e85 branch February 5, 2026 20:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated-sync Automated sync PR, e.g. from a fork or external repo automerge Label to automatically merge pull requests that meet all required conditions chore Simple dependency updates or version bumps size/M Medium change (51–200 lines) update General updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants