cargo-dist
cargo-dist copied to clipboard
axodotdev
📦 shippable application packaging
Feature request: make it so the release workflow for a PR can cope with a workspace that has projects that have different version numbers. Something like `pr-run-mode="plan-by-project"`. Rather than reporting...
In my situation, I have proper system dependencies for Linux and MacOS with apt/brew (working fine!). For Windows, I have a few lines to run before building my executables (nothing...
I found the release notes generated by cargo-dist doesn't have the changelog that can be auto generated by GitHub * https://github.com/korandoru/hawkeye/releases/tag/v5.3.2; vs * https://github.com/korandoru/hawkeye/releases/tag/v5.2.0 Is there some config I can...
There should be a way to tell install-path to try to use XDG dirs (quick skimming suggests that just means ` $HOME/.local/bin`?). What exactly that means on windows is contentious,...
Right now, we assume that generic build artifacts are located at the root of the build directory. We should add a configuration value that configures an alternate root to locate...
Hey, In one of my rust projects we use a monorepo. I've wondered if it is possible to tell cargo-dist to run all the workflows within a sub directory?
It's possible for the `repository` field in Cargo.toml and the actual location of the cloned repo to disagree with each other. If this happens, it can lead to inconsistencies in...
So it seems Apple Silicon (M1) macOS runners are now available on GitHub Actions. https://github.com/orgs/community/discussions/69211 In the limitation section of https://opensource.axo.dev/cargo-dist/book/ci/github.html#bring-your-own-release you say: > GitHub currently only provides x86_64 macOS...
cargo-dist should more fundamentally understand how you structure your releases/versions, and should potentially be in charge of updating/committing them. I don't know if this entails us absorbing/partnering with a specific...
in #848 we're more aggressively leaning on info passing through the manifest and getting merged, but no tests actually check that manifest merging works right. This is annoying to Properly...