This change adds a release for Linux 5.15 for the Proxmox Edge kernels.
In addition, this change also includes ZFS 2.1.1 which follows the
upstream Proxmox repository.
This change stops the Linux 5.10 release branch for this repository.
Proxmox has currently moved on to Linux 5.11, so this Linux 5.10 cannot really
be considered "edge" anymore.
In case you need a long-term support kernel, I recommend moving back to
the stock Proxmox kernel.
This reverts commit 01cbdebf0a.
Although almost all release builds succeed, there have been cases where
new stable releases actually cause the build to fail or other cases
where we need to test changes on the release branch.
This change adds kernel builds for the Proxmox VE 6 BETA version that is
available now. These kernels are built using Debian Bullseye instead of
Buster.
This change updates the CI build workflow to only trigger on pull
requests to the master branch. The release branches almost never cause
build errors, so we can skip that check.
This change updates the release workflow of the repository that can
automatically tag the releases after merging a pull request and build
the artifacts.
This change updates the build pipeline to build the kernel with the
default GCC version on Debian Buster. This is more safe for people
running custom kernel modules.
This change removes the custom build profiles from the CI pipeline.
Previously, this repository offered kernels that were specifically
compiled for a certain microarchitecture.
However, since the effect of such optimizations for the kernel is rather
neglible and due to the increased cost of maintaining several build profiles,
I have decided to stop offering these as pre-builts.
This change updates the build code to support in-tree builds. This is
easier to manage for CI builds and reduces the amount of IO operations
necessary for the build process.
This change renames the package again to pve-kernel. Instead, we now
differentiate the package based on the extra version (which is suffixed
with -edge).
This change removes the master kernel build workflow since it is being
replaced by update workflow which automatically updates the repository
based on the specified tag.
