0.14.2

[navarr]

Welcome to 2024! Let's start this year off with an exciting Warden release!

What's Changed

• Project and Local Warden commands will now take precedence over built-in warden commands (#676 by @flpandre)
• New Magento 2 projects will default to the latest version of Magepack (#712 by @sprankhub)
• Traefik will now properly fallback to the default Warden certificate (#725 by @SamJUK)
• warden vnc now properly connects to the container (#721 by @sprankhub)
• warden status will now properly work with dashes in project names and urls (#685 by @bap14)

New in Images

Images are regularly updated, and these fixes roll out ASAP after they are merged. This is just a summary of what changes have occurred between the last release and the new one.

• MagePack Bundle and Generate files have corrected permissions (images#12 by @ihor-sviziev)
• Resolved issues with node update crashing the php container
• Updated Nginx mapping to route to XDebug when XDEBUG get/post session parameters are present
• Added versions of services:
  • ElasticSearch 8.9, 8.10, 8.11
  • MariaDB 10.10, 10.11, 11.0, 11.1, 11.2, 11.3-rc
  • MySQL 8.2
  • Nginx 1.24, 1.25
  • OpenSearch 2.7, 2.8, 2.9, 2.10, 2.11
  • PHP 8.3
  • RabbitMQ 3.12, 3.13-rc
  • Redis 7.2
  • Varnish 7.3, 7.4

New in Documentation

Documentation is regularly updated, and these changes roll out ASAP after they are merged. This is just a summary of what changes have occurred between the last release and the new one.

• A broken link from Installation to the DNS Resolver configuration page was fixed (docs#18 by @danni140c)
• The Magento 2 testing documentation has been updated to point to the correct config directory when referring to API tests (docs#11 by @evktalo)

Our Sponsors

A huge shoutout to our Gold sponsors between 0.14.1 and 0.14.2:

---

This discussion was created from the release 0.14.2.

[emreakay]

how can i upgrade my warden

[bap14]

@emreakay Depends on how you installed it. If it was via brew, just run brew upgrade warden. If you installed it manually using git, you can just run a git pull then warden svc down && warden svc up to restart all services. If you installed it manually any other way, you'd have to essentially do whatever you did before, replace the existing installation files with the current version, then restart warden services.

[emreakay]

thanks