cargo-dist
cargo-dist copied to clipboard
axodotdev
📦 shippable application packaging
This isn't a big deal but it's ugly. Serde is auto-sorting them, when really we'd like to keep them in the same order they're checked in. I'm not sure if...
we currently support an infinite number of targets in the targets array, but github has a finite and specified number of default runners. if someone adds a target that does...
I didn't really notice at the time, but [the docs for custom build jobs](https://opensource.axo.dev/cargo-dist/book/reference/config.html#build-global-artifacts-jobs) say that "build-local-artifacts-jobs" and "build-global-artifacts-jobs" are the names of these configs, but in fact they're "local-artifacts-jobs"...
I'm attempting to integrate a custom job into the `cargo-dist` CI workflow to build a docker container and push it to GHCR. I was able to do this without `allow-dirty`...
We can catch this in plan for the user. 
in https://github.com/axodotdev/oranda/pull/667 we had ``` [[workspace.metadata.dist.extra-artifacts]] artifacts = ["oranda-css/dist/oranda.css"] build = ["cargo", "run", "--", "generate-css"] ``` and this made cargo-dist want to create an artifact *named* `oranda-css/dist/oranda.css`, which is, not...
The cargo-dist [dist-manifest.json format](https://opensource.axo.dev/cargo-dist/book/reference/schema.html) is an amalgam of bolted on concepts and features and needs a major cleanup. ## per-machine info dist-manifest is lacking a proper notion of "per-machine" output...
There are several situations where cargo-dist needs to fetch itself or axoupdater: * in ci to bootstrap with curl-sh/irm-iex, we need to fetch the shell script, and then fetch whatever...
The dispatch-releases feature implicitly relies on the fact that GitHub Releases automatically creates a tag if you ask it to create a GitHub Release for a given tag name, which...