v5.3.0

_^🔗 feature

• @rliebz added the ability for put steps to git resources with the parameter merge: true to be further configured with the parameter returning: unmerged, which will ensure that concurrent changes to the same remote branch do not affect downstream jobs concourse/git-resource#262.

_^🔗 feature

• Added the option for the BOSH Backup and Restore database backup job in the BOSH release to be configured via a BOSH link concourse/concourse-bosh-release#29, concourse/concourse-bosh-release#35.

_^🔗 feature

• @stigtermichiel tuned our build process so that the size of the compressed frontend code is reduced by a factor of 3 - page loads should be accordingly faster #3915.

_^🔗 feature

• If you want your web node to accept encrypted connections over HTTPS, you now have the option of connecting to an ACME server to automatically retrieve a certificate from an ACME server of your choice. By default it will reach the free public ACME service provided by Let's Encrypt.

  Thanks to @henderjm for the PR #3878!

_^🔗 feature

• @agurney improved the info api endpoint (/api/v1/info) to return both the external URL and cluster name #3862.

  Hopefully this will enable future improvements to fly and the web UI!

_^🔗 feature

• @jmccann enabled Concourse to authenticate with Vault as a credential manager via an LDAP backend by setting CONCOURSE_VAULT_AUTH_PARAM="username:<your ldap username>,password:<your ldap password>" #3884.

_^🔗 feature

• When you pin a resource through the web UI, your name and current local time will now be automatically added as the pin comment #3743.

_^🔗 feature

• The 'password' field on the login page now has an HTML property that will be ignored by most browsers, but helps Concourse pass some automated security scans #3839.

_^🔗 feature

• @tvon gave the highlighted lines on the build page a slightly darker color so they really pop #3866.

_^🔗 fix

• @palixthepalalix fixed a bug in the git resource where commits from extraneous branches could appear in the version history if a tag filter was specified concourse/git-resource#261.

_^🔗 fix

• Made the Concourse worker process systemd-aware. This fixed a subtle bug introduced in v5.0.0 that could, on rare occasions, cause container limits not to be enforced or prevent containers from being killed concourse/concourse-bosh-release#24, concourse/concourse-bosh-release#31.

  Thanks to @bodymindarts for contributing to this effort.

_^🔗 fix

• Addressed a bug where in rare circumstances, fly intercept -c would find multiple check containers for the same resource #3983.

_^🔗 fix

• In service of a refactor, task caches are now decoupled from the worker(s) they are stored on. As a result, you may find that in multi-worker deployments, pipelines making use of task caches may consume duplicate storage across workers #3830, #3965.

_^🔗 fix

• Corrected a surprising behaviour where, when a pipeline was paused for an extended period of time, many of its resources' versions would disappear #3963.

_^🔗 fix

• There was a long-standing bug on the dashboard, where the existence of circular pipelines would cause the browser to crash. This was fixed in v5.2.0, but the fix caused a performance regression, which is now also fixed #3870, #3901.

_^🔗 fix

• Fixed a bug, introduced in v5.1.0, where, on a build step with attempts: specified, only one attempt would be possible to view on the build page #3898.

_^🔗 fix

• @gaelL Fixed a bug, which had existed since at least v4.2.3, where operators were prevented from retiring team-scoped workers with the concourse retire-worker command #3929.

_^🔗 fix

• A bug on the reaped build logs screen was fixed, where a link was pointing to deprecated documentation #3931.

  This screen is visible when you visit a build that is older than its job's configured retention policy.

_^🔗 fix

• Fixed a problem with one of the database migrations introduced in v5.0.0 which could cause the web node startup to fail in some cases. This won't affect users who have kept up to date until now, but if this is the first version of Concourse you are deploying since before v5.0.0, the upgrade should be a little more resilient #3996.

_^🔗 fix

• @mockersf fixed a problem where timestamps weren't being properly returned when a get step or a put step finished. This caused some wacky durations to be displayed on build pages #3871.

_^🔗 fix

• Fixed an issue with our build process that caused fly to stop working for some folks making use of a VPN with split DNS.

_^🔗 fix

• Fixed a bug where the dashboard preview of a paused job with a pending build would show the color of the most recent build's status, when it should be blue #3718.