I assume it’s somewhere in Stefano’s work, but it ...
# core
s
I assume it’s somewhere in Stefano’s work, but it looks like CI is failing. I’m not going to cut a release, since it wouldn’t be buildable.
s
I have a branch I know works for x86_64 and I'm now testing for Linux aarch64. I'm fighting different permissions on the filesystem of the self hosted runner.
s
Thank you. Holler if you get to needing PRs approed
👍 1
s
Now I hope the CI will hold for a couple of days at least. I have in the backburner the update of all the actions, because that's also another place where they are deprecating stuff. But updating that might also touch some paths for packaging, so it's not quick.
s
Is there a bigger set of changes we should make that would work “better”? (My hunch is not, but I feel like I should ask)
s
If you mean, something that lands before the release, it's not necessary unless they deprecate those actions in the next two days. It's mostly that I'd like to get back to it Monday.
s
I mean after the release. If you want to make bigger changes for better future support.
s
ah I see; I cannot think of something to change. Mostly it's the upload-artifact action which will zip things with a different path. With "it's not quick" I mostly meant that I cannot just increase the version number or do the update blind. The full pipeline needs to be tested. But it shouldn't also be a tragedy to update (hopefully haha)