New release perhaps?

[svenstaro]

Hey, the latest release is almost a year old by now and a few cool things have landed in master. Perhaps it's time for a new release?

[UebelAndre]

I too would like to see a new release which includes #543

@reitermarkus would you be able to do this?

[reitermarkus]

Feel free to send a PR with a version bump and changelog update.

[svenstaro]

I suggest using cargo-release for stuff like this which will basically automate all of that away for you so you can only type cargo release and have even the CHANGELOG be generated for you. :)

[Dylan-DPC-zz]

Tbh i prefer doing it manually, ensures we haven't overlooked anything or included any breaking changes by mistake. (Also getting publishing rights would be nice ;) )

[reitermarkus]

CI should be set up to do everything automatically when a tag is pushed

[reitermarkus]

… except the changelog part.

[UebelAndre]

Does anyone have bandwidth to throw together that PR? 🙏

[UebelAndre]

@adamgreig @burrbull @Emilgardis @reitermarkus @ryankurte @therealprof
Sorry for pinging the entire tools team, but would any of you be able to create and merge a PR for a new release? 🙏

[therealprof]

It's a bit unfortunate that the CHANGELOG is not continuously maintained. Otherwise a release wouldn't be a big deal.

Edit: I've just created PR #552 to reduce that pain for the future.

I haven't been paying too much attention to cross lately so I'm very likely to miss something if I were to create a CHANGELOG. Any volunteers?

[UebelAndre]

I'm brand new to this repo but I do think my change (#543) might be a good one to go in the change log.

[rawkode]

Waiting on #543 too 😅

[lpil]

Hello all! It would be fantastic to get a release out as #543 is needed to fix my build and is currently blocking releases. Thank you

[Emilgardis]

There are some standing issues with this version, namely changelog and windows support (that is, cross doesn't work on windows anymore).

There will be an announcement posted where we want more eyes on this codebase.

[adamgreig]

We've also posted a call for help in #574 asking for assistance with maintenance and getting a new release out the door.

[svenstaro]

So with the CHANGELOG change merged, how are we looking for a release?

[svenstaro]

@adamgreig ping

[UebelAndre]

@Emilgardis with CI now unblocked, would it be possible to get a new release? 😅 🙏

[Emilgardis]

haha, no, what I meant with CI being crippled is that we basically have no CI now 😁 need to get #609 up and running to actually publish the changes in the images

[Emilgardis]

Should we do a release and fix Windows in a later version? I think that's the only remaining issue now that CI is fixed

[svenstaro]

I think it would be prudent to make a release now and figure out any remaining problems later at any rate.

[Emilgardis]

Windows support has been fixed and CI is up and well.

I think the only (new) issue left is #683

[abrisco]

@Emilgardis hey, thanks for all the work on the project! Was wondering, what the outstanding blockers were to creating a new release?

[Emilgardis]

I have one last concern with the x86_64-unknown-linux-gnu now being centos, but I think we're set to make a release.

This release would update a lot of workflows using cross in CI, especially those that use actions-rs, so it'd be good to make sure we're all set and everything is correct and that we don't break any assumptions, even though this would be a semver break.

It'd be nice if we could test this new release in CI, to do so yourself with GHA, you can just install cross manually before running the action that uses cross: run: cargo install cross --git https://github.com/cross-rs/cross

[abrisco]

@Emilgardis hello again. Is there a tracking issue or PR for the outstanding work?

[Emilgardis]

the issue with x86_64-unknown-linux-gnu is #680, im still not sure we know how to best proceed

[Emilgardis]

We've now released v0.2.2, thank you everyone for your involvement and patience!

Full list of changes can be found on the release page. Read the README and wiki for guidance.

#857