-
Notifications
You must be signed in to change notification settings - Fork 13
Comparing changes
Open a pull request
base repository: planetscale/ghcommit-action
base: v0.2.20
head repository: planetscale/ghcommit-action
compare: v0.2.21
- 9 commits
- 7 files changed
- 6 contributors
Commits on Mar 4, 2026
-
chore(deps): update docker/setup-qemu-action action to v4 (#130)
Co-authored-by: felix-renovate[bot] <143542247+felix-renovate[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 0f12d77 - Browse repository at this point
Copy the full SHA 0f12d77View commit details -
chore(deps): update docker/login-action action to v4 (#131)
Co-authored-by: felix-renovate[bot] <143542247+felix-renovate[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 19f6b80 - Browse repository at this point
Copy the full SHA 19f6b80View commit details
Commits on Mar 5, 2026
-
chore(deps): update docker/setup-buildx-action action to v4 (#132)
Co-authored-by: felix-renovate[bot] <143542247+felix-renovate[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 639a646 - Browse repository at this point
Copy the full SHA 639a646View commit details
Commits on May 14, 2026
-
ci: pin autotag binary by version + sha256
Replace the deprecated `git.io/autotag-install` one-liner with a direct download of `autotag_linux_amd64` from a pinned release, verified against a hardcoded SHA-256. Why: - The installer is generated by godownloader (also deprecated upstream) and, while it does check the checksum file published with each GitHub release, those checksums are mutable — anyone who can publish a release can publish matching checksums. There's no way to pin an out-of-band expected SHA. - autotag's maintainers are me and a couple of trusted ex-coworkers (incl. @will.milton) and I trust the code, but a compromise of the `autotag-dev` org or a maintainer account would silently flow into every pipeline that runs the installer. Hardcoding the SHA in our workflow makes that class of supply-chain attack fail loudly. - autotag rarely changes and we only use its most basic functionality, so we don't upgrade often. Grabbing the new binary's SHA from `checksums.txt` on bump is a cheap one-time step for meaningful hardening. See: https://github.com/autotag-dev/autotag/blob/main/README.md (CI install section) for the recommended pattern.
Configuration menu - View commit details
-
Copy full SHA for 7456b62 - Browse repository at this point
Copy the full SHA 7456b62View commit details
Commits on May 15, 2026
-
Merge pull request #133 from planetscale/joem/autotag-sha-pin
ci: pin autotag binary by version + sha256
Configuration menu - View commit details
-
Copy full SHA for eb8ef2a - Browse repository at this point
Copy the full SHA eb8ef2aView commit details
Commits on May 22, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 1a2219d - Browse repository at this point
Copy the full SHA 1a2219dView commit details
Commits on May 27, 2026
-
feat: add optional repository input
Add an optional `repository` input that points to a relative path under $GITHUB_WORKSPACE for the git repository to operate on. Defaults to `.` (the workspace root). The entrypoint adds the resolved path to safe.directory and cd's into it before running git status / ghcommit. This mirrors the behaviour of stefanzweifel/git-auto-commit-action and enables using the action on repositories checked out into a subdirectory of the workflow workspace. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 41c513d - Browse repository at this point
Copy the full SHA 41c513dView commit details
Commits on Jun 4, 2026
-
Merge pull request #138 from gabriele-ct/contrib/repository-input
feat: add optional repository input
Configuration menu - View commit details
-
Copy full SHA for 6304d85 - Browse repository at this point
Copy the full SHA 6304d85View commit details -
Configuration menu - View commit details
-
Copy full SHA for 57a6c78 - Browse repository at this point
Copy the full SHA 57a6c78View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.2.20...v0.2.21