Repository navigation
Upgrade dependencies on workflow ci - #4471
Merged
Merged
Conversation
A fork that enables Actions runs it every day, and on its pull requests, to fail in pre_activation. As in 8571e08, the 168 of GH_AW_ACTION_FAILURE_ISSUE_EXPIRES_HOURS is kept: gh-aw v0.93.5 writes 0 even from the unchanged source.
gh aw compile --dir .github/workflows skips the maintenance-workflow step, which rewrites GH_AW_ACTION_FAILURE_ISSUE_EXPIRES_HOURS from 168 to 0 when no aw.json opts into issue expiration.
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
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.
Every job of the CI reported two annotations:
Node.js 20 is deprecated, foractions/checkout@v4,setup-dotnet@v4,cache@v4andupload-artifact@v4, which GitHub now forces onto Node 24, and the notice thatubuntu-latestmigrates to Ubuntu 26 between October 19 and November 19, 2026. This branch removes both, and stops Repo Assist and Release from running in the forks.Actions and runners
checkout@v7,setup-dotnet@v6,cache@v6andupload-artifact@v7inci.yml,docs.ymlandrelease.yml, the versionsrepo-assist.lock.ymlalready uses. Their release notes change none of the inputs these workflows use.ubuntu-26.04instead ofubuntu-latest, so this PR builds and runs the integration tests on 26.04 before the migration does it unnoticed. The Windows jobs keepwindows-latest.Forks
Once a fork enables Actions, it runs every workflow of the repository. Recent forks show about 80 Repo Assist runs each, from its daily schedule and their own pull requests, all failing in
pre_activation, and Release runs that build on Windows before failing to publish.if: github.repository == 'fsprojects/Paket'in the frontmatter ofrepo-assist.md, which gh-aw adds to the conditions ofpre_activationandactivation.detect-release, whichreleaseanddocsdepend on.In a fork, these runs are now skipped instead of failing. The CI keeps running there.
Regenerating the Repo Assist lock
gh aw compilewithout--diralso runs the maintenance-workflow step of gh-aw. As the repository has noaw.jsonopting into issue expiration, that step rewritesGH_AW_ACTION_FAILURE_ISSUE_EXPIRES_HOURSfrom168to0(gh-aw ADR-51425). Withgh aw compile --dir .github/workflows, the lock keeps the168, and the diff only has the added condition.CLAUDE.mdand the frontmatter ofrepo-assist.mdnow give that command.Not tested by this PR
git pushofdocs.ymltogh-pages: from v6,checkoutkeeps the credentials in a file of$RUNNER_TEMPinstead of.git/config. It only runs after a stable release, or by hand.