WordPress/gutenberg

Workflows: Replace unmaintained actions

Closed

#29,946 opened on Mar 17, 2021

View on GitHubContributor guide
 (0 comments) (1 reaction) (0 assignees)JavaScript (3,893 forks)batch import
Good First Issue[Status] In Progress[Type] Build Tooling[Type] Task

Repository metrics

Stars
 (9,607 stars)
PR merge metrics
 (Avg merge 12d 18h) (509 merged PRs in 30d)

Description

As mentioned here by @swissspidy:

GitHub recently deprecated a number of their actions, among them

We should:

  1. audit which other actions that we use are no longer maintained and
  2. replace them with something else.

In a number of cases, we might be able to simply use the actions/script action instead, which allows us to write actions in JS, and gives us access to GitHub's JS API ("octokit") -- which readily provides functionality such as release creation, or attaching an asset to a release.

Contributor guide

Research direction
Audit all workflow files in .github/workflows/ for deprecated actions like actions/create release and actions/upload release asset. Replace them with actions/github script or other maintained alternatives. See PR #28138 for initial discussion and context. Review GitHub's deprecation notices to identify all affected actions.
Tech stack
javascriptgithub actions
Domain
ci cddevopsbuild system
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitHub Actions basicsYAML syntaxfamiliarity with Gutenberg CI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50