Aria Desires

potential approach (performed in precise sequence): 1. release "dist" 1.0.0 (it can be a version less than that but let's call it that for now) 2. release "cargo-dist" 0.X.0 *...

The bulk of this work is in #1267

(will re-evaluate this when core stuff is more settled, thanks for the info!)

Things typically desired of a release system: * ability to specify which things should be included in a release (are we just releasing a library? or an app proper? or...

for the purposes of config, if we were to make our own config and not using someone else's, assume we're adopting #841, and there would be a `[release]` section

Could you elaborate on what reason you need this for, so that I know what you do/don't want this to affect? (Note that Cargo already lets you call your binaries...

whoever does this should duplicate the logic to also fill in the "authors" (maybe actually prompt for this like we do for npm scopes) (...or "the {repo_name} authors"), that's the...

per the linked issue, a bit messier than i'd like (the obvious flags are too new for the platforms where this matters)

the user did find this works ``` [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; irm https://astral.sh/uv/install.ps1 | iex ``` but lord that makes me sad to ask someone to run

5.1 is the last version of powershell windows users have (everything after is "core") https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/invoke-restmethod?view=powershell-5.1