concourse/concourse v6.4.0

on GitHub

_^🔗 feature

• @mouellet added a way of renaming pipeline resources while preserving version history by updating the resource name (as well as any reference in steps) and specifying its old name as old_name. After the pipeline has been configured, the old_name field can be removed. #5833

_^🔗 feature

• Archived pipelines can be displayed in the web UI via a toggle switch in the top bar. #5777, #5760

_^🔗 fix

• Fixed a regression where builds could be stuck pending forever if an input was pinned by partially specifying a version via the version: on a get step, version: on a resource config or by running fly pin-resource. #5780

_^🔗 fix

• @evanchaoli fixed a regression that prevented using both static vars and dynamic vars simultaneously in a task. #5758

_^🔗 fix

• Pipelines can be re-ordered in the dashboard when filtering. This was a regression introduced in 6.0. #5821

_^🔗 feature

• Style improvements to the sidebar. #5778

_^🔗 fix

• The sidebar can now be expanded in the UI - no more long pipeline names being cut off! #5782

_^🔗 feature

• Add --include-archived flag for fly pipelines command. #5673

_^🔗 fix

• fly login now accepts arbitrarily long tokens when pasting the token manually into the console. Previously, the limit was OS dependent (with OSX having a relatively small maximum length of 1024 characters). This has been a long-standing issue, but it became most noticeable after 6.1.0 which significantly increased the size of tokens. Note that the pasted token is now hidden in the console output. #5770

_^🔗 feature

• Add --team flag for fly set-pipelines command #5805

_^🔗 fix

• Fix a validation issue where a step can be set with 0 attempts causing the ATC to panic. #5830

_^🔗 fix

• Fix tooltip on pipeline names. PR: #5855

_^🔗 feature

• Refactor existing step structure to simplify introducing new steps. The primary user facing changes are stricter validation and slightly different step validation messages. Previously, fields that were not part of a step wouldn't have failed validation,however, now they will. This will impact stateful actions such as set-pipeline. PR: #5504, #5878

_^🔗 feature

• @tlwr updated the set_pipeline step to be used across teams. This is 'experimental' for now, please share your feedback in the thread. PR: #5729

_^🔗 feature

• @evanchaoli added OPA integration to Concourse to enable policy enforcement. The RFC #41 for the integration is still in progress so it is considered 'experimental'. PR: #5034

_^🔗 feature

• Add support for task.run.user field in containerd runtime. Issue: #5144 PR: #5704