CI: Pin to specific version of Zephyr SDK in default PRs about libmetal HOT 3 OPEN

@arnopo what do you want to do about this? Right now libmetal is using 0.16.6 for CI and can change at any time. open-amp is using 0.16.1 (which is old but at least a fixed version.)

from libmetal.

The answer is not simple.

• if we fix the SDK and the Zephyr version. PRs related to a Zephyr update could fail as not build in a up to date environment. And we can miss some new Zephyr update in Zephyr that breaks compatibility.
• if we keep like this drawback is that CI breaks each time we have an SDK update.

I would say I would prefer to see the SDK issue ( CI is broken around 2 times /years) than miss something that would be discover during the release or after the release.

If the hypothesis is that the Zephyr build with lastest SDK with the main branch, what would be nice is to find a way to not have the SDK version hardcoded but pointing to the lastest version.

from libmetal.

Yes I would setup up a separate job to test against bleeding edge Zephyr. Not force individual contributors to deal with it.
We could automate the "know good" update but manually bumping it a few times a years seems OK to me.

from libmetal.