release new version v0.2.3 of unused-volumes

[krew-release-bot]

hey krew-index team,

I am krew-release-bot, and I would like to open this PR to publish version v0.2.3 of unused-volumes on behalf of @Dirrk.

Thanks,
@krew-release-bot

[ahmetb]

🤖 Beep beep! I’m a robot speaking on behalf of @ahmetb. 🤖

---

This pull request does not seem to be a straightforward version bump. I'll have a human review this. If we don't respond within a day, feel free to ping us.

Why wasn't this detected as a plugin version bump:

file plugins/unused-volumes.yaml is not a straightforward version bump: changing old version ("0.1.2") with new version ("0.2.3") in the url (https://github.com/dirathea/kubectl-unused-volumes/releases/download/v0.1.2/kubectl-unused-volumes_linux_amd64.tar.gz) does not appear in the patch as https://github.com/dirathea/kubectl-unused-volumes/releases/download/v0.2.3/kubectl-unused-volumes_linux_amd64.tar.gz
/kind plugin-update

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: krew-release-bot
Once this PR has been reviewed and has the lgtm label, please assign chriskim06 for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ahmetb]

This seems to be an ownership change. I don't see a sign at https://github.com/dirathea/kubectl-unused-volumes/ indicating the plugin is archived, or this is the new blessed version. Typically the users don't expect the source of the plugin to change. Can you please explain if we have the current plugin maintainer's approval etc? @Dirrk

[k8s-triage-robot]

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

[Dirrk]

@ahmetb Please close this, it was opened by mistake.

[ahmetb]

/close

[k8s-ci-robot]

@ahmetb: Closed this PR.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.