Releases: lando/core
Releases · lando/core
v3.20.1
v3.20.0
New Features
- Added support for Docker Compose V2 which is now the default orchestrator.
- Added an
orchestratorVersionoption to the global config. - Added
healthchecksupport to all Lando 3 services. - Added a generic Lando 3
landoservice into core. See - Bumped support of Docker Compose to
1.x.x || 2.x.x - Bumped support of Docker Desktop to
>=4.0.0 <4.24 - Bumped support of Docker Engine to
>=18 <25 - Dropped support for Docker Desktop
<4.0.0
Fixes
- Fixed bug where
lando ssh --helpwas incorrectly listingappserveras the defaultservicein some situations - Fixed bug where
cliwas needlessly printingusermod: no changes - Fixed bug where dynamic tooling events were not setting the service with an option correctly
- Fixed bug where
proxyservice was wiping outapp.compose - Fixed deprecated usage of
network.external.nameonlando_proxyedge
Internal
config.ymlfrom@lando/coreis now loaded after theconfig.ymlfrom@lando/cli
DEPRECATIONS
Global Config
composeBinis now discouraged in favor oforchestratorVersion.maxandminindockerSupportedVersionsare now discouraged in favor ofsatisfies.
v3.17.2
v3.17.1
v3.17.0
- Added
~/.lando/binas preferred install location for Docker Compose - Switched release flow over to @lando/prepare-release-action
- Docker Compose
1.29.2will now be automatically installed to~/.lando/binif a suitable version is not detected, this is to prepare for Docker Compose V1 being removed from Docker Desktop
v3.16.2
v3.16.1
v3.16.0
v3.15.0
v3.14.0
Changelog
- Added new and improved URL
scannerprovides real time feedback on service status. READ MORE - Improved
scannerreliability by preferring IPv4 #21
Notes
This pre-release is a bit more experimental than most pre-releases. It implements a new URL scanner that
- Provides real time updates on the status of services URLS
- Has a new
pathoption so you can configure a different path besides/to scan - Has a new
timeoutoption so you can configure the time to wait for a response from your service - Has a new
retryoption so you can configure the amount of retries the scanning does per service - Has a new
okCodesoption so you can configure additional code eg404that should pass the scanner
See more here: https://docs.lando.dev/core/v3/scanner.html
Report scanner errors here: https://github.com/lando/lando/issues