Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

[repo-assist] CI: bump actions/checkout and actions/setup-node to v5

Fermée Adaptée aux débutants
  • Quelque chose ne va pas ?
#353 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
1/5
Temps estimé
Moins d'une heure
Accessibilité débutants
70/100
Type d'issue
Refactorisation
Clarté
Clairement spécifiée
Activité
Active
Stack technique
github-actions
Domaine
ci-cd

Piste de recherche

Les modifications se trouvent dans .github/workflows/pull-request.yml et .github/workflows/publish.yml. Mets à jour actions/checkout de la v4 à la v5 dans les deux fichiers, et actions/setup-node de la v4 à la v5 dans le workflow de pull request. Vérifie les modifications en contrôlant la syntaxe du workflow et en t'assurant que l'intégration continue s'exécute avec succès après la mise à jour.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

agentic-workflows automation repo-assist

[!CAUTION]
Protected files were modified in this change.
This pull request is in request_review mode and requires explicit human scrutiny before merge.

Protected files: .github/workflows/publish.yml, .github/workflows/pull-request.yml

[!CAUTION]
Protected files were modified in this change (.github/workflows/pull-request.yml, .github/workflows/publish.yml). Please review carefully before merging.

Summary

Updates GitHub Actions used in this repo's CI workflows to their current major releases:

Action Before After
actions/checkout v4 v5
actions/setup-node v4 v5

Applied to both .github/workflows/pull-request.yml and .github/workflows/publish.yml (setup-node is only used in pull-request.yml). actions/setup-dotnet is left unchanged at v4.3.1, which is still current.

No functional changes to build/test steps — only pinned action versions change.

This addresses #349, which tracked three previous automated attempts (2026-08-25, 2026-09-01, 2026-09-15) at the same upgrade that failed to push due to workflows-permission restrictions on the automated agent at the time. This PR is opened via the create_pull_request safe-output tool, which handles the branch push through the workflow's configured permissions.

Test Status

  • dotnet build FSharp.Control.AsyncSeq.sln -c Release — succeeded, 0 errors (5 pre-existing unrelated warnings about groupBy/groupByAsync consumption, present before this change).
  • dotnet test tests/FSharp.Control.AsyncSeq.Tests -c Release — 497/497 tests passed (no test changes; this is a workflow-file-only change).
  • Workflow YAML changes only affect action pinning; CI will validate the updated actions run correctly once this PR's own checks execute.

🤖 This PR was created by Repo Assist, an automated AI assistant, taking forward a previously-stalled engineering task (issue #349). A human maintainer should review before merging, given the protected-file changes.

[!NOTE]
This was originally intended as a pull request, but the git push operation failed.

Original error: The process '/usr/bin/git' failed with exit code 1

Workflow Run: View run details and download bundle artifact

The bundle file is available in the agent artifact in the workflow run linked above.

Create the pull request manually 
# Download the artifact from the workflow run
gh run download '35762384844' -n agent -D '/tmp/agent-35762384844'

# Resolve the bundle source ref, fetch it into a temporary ref, then create the local branch
bundle_path='/tmp/agent-35762384844/aw-repo-assist-eng-update-ci-actions-20260922.bundle'
temp_ref='refs/bundles/create-pr-repo-assist-eng-update-ci-actions-20260922-ae27d1892093cee8-903bbace'
target_ref='refs/heads/repo-assist/eng-update-ci-actions-20260922-ae27d1892093cee8'
bundle_source_ref=$(git bundle list-heads "$bundle_path" | awk '$2 ~ /^refs\/heads\// { print $2 }')
if [ -z "$bundle_source_ref" ]; then
  bundle_source_ref=$(git bundle list-heads "$bundle_path" | awk '$2 == "HEAD" { print $2 }')
fi
if [ "$(printf '%s\n' "$bundle_source_ref" | sed '/^$/d' | wc -l | tr -d ' ')" != "1" ]; then
  echo "Expected exactly one bundle source ref, found: $bundle_source_ref" >&2
  exit 1
fi
git fetch "$bundle_path" "${bundle_source_ref}:${temp_ref}"
git update-ref "$target_ref" "$temp_ref"
git checkout 'repo-assist/eng-update-ci-actions-20260922-ae27d1892093cee8'
# Ensure the working tree matches the updated branch
git reset --hard
# Remove the temporary bundle ref
git update-ref -d "$temp_ref"

# Push the branch to the target remote
git push 'origin' 'repo-assist/eng-update-ci-actions-20260922-ae27d1892093cee8'

# Create the pull request
gh pr create --title '[repo-assist] CI: bump actions/checkout and actions/setup-node to v5' --base 'main' --head 'repo-assist/eng-update-ci-actions-20260922-ae27d1892093cee8' --repo 'fsprojects/FSharp.Control.AsyncSeq'

Generated by 🌈 Repo Assist, see workflow run. Learn more.
Comment /repo-assist to run again

Add this agentic workflow to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@4bc8419fad05e6b032741cbfd189986700bcf71c
Langage dominant
F#
Étoiles
175
Forks
54
Merge moyen
6 j 13 h
PR mergées (30 j)
3

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de fsprojects/FSharp.Control.AsyncSeq

Toutes les issues de fsprojects/FSharp.Control.AsyncSeq

Issues similaires

Plus d'issues DevOps

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.