chore(deps): update dependency cargo:cargo-dist to 0.29.0#1267
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/cargo-cargo-dist-0.x
branch
from
520e288 to
1b97a9a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.28.0->0.29.0Release Notes
axodotdev/cargo-dist (cargo:cargo-dist)
v0.29.0Compare Source
This is a big release! 0.29.0 includes all of the new features from Astral's fork of dist along with some new bugfixes. It also removes support for Axo Releases.
Pinning GitHub Actions to commits
By default, dist uses Actions via floating versioned tags such as
actions/checkout@v4. Users with specific security requirements may instead want to pin these to specific commits so that they know exactly which version will be run. This release provides configuration to allow users to specify which commit to use for a given action. For more information, see the docs.Recursive source tarballs, including the contents of submodules
While we've had support for source tarballs since 0.5.0, those tarballs have been limited to the contents of the base repository and didn't contain the contents of submodules. (This is a limitation of the
git archivetool that we use to generate them.) This release adds support for recursive tarballs that include the contents of submodules as well. This feature is opt-in and can be enabled with therecursive-tarballs = truesetting. For more information, see the docs.Support cross-compiling from Windows to Windows
In previous versions, dist would refuse to cross-compile from one Windows architecture to another. This release fixes that and allows the build to be attempted. We still default to cross-compiling via
cargo-xwin; users who would like to try this will need to configure their builds to use a Windows runner. For example:Installer improvements
We've improved compatibility for the shell installer by bringing in newer changes from the Rustup installer it was originally based on. We've also improved compatibility with Linux distributions that don't use the
$HOMEenvironment variable.BYO GitHub bearer token for installers
In addition to the above, we now allow users to bring their own GitHub token to be used when fetching tarballs from GitHub. This is useful for users who are often rate-limited when downloading artifacts or who need to fetch artifacts from private repositories. Like our other environment variables, this is branded with your application's name in the format
{APP_NAME}_GITHUB_TOKEN. This environment variable is supported in both the shell and PowerShell installers. For more information, see the docs.{APP_NAME}_GITHUB_TOKENinstall env-varReduce unnecessary credentials persistence in Actions config
This release includes some tweaks to generated Actions config in order to reduce the risk of accidentally persisting credentials longer in the run than necessary. This is always enabled and doesn't require configuration to opt into.
Allow overriding binaries per-platform
It's now possible to override the set of binaries to install on a per-platform basis. For example, a project with three binaries may choose to only install two of them on Windows, or may choose to provide an extra binary on other platforms. For more information, see the docs.
New setting for overriding packages to dist
A new top-level option,
packages, allows specifying a list of exactly which packages should be disted. This overrides any individualdist = trueordist = falseset in individual packages, and can be easier to reason about. For more information, see the docs.Overriding package versions
The new top-level
versionoption overrides the individually-configuredversions for every package and instead causes dist to assume every package has the specified version. For more information, see the docs.Fixes
v0.28.2Compare Source
This release updates dependencies and contains no substantive code changes.
v0.28.1Compare Source
This release contains several important bugfixes. This primarily ensures that GitHub Actions builds work again, but there are also several fixes for minor configuration issues and updates to the runtime dependencies for the npm installer.
Fixes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.