Skip to content

[Sync] Update project files from source repository (eec0e19)#89

Merged
mrz1836 merged 1 commit into
masterfrom
chore/sync-files-bsv-blockchain-sdks-20260406-201815-eec0e19
Apr 7, 2026
Merged

[Sync] Update project files from source repository (eec0e19)#89
mrz1836 merged 1 commit into
masterfrom
chore/sync-files-bsv-blockchain-sdks-20260406-201815-eec0e19

Conversation

@mrz1836
Copy link
Copy Markdown
Collaborator

@mrz1836 mrz1836 commented Apr 7, 2026

What Changed

  • Updated .dockerignore to exclude dist/ but explicitly include !dist/linux/ subdirectory
  • Upgraded actions/setup-go from v6.3.0 (commit 4b73464) to v6.4.0 (commit 4a36011) in .github/actions/setup-go-with-cache/action.yml
  • Added clarifying comments indicating that actions/cache handles both restore and save operations for Go module cache and Go build cache
  • Updated GITLEAKS_VERSION from 8.30.0 to 8.30.1 in .github/env/10-security.env
  • Added permissions: contents: read to the pre-commit job in .github/workflows/fortress-pre-commit.yml

Why It Was Necessary

  • The Docker build process needs access to Linux-specific binaries in dist/linux/ while excluding other distribution artifacts
  • Upgrading security and build tooling ensures latest bug fixes and security patches are applied
  • Explicit permission declarations in GitHub workflows follow security best practices by adhering to the principle of least privilege
  • Comments improve maintainability by clarifying caching behavior for future contributors

Testing Performed

  • Verify Docker builds correctly include dist/linux/ contents while excluding other dist/ subdirectories
  • Confirm GitHub Actions workflows execute successfully with the updated setup-go action version
  • Validate pre-commit workflow runs with the explicit contents: read permission
  • Ensure gitleaks security scanning completes with version 8.30.1

Impact / Risk

  • Low Risk: Changes are primarily dependency version bumps and clarifying comments
  • Docker Build: Potential impact if dist/linux/ contents are required for container images; previously these may have been excluded
  • CI/CD: Adding explicit permissions is a security hardening measure with no functional impact on existing workflows

@mrz1836 mrz1836 self-assigned this Apr 7, 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 Apr 7, 2026
@github-actions github-actions Bot added update General updates size/M Medium change (51–200 lines) labels Apr 7, 2026
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Apr 7, 2026

@mrz1836
Copy link
Copy Markdown
Collaborator Author

mrz1836 commented Apr 7, 2026

LGTM!

@mrz1836 mrz1836 merged commit 06f2e31 into master Apr 7, 2026
44 checks passed
@github-actions github-actions Bot deleted the chore/sync-files-bsv-blockchain-sdks-20260406-201815-eec0e19 branch April 7, 2026 00:25
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.

1 participant