Swift NIO 2.80.0 contains a workaround for a miscompile which causes
swiftly to hang. Specifically code like `@usableFromInline let _free:
@convention(c) [...] = { free($0) }` miscompiles into a CPU spin loop on
some builds of `swift`.

Put a check in-place to unset the global default toolchain if it is no longer installed

Set the global default to the installed toolchain if it is not set

Add full toolchain selection resolution to the update operation resolve update parameters

Fix the use command and toolchain selection routine to consider a global default set to a toolchain that is not installed as no selection at all

Add check for the physical presence of a toolchain to proxy so that it prevents circularity errors and provides an actionable message

Allow uninstalling of partially installed toolchains from config.json

Control verbosity of uninstall operation on macOS and other platforms

Synthesize a product build and custom distribution plist.

Prepare for shell one-liner that update the shell environment.

Copy swiftly to the user home directory instead of install it in their home directory

Add more output to diagnose build release issues.

Change Debian 12 binutils-gold virtual package to binutils

Move some progress indications under verbose flag for shorter default install log

Correct productbuild issue when creating a pkg

Set the default swiftly home and binary locations on macOS to ~/.swiftly

)

Update the abstracts for the HowTo guides, Rename HOWTOS to Guides (#258)

Updates the abstracts for each of the HowTo guides, and renames the topic heading from 'HOWTOS' to 'Guides'.

Co-authored-by: Joseph Heck <[email protected]>

* Update swiftly README for the 1.0.0 release

* Add upgrade instructions for pre-1.0.0 swiftly

* Use the swiftly 1.0.0 release for the GH workflows

* Change default release version to 1.0.1 the release/1.0 branch

Fix the lists in Sources/LinuxPlatform/Linux.swift

* List toolchain location and restructure message concatenation

* Add introduction

* Mention modification of profile

Co-authored-by: Danny Mösch <[email protected]>

Remove swiftly from the path during proxying (#311)

Retaining swiftly in the path increases the probability that
a tool might run the proxy again, resulting in circularities.
Also, tools will locate programs in the path to try and find
adjacent toolchain files that cannot be discovered in the swiftly
bin directory.

Remove the swiftly bin directory from the path when proxying
to help improve the experience with other tools.

Add SDKROOT when proxying on macOS based on xcrun information (#316)

* Strip newlines from xcrun output

* Move release 1.0 to swift 6.1

* Update swift version check regexes in build script to work with swift at no minor version

Make the toolchains directory location configurable (#324)

Using a new environment variable SWIFTLY_TOOLCHAINS_DIR that
follows a similar pattern as SWIFTLY_HOME_DIR and SWIFTLY_BIN_DIR
make it possible for the user to configure the toolchain location
on init in the same way.

On macOS, this level of configuration requires a different approach
to extracting the toolchain whenever the installation location is
anything other than the default. Use the pkgutil utility of macOS
to extract the toolchain in the location specified by the user.
Installing the toolchains outside of the installer in a custom
location means that Xcode may not be able to pick them up easily.
Make a note of that in the init screen so that users are aware.

When using the init `--no-modify-profile` flag the init was skiping
steps like installing the latest toolchain, and emitting the notes
about updating the current shell environment. Separate this logic
so that the user can have these steps performed with the flag.

* Fix list-available showing wrong toolchain in use (#314)

fix: get `in use` toolchain from `selectToolchain` & parse `in use` separately

---------

Co-authored-by: Louis Qian <[email protected]>

)