Skip to content

[Sync] Update project files from source repository (c5b3708)#93

Merged
mrz1836 merged 2 commits intomasterfrom
chore/sync-files-mrz-tools-20260110-094050-c5b3708
Jan 10, 2026
Merged

[Sync] Update project files from source repository (c5b3708)#93
mrz1836 merged 2 commits intomasterfrom
chore/sync-files-mrz-tools-20260110-094050-c5b3708

Conversation

@mrz1836
Copy link
Owner

@mrz1836 mrz1836 commented Jan 10, 2026

What Changed

  • Updated MAGE_X_VERSION from v1.15.0 to v1.15.5 in .github/.env.base
  • Updated MAGE_X_GOLANGCI_LINT_VERSION from v2.7.2 to v2.8.0 in .github/.env.base
  • Updated GO_PRE_COMMIT_GOLANGCI_LINT_VERSION from v2.7.2 to v2.8.0 in .github/.env.base
  • Added go-version input parameter to .github/actions/setup-benchstat/action.yml with description "Go version being used (e.g., 1.24.x, 1.22). Benchstat requires Go 1.23+"
  • Modified cache-hit output description in .github/actions/setup-benchstat/action.yml to note "Empty if skipped due to Go version"

Why It Was Necessary

  • Upgrade to latest MAGE-X tooling version (v1.15.5) to incorporate bug fixes and improvements
  • Update golangci-lint to v2.8.0 across both MAGE-X and pre-commit configurations for consistency and access to latest linting rules
  • Add Go version awareness to benchstat setup action to handle version-specific requirements (benchstat requires Go 1.23+)

Testing Performed

  • Verify MAGE-X v1.15.5 is compatible with existing workflows and CI configurations
  • Confirm golangci-lint v2.8.0 runs successfully against the codebase
  • Test benchstat action behavior with different Go versions to ensure proper version gating

Impact / Risk

  • Low Risk: Version bumps are incremental updates to development and CI tooling
  • No Breaking Changes: Configuration updates are backwards compatible with existing workflows
  • Developer Experience: Teams using Go versions below 1.23 will have benchstat installation skipped automatically based on the new go-version input parameter

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

github-actions bot commented Jan 10, 2026

Code Coverage Analysis

🟡 Overall Coverage: 82.3%
No Go files modified in this PR

Project coverage remains at 82.3% (3.0K/3.6K statements)

Changes: 6 config files

Coverage Metrics

Metric Value Grade Trend
Percentage 82.3% ⭐ B 📊
Statements 3.0K/3.6K ⭐ B No change
Quality Score 82.3/100 ⭐ B 📈

Coverage Breakdown

████████████░░░ 82.3%

Resources

Generated via go-coverage • 2026-01-10 14:45:51 UTC

github-actions bot added a commit that referenced this pull request Jan 10, 2026
@github-actions
Deploy PR #93 coverage (commit a49de4a)
2ce2343 
🏷️ Generated with GoFortress
@mrz1836
refactor(lint): optimize retryArgs initialization for clarity
6f3a6de 
Updated retryArgs to use a fixed capacity slice for known arguments, improving readability and performance.
github-actions bot added a commit that referenced this pull request Jan 10, 2026
@github-actions
Deploy PR #93 coverage (commit 017c69f)
d485d56 
🏷️ Generated with GoFortress
@mrz1836 mrz1836 merged commit c90e7bf into master Jan 10, 2026
43 checks passed
@github-actions github-actions bot deleted the chore/sync-files-mrz-tools-20260110-094050-c5b3708 branch January 10, 2026 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@mrz1836 mrz1836

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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@mrz1836