kernel-ci
kernel-ci copied to clipboard
sammcj
Continuous integration for the Linux Kernel - Built within Docker
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more. ## Config Migration Needed - [ ] Select this checkbox to let Renovate create...
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "renovate[bot] avatar"){kind=avatar}
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [fuxingloh/multi-labeler](https://redirect.github.com/fuxingloh/multi-labeler) | action | major | `v1` -> `v4` | --- ### Release...
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | debian | final | major | `wheezy` -> `bookworm` | --- ### Configuration...
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [actions/checkout](https://redirect.github.com/actions/checkout) | action | major | `v3` -> `v4` | --- ### Release...
At present kernel.org labels major releases (i.e. 4.9) as mainline releases, although considered production / stable, the build does not grab them until a minor has been added (i.e. 4.9.1)...
As they take a long time to build and aren't required by everyone
``` bash linux-image-4.6.3-ci-mq-nodebug_4.6.3-ci-mq-nodebug-10.00.Custom_amd64.deb ``` It's like Frankenstein's naming standard or something... You can see it happening when the package is being generated right at the last stage of the build:...
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [alstr/todo-to-issue-action](https://redirect.github.com/alstr/todo-to-issue-action) | action | major | `v4` -> `v5` | --- ### Release...