Ci release

[gwbres]

No description provided.

[lnicola]

I wonder if a single app-approach (rinex crx2rnx [stuff]) wouldn't be easier for the users.

If you need more inspiration for CI workflows, you can check out https://github.com/rust-lang/rust-analyzer/blob/master/.github/workflows/release.yaml and https://github.com/rust-lang/rust-analyzer/blob/master/.github/workflows/ci.yaml. They're not perfect, but maybe you see something interesting in there.

[gwbres]

I wonder if a single app-approach (rinex crx2rnx [stuff]) wouldn't be easier for the users.

If you need more inspiration for CI workflows, you can check out https://github.com/rust-lang/rust-analyzer/blob/master/.github/workflows/release.yaml and https://github.com/rust-lang/rust-analyzer/blob/master/.github/workflows/ci.yaml. They're not perfect, but maybe you see something interesting in there.

Thank you for pointing that out, I will take a look if we can grab a few things from there.

Regarding the app, honestly I don't know. It's only a matter of writing a different name in a workflow script.
Both approaches work, but either way it is important to maintain an access to dedicated functions like crx2rnx.
Because you can easily imagine some users might have their own processing programs but want to use our decompression program in their workflow

[gwbres]

If you need more inspiration for CI workflows, you can check out https://github.com/rust-lang/rust-analyzer/blob/master/.github/workflows/release.yaml and https://github.com/rust-lang/rust-analyzer/blob/master/.github/workflows/ci.yaml. They're not perfect, but maybe you see something interesting in there.

From what I can see we're not far from truth, they also use a very lengthy and tedious artifact upload then download then publish sucessive steps. Unfortunately the publish step is what it is, and the artifact download seems the only option to retrieve what you're interested in. I may try to use a strategy.matrix in the future, to reduce the length of the script.

I'll trigger this release to make sure the binaries name are correct.
Then we need one final PR for the artifacts actual publication