Pulled Docker image is stuck at stale_repos:v1

[bcbrookman]

Describe the bug

Despite setting a specific version (@v2, @v3.0.0, etc.), the Docker image that's pulled is always stale_repos:v1 which isn't updated.

I believe this is happening because the action.yml metadata file still references the v1 image, even in later releases.

stale-repos/action.yml

Lines 8 to 10 in 1d81794

	runs:
	using: "docker"
	image: "docker://ghcr.io/github/stale_repos:v1"

To Reproduce

For example, when using github/stale-repos@v2 as shown in the README examples.

steps:
      - name: Run stale_repos tool
        uses: github/stale-repos@v2
        env:
<...>

The image pulled in the Actions log is ghcr.io/github/stale_repos:v1

Pull down action image 'ghcr.io/github/stale_repos:v1'
  /usr/bin/docker pull ghcr.io/github/stale_repos:v1
<...>

Using a docker path instead of the action name is a potential workaround.

steps:
      - name: Run stale_repos tool
        uses: docker://ghcr.io/github/stale_repos:v2
        env:
<...>

Expected behavior

I would expect the action version and the pulled docker image to correspond. In other words, I expect @v2 to pull a Docker image containing the code released at v2.x.x

Screenshots

No response

Additional context

No response

[jmeridth]

Thanks for reporting this. We have a fix we have used in another repo. I will apply it first thing in the morning. I'll also look at and release your Dockerfile PR #324.

[jmeridth]

Fixed this manually for now. Apologies @bcbrookman I added you as co-author but had to do some commit finagling. I'm going to add automation for this to the workflows. Thank you again for raising this flag.

[bcbrookman]

No problem! Thank you!