CircleCI nightly job is broken

[MikeMcC399]

Issue

The CircleCI job which is linked to by https://github.com/yarnpkg/yarn/blob/master/README.md runs nightly and fails nightly.

See https://app.circleci.com/pipelines/github/yarnpkg/yarn

The badge also fails to show the status:

<a href="https://circleci.com/gh/yarnpkg/yarn"><img alt="Circle Status" src="https://circleci.com/gh/yarnpkg/yarn.svg?style=shield&circle-token=5f0a78473b0f440afb218bf2b82323cc6b3cb43f"></a>

Tests are failing using Docker images for Ubuntu versions which entered end-of-life several years ago. See https://endoflife.date/ubuntu for a convenient reference table:

Image	End-of-life
ubuntu:16.04	Apr 2021
ubuntu:14.04	Apr 2019
ubuntu:12.04	Apr 2017

Suggestion

Either disable the job and remove the badge OR update the job so it runs successfully and update the badge link, for example:

using Markdown syntax:

[![Circle Status](https://circleci.com/gh/yarnpkg/yarn/tree/master.svg?style=svg)](https://circleci.com/gh/yarnpkg/yarn/tree/master)

[Daniel15]

Yarn v1 is not under active development so I'm not sure it even needs CI any more.

[MikeMcC399]

@Daniel15

Yarn v1 is not under active development so I'm not sure it even needs CI any more.

Do you have admin access to CircleCI to disable the nightly job or even the complete outdated workflow .circleci/config.yml?

[MikeMcC399]

@Daniel15

Yarn v1 is not under active development so I'm not sure it even needs CI any more.

If Yarn v1 Classic is an approved step to installing Yarn Modern, without relying on corepack, which the documentation describes as being experimental and not suitable for production, why isn't Yarn v1 Classic being tested on current Node.js versions in a CI workflow?

[MikeMcC399]

The CircleCI job https://app.circleci.com/pipelines/github/yarnpkg/yarn continues to run nightly and fails nightly.