https://github.com/kubewarden/github-actions

GitHub actions used by the Kubewarden project
https://github.com/kubewarden/github-actions

hacktoberfest kubernetes kubernetes-security policy-as-code webassembly

Last synced: 5 months ago
JSON representation

GitHub actions used by the Kubewarden project

• Host: GitHub
• URL: https://github.com/kubewarden/github-actions
• Owner: kubewarden
• License: apache-2.0
• Created: 2022-01-20T13:31:23.000Z (almost 4 years ago)
• Default Branch: main
• Last Pushed: 2024-09-17T06:09:36.000Z (over 1 year ago)
• Last Synced: 2024-09-17T08:43:07.355Z (over 1 year ago)
• Topics: hacktoberfest, kubernetes, kubernetes-security, policy-as-code, webassembly
• Homepage: https://kubewarden.io
• Size: 358 KB
• Stars: 4
• Watchers: 6
• Forks: 7
• Open Issues: 3
• Metadata Files:
  • Readme: README.md
  • License: LICENSE
  • Codeowners: CODEOWNERS

Awesome Lists containing this project

README

          
# Kubewarden GitHub Actions

[![Kubewarden Infra Repository](https://github.com/kubewarden/community/blob/main/badges/kubewarden-infra.svg)](https://github.com/kubewarden/community/blob/main/REPOSITORIES.md#infra-scope)

[![Stable](https://img.shields.io/badge/status-stable-brightgreen?style=for-the-badge)](https://github.com/kubewarden/community/blob/main/REPOSITORIES.md#stable)

This is a collection of GitHub Actions to help with Kubewarden and Kubewarden

policies. It contains:

- GitHub Actions in the root of the repo. Normally not consumed by end users.

- Reusable workflows for policy testing and release, that make use of the

  mentioned GitHub Actions.

### Versioning

`v2` and upwards are under semver tags, following ["using tags for release

management"](https://docs.github.com/en/actions/creating-actions/about-custom-actions#using-tags-for-release-management).

`v1` is under the v1 branch, following ["using branches for release

management"](https://docs.github.com/en/actions/creating-actions/about-custom-actions#using-branches-for-release-management).

### Releasing a new tag

1. We ourselves are consumers of our own GHA in this repo, as we

   consume the actions in the reusable workflows. To release, decide on the

   future tag version you will create, and then, preemptively update all the

   tags of our own github-actions in this repo to that one, and commit those changes.

   

   We can't use RenovateBot or the like, as it would update the tags *after* we

   have already tagged, so the tagged version would not consume itself, but a

   previous version.

1. Tag your release with a semver tag (e.g: `v2.3.0`).

1. Proof-check the GH release notes created by release drafter. Add hints on how

   to update to new version if needed.