ci: bump deprecated actions; replace archived release action#234
Merged
Conversation
cameroncuster
added a commit
that referenced
this pull request
Jul 9, 2026
actions/checkout@v4 defaults to a shallow clone (fetch-depth: 1), which broke oj-verify's timestamp-based change detection (regressed in #234, when checkout went v1 -> v4). Pin fetch-depth: 0 so only changed tests re-run.
cameroncuster
added a commit
that referenced
this pull request
Jul 9, 2026
actions/checkout@v4 defaults to a shallow clone (fetch-depth: 1), which broke oj-verify's timestamp-based change detection (regressed in #234, when checkout went v1 -> v4). Pin fetch-depth: 0 so only changed tests re-run.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces deprecated/unmaintained GitHub Actions:
actions/checkout@v1→@v4andactions/setup-python@v1→@v5inlibrary_checker_aizu(v1 targets Node versions that runners are deprecating; the rest of the workflow already uses v4)marvinpinto/action-automatic-releases@latest→softprops/action-gh-release@v2inpublish_pdf(marvinpinto's action is archived and unmaintained; pinned@latestis also a supply-chain risk)Details on the release step:
softprops/action-gh-release@v2uses the defaultGITHUB_TOKEN; the workflow already grantspermissions: contents: writetag_name: ptc/name: ptcreproduces the existing rolling-release behavior (updates the sameptcrelease/tag in place)download-artifactpath changed fromtests/ptc.pdftotests/: with download-artifact@v4,pathis the destination directory, so the old value producedtests/ptc.pdf/ptc.pdf; nowtests/ptc.pdfis the file itselfRelease behavior should be verified on the first dev push after merge (release
ptcgets a freshptc.pdfasset).