No releases since 4.0.2 have docker images

[jbergler]

The latest image uploaded to the documented registry is 4.0.2 (far behind the 4.0.18 latest release as of writing this) https://explore.ggcr.dev/?repo=k8s.gcr.io/sig-storage/nfs-subdir-external-provisioner

I did some trawling through git history and found this PR which changed the release workflow to only trigger on tags prefixed with gh- which doesn't match the tags being created when new releases are cut.

I suspect the correct fix here is to update the workflow to trigger on tags without the prefix and then either manually trigger the release for 4.0.18 or to release a new version (since there are unreleased changes anyway)

[jbergler]

@moikot & @kmova fyi as you were both involved in #21

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[Orhideous]

/remove-lifecycle rotten

[Orhideous]

It's still an issue. There are some unmerged PRs and release process just stuck in the limbo.

[Starttoaster]

The releases you're referring to appear to be releases for the helm chart. The actual program doesn't appear to have "releases", instead the maintainer(s) here appear to just make tags (without creating a release for them.) And the last tag for the program is 4.0.2. And if you look at the helm chart, the last version of the helm chart is 4.0.18.

So I'm not really sure if there is an issue at all here. We're just waiting for 4.0.3, I guess is the real issue :)

[jbergler]

Thanks @Starttoaster - you are definitely right. Looks like 4.0.3 release is being discussed in #330 so I'll mark this as closed.