Release engineering is exhausting so here's cargo-dist

1. cargo-dist

   1 11 1,672 9.8 Rust

   📦 shippable application packaging

   

   Just to elaborate on this a bit: as discussed in the Concepts section of the docs[0] the core of cargo-dist absolutely supports workspaces with multiple binaries, and will chunk them out into their own distinct logical applications and provide builds/metadata for all them.

   However this isn't fully supported by the actual github CI integration yet[1], as I haven't implemented proper support for detecting that you're only trying to publish a new version of one of the applications (or none of them!), and it doesn't properly merge the release notes if you're trying to publish multiple ones at once.

   I never build workspaces like that so I'm waiting for someone who does to chime in with the behaviour they want (since there's lots of defensible choices and I only have so many waking hours to implement stuff).

   [0]: https://github.com/axodotdev/cargo-dist/#concepts

2. InfluxDB

   influxdata.com featured

   InfluxDB high-performance time series database. Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.

   

3. act

   2 155 60,126 9.1 Go

   Run your GitHub Actions locally 🚀

   

   Seconding this; act has a lot of potential but misses a number of features such as support for deployment environment variables (eg `${{ var.DEPLOY_SPECIFIC_ENV_VAR }}`) and only recently added support for reusable workflows (https://github.com/nektos/act/issues/826). It looks like fine software and the maintainers deserve praise for their work but it's not yet a drop-in replacement for GitHub Actions.

4. cargo-install-favorites

   3 2 48 6.1 Shell

   Use the `cargo` command install our favorite crates

   

   Awesome thank you. I'm adding it now to the awesome list here: https://github.com/sixarm/cargo-install-favorites

5. sgr

   4 23 322 1.5 Python

   sgr (command line client for Splitgraph) and the splitgraph Python library

   

   I wrote up the details of this in a PR [0] where I last dealt with it.

   [0] https://github.com/splitgraph/sgr/pull/656

6. goreleaser

   5 65 14,547 9.9 Go

   Release engineering, simplified

   

   i really enjoy goreleaser https://github.com/goreleaser/goreleaser/ and use it with rust https://github.com/chmouel/snazy/blob/main/.goreleaser.yaml#... combined with build matrix https://github.com/chmouel/snazy/blob/main/.github/workflows...

7. snazy

   6 1 33 8.7 Rust

   a snazzy json log viewer (with one z)

   

   i really enjoy goreleaser https://github.com/goreleaser/goreleaser/ and use it with rust https://github.com/chmouel/snazy/blob/main/.goreleaser.yaml#... combined with build matrix https://github.com/chmouel/snazy/blob/main/.github/workflows...

8. release-plz

   7 6 1,031 9.7 Rust

   Publish Rust crates from CI with a Release PR.

   

   How does this tool differ from release-plz?: https://github.com/marcoIeni/release-plz

9. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

10. ideas4

    8 26 88 4.6

    Discontinued An Additional 100 Ideas for Computing https://samsquire.github.io/ideas4/

    Thanks for remembering me :-)

    I would like things to run locally by default and then deployed to the cloud where they run.

    Should be easier to debug problems if I can get the code to my machine and investigate issues with tools that my computer has such as "strace", "perf" and debug logging that I liberally apply to the build script.

    In production we would have log aggregation and log search (such as ELK stack) and it is a good habit to get into the perspective of debugging production via tooling.

    But CICD feels before that tooling in the pipeline. You could wire up your CICD to log to ELK but I would prefer local deployable software.

    I think my focus on automating things means I want to be capable of seeing how the thing works without relying on a deployed black box in the cloud and using assumptions of how it works rather than direct investigation.

    One of my journal entries is almost a lamentation of all the things that need to be done to release and use software.

    This is that entry:

    https://github.com/samsquire/ideas4#5-permanent-softwareplat...

    I wonder if software could be deployed more like a URL that has all the information to configure a virtual machine. Docker over URL or something.

11. cargo-binstall

    9 24 1,917 9.5 Rust

    Binary installation for rust projects

    

    If you happen to install a lot of things with cargo, check out cargo-binstall: https://github.com/cargo-bins/cargo-binstall

    It'll fetch the binary release from the repo so you don't have to compile it yourself.

Suggest a related project