If (big if) I were to undertake some CI automation work to auto bump kernels to latest would this PR serve as a good template for what has to be done?

I note you are only updating the 6.12 line, presumably because that’s the latest major.minor version supported? I assume all tests etc point at the latest major.minor?

If (big if) I were to undertake some CI automation work to auto bump kernels to latest would this PR serve as a good template for what has to be done?

That is a "big if" because it is a big lift. I did a lot of work a few years back to make updating the kernels much easier, which should help a lot, but it still requires a chunk of work.

The whole process is listed in docs/kernels.md, both for a new patch version (6.12.z) and a new series (6.y); major version is the same as new series, from the perspective of linuxkit.

If you can do that, by all means.

Keep in mind that building a new kernel version can be slow, especially when cross-building for architectures. That may or may not hit up against GHA job time limits.

@ChrisIgel looks like the "build packages" job failed.

That is a "big if" because it is a big lift.

yeah i understand its a lot (i mean, look at this pr) but its also very close to something I've recently done in $company with renovate+github actions. i have to wonder if an 80% solution would at least make the process easier. if its not wanted (or im missing a hilarious amount of complexity here) thats reasonable

Keep in mind that building a new kernel version can be slow, especially when cross-building for architectures.

i was consider i could bypass that as its own check and instead simply open a pr with the latest, allowing the normal pr workflow to work normally. it appears i may need to do more reading though

yeah i understand its a lot (i mean, look at this pr) but its also very close to something I've recently done in $company with renovate+github actions

That is something I would like to see. Funny how many of us have worked for that same place, $company 😆

i have to wonder if an 80% solution would at least make the process easier.

It absolutely would. I am in favour!

@ChrisIgel looks like the "build packages" job failed.

But only because the new kernel version wasn't built and published yet, which is a manual step currently, or am I mistaken?