chore(ci): Update Rust versions in CI to 1.74, 1.78, and 1.79

[v0y4g3r]

• I agree to follow the project's code of conduct.
• I added an entry to CHANGELOG.md if knowledge of this change could be valuable to users.

---

This PR changes the rust toolchain for CI according to geo_types because geo_types no longer compiles with current CI settings.

[v0y4g3r]

@lnicola @frewsxcv Could you please have a look at this PR?

[lnicola]

Any particular reason to only run these on master?

[v0y4g3r]

Any particular reason to only run these on master?

No, I just thought it would be nice to let actions only run on importance branches like master. But maybe better to keep the original behavior 14c5816

[lnicola]

This doesn't actually bump rust-version in the manifest, though I suspect it still builds on older versions?

[v0y4g3r]

This doesn't actually bump rust-version in the manifest, though I suspect it still builds on older versions?

I updated the changelog in f23ed65. This PR only changes the CI toolchain.

[michaelkirk]

"Yes we support older versions, but we don't know how to build them" doesn't make sense to me.

I'd say bump the rust-version, call it an MSRV and move on with your lives.

The alternative you're leading us down here is to have an MSRV that doesn't mean anything to anyone. How would we know when it breaks?

[michaelkirk]

To clarify: Whatever is listed as rust-version in Cargo.toml should have a corresponding build in CI. If that means you need to bump rust-version, (I think) that's OK.

[lnicola]

But if we switch to rustup, we might not need to bump the MSRV.

[lnicola]

Since we're at this, we should also update time to 0.3.35 or 0.3.36.

[lnicola]

And do we really need a custom image, or can we build it directly?

[michaelkirk]

And do we really need a custom image, or can we build it directly?

In the geo and proj repos anyway, we use libproj which takes a while to build, so having a custom image was the way that we cached that build to speed up CI.

Probably you could set something else up though.

Or if you're not using those dependencies, I expect you'd have luck using a standard container.

[v0y4g3r]

Since we're at this, we should also update time to 0.3.35 or 0.3.36.

Will do.

And do we really need a custom image, or can we build it directly?

In the geo and proj repos anyway, we use libproj which takes a while to build, so having a custom image was the way that we cached that build to speed up CI.

Probably you could set something else up though.

Or if you're not using those dependencies, I expect you'd have luck using a standard container.

AFAIK the CI does not need a customzied container to do those actions:

• cargo build --no-default-features
• cargo test --no-default-features
• cargo build --all-features
• cargo test --all-features

[lnicola]

Filed #109 as an alternative without the containers.