Conversation
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
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.32.0→0.33.0Release Notes
axodotdev/cargo-dist (axodotdev/cargo-dist)
v0.33.0Compare Source
This release includes several new features and a change to the shell installers in certain environments.
Azure Artifact Signing for Windows binaries and installers
We now include support for codesigning Windows binaries and installers using Azure Artifact Signing. For more information, see the docs.
This currently only supports x86_64 Windows targets, and doesn't support aarch64 Windows targets or non-Windows targets.
Shell installers now place
envhelper alongside receipts for flat installsIn previous versions of dist, we would place the
envhelper scripts which add your program to the user'sPATHalongside the binary when using a "flat" install layout. ("Flat" layouts consist of only a single directory, as opposed to the default "hierarchical" layout that places binaries in a "bin" subdirectory.) Beginning with dist 0.33.0, we instead place theenvscript in the app-specific config path alongside the install receipt. By default, this is~/.config/$APP_NAME. If users had installed a previous version of your app, newer versions of the installer will migrate oldenvfiles to the new location in addition to updating the user's dotfiles.-impl @Gankra Install env scripts in receipts dir instead of bin dir
Fixes
--repoin bothgh attestationcommandsConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.