[Repo Assist] ci: update GitHub Actions to latest versions (checkout@v4, setup-dotnet@v4)

Open Beginner friendly
#1,507 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd

Research direction

Review .github/workflows/build.yml, .github/workflows/build-and-pack-nightly.yml, and .github/workflows/release.yml for the action versions and deprecated output command listed in the issue. Update the specified workflow references, then inspect the resulting YAML and workflow diff; done means all listed outdated actions and the deprecated command are replaced without changing other workflow behavior.

Written by the indexing model from the issue text.

Description

agentic-workflows automation repo-assist

🤖 This is an automated pull request from Repo Assist.

Problem

Several GitHub Actions workflow files were using outdated action versions and a deprecated workflow command:

File Issue
build.yml (build job) actions/checkout@v3
build.yml (analyze job) actions/checkout@v3
build-and-pack-nightly.yml actions/checkout@v3, actions/setup-dotnet@v2
build-and-pack-nightly.yml ::set-output deprecated command
release.yml actions/checkout@v3

actions/checkout@v4 has been available since September 2023, and actions/setup-dotnet@v4 since early 2024. The ::set-output workflow command was deprecated in GitHub Actions in October 2022 and replaced by writing to $GITHUB_OUTPUT.

Changes

  • actions/checkout@v3@v4 in all three workflow files
  • actions/setup-dotnet@v2@v4 in build-and-pack-nightly.yml
  • echo "::set-output name=date::..."echo "date=..." >> $GITHUB_OUTPUT in build-and-pack-nightly.yml

Benefits

  • Resolves Node.js 16 deprecation warnings from checkout@v3 (GitHub Actions now requires Node.js 20+)
  • Eliminates deprecated ::set-output warnings that appear in nightly build logs
  • Stays current with upstream security patches in these actions

Test Status

Workflow-only change — no source code or tests modified. No local build/test run needed.
These changes are safe; checkout@v4 and setup-dotnet@v4 are drop-in replacements with the same interface.

Generated by Repo Assist ·

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@346204513ecfa08b81566450d7d599556807389f

[!WARNING]
🛡️ Protected Files — Push Permission Denied

This was originally intended as a pull request, but the patch modifies protected files: .github/workflows/build-and-pack-nightly.yml, .github/workflows/build.yml, .github/workflows/release.yml.

The push was rejected because GitHub Actions does not have workflows permission to push these changes, and is never allowed to make such changes, or other authorization being used does not have this permission. A human must create the pull request manually.

To create a pull request with the changes:

# Download the patch from the workflow run
gh run download 23198566450 -n agent-artifacts -D /tmp/agent-artifacts-23198566450

# Create a new branch
git checkout -b repo-assist/eng-update-github-actions-2026-03-17-90a5c06e08ef963f main

# Apply the patch (--3way handles cross-repo patches)
git am --3way /tmp/agent-artifacts-23198566450/aw-repo-assist-eng-update-github-actions-2026-03-17.patch

# Push the branch and create the pull request
git push origin repo-assist/eng-update-github-actions-2026-03-17-90a5c06e08ef963f
gh pr create --title '[Repo Assist] ci: update GitHub Actions to latest versions (checkout@v4, setup-dotnet@v4)' --base main --head repo-assist/eng-update-github-actions-2026-03-17-90a5c06e08ef963f --repo ionide/FsAutoComplete
Dominant language
F#
Stars
488
Forks
169
Avg merge
2d 8h
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ionide/FsAutoComplete

All issues in ionide/FsAutoComplete

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.