Releases: lando/setup-lando
Releases · lando/setup-lando
v3.6.0
Changes
- Added
--syslink
to add symlink to/usr/local/bin
on POSIX install, see notes below - Improved post-install
PATH
consideration messaging - Updated default
--dest
to~/.lando/bin
on POSIX install - Updated POSIX script to run
sudoless
if possible, see notes below
Notes
--syslink
will be automatically set onCI
--syslink
will be automatically set if alando
already exists at/usr/local/bin
and the invoking user has permission to edit itsudoless
install just means the script itself does not requiresudo
, you may still get downstreamsudo
requests like inlando setup
v3.5.0
- Added
path
based installation to POSIXsetup-lando.sh
script - Added GitHub Actions
RUNNER_DEBUG
support to PowerShell script - Fixed bug preventing POSIX/Windows script from replacing existing
lando
installations - Fixed bug preventing Windows script from downloading the correct
dev
alias - Fixed bug causing Windows script to persist
utf-16
encoding
v3.4.5
v3.4.4
v3.4.3
- Updated docs
v3.4.2
- Fixed bug causing GitHub convenience aliases eg
3-edge-slim
to incorrectly resolve to releases with hitherto unpopulated assets
v3.4.1
- Fixed bug causing
&&
separatedauto-setup
command strings to not run correctly
v3.4.0
New Features
- Added
LANDO_VERSION
as a way to set theversion
in the install pathways
Fixes
- Fixed bug causing
@lando/setup-lando
GitHub Action to fail on Windows usingbash
Internal
- Updated download locations to standardize on relevant
core
andcore-next
pathways
v3.3.0
- Removed automatic
lando update
fromsetup-lando.sh
to be consistent with other install pathways and because it makes--version
sort of pointless 😉
v3.2.2
- Fixed
windows
setup script passing incorrect parameter towsl
setup script #46