Hi! I'm a Kubewarden maintainer and I would like to share with you that in recent version of our tooling and Github actions we simplify the process of releasing policies by generating the artifacthub-pkg.yml file automatically based on the metadata.yml file. We would love help you migrating your policy to the new tools. You can see example of how to do it here:

https://github.com/kubewarden/user-group-psp-policy
https://github.com/kubewarden/pod-privileged-policy
https://github.com/kubewarden/safe-labels-policy

Notice that the new Gihub action publishes the Artifacthub files into another branch. This is required because the update in the file must occurs after the policy artifact is built, published and signed. Otherwise, Artifacthub scan job can detect the change before the signing of the policy OCI artifact. Then, showing the policy as not signed in the Artifact hub web page.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update Rust crate k8s-openapi to 0.17.0

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• Update Rust crate kubewarden-policy-sdk to 0.9.2

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

As an spin off of the issue #10, this issue aims to keep track of the changes required to publish the policy on artifacthub.io. To make that possible we need to do the following:

• @nlamirault needs to create an account in artifacthub.io
• We need to publish the policy artifact in a public registry. ghrc.io should be enough
• Create a Kubewarden repository in the artifacthub.io for this policy.

More info about Kubewarden policies in artifacthub.io can be found in the docs