mirror of
https://github.com/kubescape/kubescape.git
synced 2026-02-14 18:09:55 +00:00
Updated Publishing (markdown)
@@ -1,2 +1,32 @@
|
||||
## Homebrew-tap
|
||||
Homebrew-tap has a [workflow](https://github.com/kubescape/homebrew-tap/blob/main/.github/workflows/release.yml) that can auto bump the kubescape version in its own repository. That workflow will get triggered automatically by the [kubescape post release workflow](https://github.com/kubescape/kubescape/blob/master/.github/workflows/03-post-release.yaml) once a new release of kubescape is made.
|
||||
## Release Asserts and Docker client images
|
||||
Release Asserts and Docker client images are generated by the [02-create_release](https://github.com/kubescape/kubescape/blob/master/.github/workflows/02-release.yaml) workflow when a new tag such as `v1.2.3-rc.4` gets pushed into the kubescape repository. It includes:
|
||||
- `kubescape-ubuntu-latest`: Linux amd64 executable built on GitHub Actions Runner ubuntu-20.04
|
||||
- `kubescape-ubuntu-latest.sha256`: SHA256 of the Linux amd64 executable
|
||||
- `kubescape-ubuntu-latest.tar.gz`: Tarball containing the LICENSE and kubescape Linux amd64 executable
|
||||
- `kubescape-arm64-ubuntu-latest`: Linux ARM64 executable built with Docker Golang Bullseye image and QEMU on GitHub Actions Runner
|
||||
- `kubescape-arm64-ubuntu-latest.sha256`: SHA256 of the Linux ARM64 executable
|
||||
- `kubescape-arm64-ubuntu-latest.tar.gz`: Tarball containing the LICENSE and kubescape Linux ARM64 executable
|
||||
- `kubescape-macos-latest`: Intel macOS executable built on GitHub Actions Runner macos-latest
|
||||
- `kubescape-macos-latest.sha256`: SHA256 of the Intel macOS executable
|
||||
- `kubescape-macos-latest.tar.gz`: Tarball containing the LICENSE and kubescape Intel macOS executable
|
||||
- `kubescape-arm64-macos-latest`: Silicon (M1/M2) macOS executable built on GitHub Actions Runner macos-latest with Golang cross compile and libgit2 ARM64 build option `-DCMAKE_OSX_ARCHITECTURES="arm64"`.
|
||||
- `kubescape-arm64-macos-latest.sha256`: SHA256 of the Silicon (M1/M2) macOS executable
|
||||
- `kubescape-arm64-macos-latest.tar.gz`: Tarball containing the LICENSE and kubescape Silicon (M1/M2) macOS executable
|
||||
- `kubescape.exe`: Windows x86_64 executable built on GitHub Actions Runner windows-latest
|
||||
- `kubescape-windows-latest`: Deprecated, same as `kubescape.exe`
|
||||
- `kubescape-windows-latest.sha256`: SHA256 of the Windows x86_64 executable
|
||||
- `kubescape-windows-latest.tar.gz`: Tarball containing the LICENSE and kubescape.exe Windows x86_64 executable
|
||||
|
||||
[Docker client images](https://quay.io/repository/kubescape/kubescape?tab=tags) are tagged with current version and `latest` when publishing.
|
||||
|
||||
## [Homebrew-tap](https://github.com/kubescape/homebrew-tap/blob/main/.github/workflows/release.yml)
|
||||
Homebrew-tap has a [workflow](https://github.com/kubescape/homebrew-tap/blob/main/.github/workflows/release.yml) that can auto bump the kubescape version in its own repository. That workflow will get triggered automatically by the [kubescape post release workflow](https://github.com/kubescape/kubescape/blob/master/.github/workflows/03-post-release.yaml) once a new release of kubescape is made.
|
||||
|
||||
## [Other packaging](https://github.com/HollowMan6/packaging)
|
||||
Packaging repository includes the following formats:
|
||||
- [Debian](https://github.com/HollowMan6/packaging/tree/main/deb/debian)
|
||||
- [RPM](https://github.com/HollowMan6/packaging/blob/main/kubescape.spec)
|
||||
- [AUR](https://github.com/HollowMan6/packaging/blob/main/PKGBUILD)
|
||||
- [snap](https://github.com/HollowMan6/packaging/tree/main/snap)
|
||||
|
||||
Packaging has a [workflow](https://github.com/HollowMan6/packaging/blob/main/.github/workflows/release.yml) that can auto bump the kubescape version in its own repository packaging scripts. That workflow will get triggered automatically by the [kubescape post release workflow](https://github.com/kubescape/kubescape/blob/master/.github/workflows/03-post-release.yaml) once a new release of kubescape is made.
|
||||
Reference in New Issue
Block a user