Pull Requests | Issues | v0.3.6...v0.3.7

#561 Fix Homebrew tap to remove the quarantine bit from the binary on a post install hook

Pull Requests | Issues | v0.3.5...v0.3.6

#558 Update Go to v1.24.5
#558 Release SBOM
#558 Add license files of Go and Go Modules to released assets

v0.3.5...v0.3.6-0

Pull Requests | Issues | v0.3.4...v0.3.5

Pull Requests | Issues | v0.3.3...v0.3.4

🐛 Bug Fixes

#378 Fix a bug ghatm can't parse workflows if an expression is used in timeout-minutes @taiki45

Pull Requests | Issues | v0.3.2...v0.3.3

Others

#114 Update Go to 1.23.2
#102 Create GitHub Artifact Attestations

https://github.com/suzuki-shunsuke/ghatm/attestations

You can verify downloaded assets from GitHub Releases using GitHub CLI.

gh release download -R suzuki-shunsuke/ghatm v0.3.3 -p ghatm_darwin_arm64.tar.gz
gh attestation verify ghatm_darwin_arm64.tar.gz \
  -R suzuki-shunsuke/ghatm \
  --signer-workflow suzuki-shunsuke/go-release-workflow/.github/workflows/release.yaml

v0.3.2...v0.3.3-2

v0.3.2...v0.3.3-1

Pull Requests | Issues | v0.3.1...v0.3.2

Features

#68 #70 #93 Enable you to estimate appropriate timeout-minutes per job by the job execution history using GitHub API

⚠️ This feature doesn't support workflow_call

ghatm sets 30 to timeout-minutes by default, but the appropriate timeout-minutes are different by job, and it's difficult to decide the appropriate timeout-minutes.
So this release provides the feature estimating appropriate timeout-minutes of each job by the job execution history using GitHub API.

Usage:

ghatm set -auto [-repo <repository full name | $GITHUB_REPOSITORY>] [-size <The number of sample jobs | 30>]

You need to pass a GitHub access token via environment variable GITHUB_TOKEN or GHATM_GITHUB_TOKEN.
This feature uses GitHub API.

• https://docs.github.com/en/rest/actions/workflow-jobs#list-jobs-for-a-workflow-run
• https://docs.github.com/en/rest/actions/workflow-runs?apiVersion=2022-11-28#list-workflow-runs-for-a-workflow

By default, the feature collects 30 successful jobs for each job, but you can change the number using -size option.
The feature collects 30 jobs for each job and gets the longest job execute time.

timeout-minutes: The longest job execution time + 10

v0.3.1...v0.3.2-1