10up/actions-wordpress

Update dependencies with deprecated node version

Open

#46 opened on Oct 27, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Shell (463 stars) (41 forks)user submission
help wanted

Description

In checking the readme updater action on AS4T, I noticed that it was throwing some warnings about the actions/checkout needing to be updated (it could go from v2 to v4), but instead of just updating that one repo I figured I'd open an issue here for someone to go across our projects and updating all related actions (probably worth checking what other actions are using deprecated node dependencies that could be updated).

Contributor guide

Tech stack
github actionsshell
Domain
devopsci cd
Issue type
chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
GitHub Actions basicsYAML editingNode.js version deprecation awareness
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Identify all GitHub Actions workflows in the repository and check for actions using deprecated Node.js versions (e.g., actions/checkout v2 to v4). Update version numbers accordingly. Refer to the linked GitHub Actions workflow run for an example. Also check the GitHub Actions marketplace for current versions and deprecation notices.