super-linter: Latest release (4.6.3 or maybe 4.7.0?) not available on Docker.

Describe the bug

Dependabot tried to upgrade me to 4.6.3 but weirdly tried to use 4.7.0, but it wasn’t available:

image

11s
Pull down action image 'ghcr.io/github/super-linter:v4.7.0'
  /usr/bin/docker pull ghcr.io/github/super-linter:v4.7.0
  Error response from daemon: manifest unknown
  Warning: Docker pull failed with exit code 1, back off 4.638 seconds before retry.
  /usr/bin/docker pull ghcr.io/github/super-linter:v4.7.0
  Error response from daemon: manifest unknown
  Warning: Docker pull failed with exit code 1, back off 4.765 seconds before retry.
  /usr/bin/docker pull ghcr.io/github/super-linter:v4.7.0
  Error response from daemon: manifest unknown
Error: Docker pull failed with exit code 1

Can’t see 4.63. in the Releases page.

Then I set it to 4.7.0 but that also didn’t work

45s
Current runner version: '2.280.3'
Operating System
Virtual Environment
Virtual Environment Provisioner
GITHUB_TOKEN Permissions
Prepare workflow directory
Prepare all required actions
Getting action download info
Failed to resolve action download info. Error: Unable to resolve action `github/super-linter@v4.7.0`, unable to find version `v4.7.0`
Retrying in 15.534 seconds
Failed to resolve action download info. Error: Unable to resolve action `github/super-linter@v4.7.0`, unable to find version `v4.7.0`
Retrying in 28.264 seconds
Error: Unable to resolve action `github/super-linter@v4.7.0`, unable to find version `v4.7.0`

Expected behavior

Using an explicitly version number in a GitHub action should work but neither of these work:

        uses: github/super-linter@v4.6.3

Or

        uses: github/super-linter@v4.7.0

Possibly related to #1839 ?

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 15 (5 by maintainers)

Most upvoted comments

@tunetheweb @dbergman24 Trying to resolve it now… Seems an internet outage during the build really beefed it… I wish automation would work somedays 😃