yes, this is something we really should get to, currently blocked on #1208 and I don't know how to fix it myself. I might cut a release without sparcv9-sun-solaris.

I'm on vacation in august, maybe I can find some motivation and do this myself.

Thanks for the reply. No worries. I was mostly just wondering about the status.

it's going slowly, I'd want most of these to be merged/fixed and then I think we'd be good to go

@Emilgardis just checking on the progress, hopefully can bring a bit of support (moral or otherwise) 🙂
I was wondering if some of the items could be pushed to a 0.3.1. I am guessing most serious people are using the main branch or newer images at the very least these days.
It could be interesting to get some RC out for us to test / report issues more consistently too.
Appreciate all the work 🙏

thanks, thats an excellent suggestion, I've moved the non-breaking changes to a new milestone v0.3.1. The few remaining items seem very doable, although I can't promise it will be this week, I think my motivation seeing the new list went up a bit ;)

Also (削除) not on that list (削除ここまで) are some breakages in CI, but I think I'll rip the bandaid and just disable those targets until someone really wants it and can fix it. Can make them use the old images that used to work.

edit: I added the breakages as new issues and linked them to the milestone

Excellent! Glad I could help a bit :)
Eagerly waiting for it!!

You can also update cross to the main branch and that would automagically use the images on main.

Im sorry for the delay in getting a new version out, the reason is that my bandwidth is limited and the changes that remain are quite big. Just doing a 0.2.6 would be hard due to the time that has since passed and packages being deprecated.

I wont promise qnything but I feel like I'll be comfortable releasing 0.3.0 soon

Thanks for the quick reply.

Using cross from main branch isn't really great either for CI, IMHO, we do not really want to be a in a situation were the build breaks because of a change in this repo (it's already questionable for the docker images, but even more for the tool itself...).

me: wonder why github build works and "newest" tag doesn't
sees: v0.2.5: 684 commits to main since this release

Oh...