Release 8.3.1

Only security and critical bug fixes! Feel free to suggest other changes we should include in the patch. Features will NOT be accepted.

Current changes planned to land in the patch:

• https://github.com/concourse/concourse/pull/9701
• https://github.com/concourse/concourse/pull/9702
• https://github.com/concourse/concourse/pull/9703
• https://github.com/concourse/concourse/pull/9695
• https://github.com/concourse/concourse/pull/9709
• https://github.com/concourse/concourse/pull/9697
• https://github.com/concourse/concourse/pull/9710
• https://github.com/concourse/concourse/pull/9714
• https://github.com/concourse/concourse/pull/9723
• https://github.com/concourse/concourse/pull/9728

Steps for a new patch release:

• Ensure each resource type is pinned to whatever version was last shipped within the MAJOR.MINOR series. This is to avoid accidentally shipping breaking changes in resource types with patch releases.

  • If a patch release is being shipped in order to bump a resource type (e.g. for a CVE or bug fix), pin it to the appropriate version instead.

• Once the final commit has made it through the pipeline, the create-draft-release job can be triggered. This job will create a draft release within the concourse GitHub release page where you can make any final adjustments or arrangements to the generated release notes. PLEASE NOTE that any manual changes made on the draft release WILL BE OVERWRITTEN if you retrigger the create-draft-release job. Please be sure to only make manual edits AFTER you are sure this is the final run of the job.

  • If you would like to edit the content, you can directly edit the PRs that it was generated from. The title is used for each PR and also the body within the Release Note header in the PR. After you have made your edits within the PR, you can rerun the create-draft-release job in order to regenerate a new release note.

  • If you would like to change the arrangement of the PRs within the release note, you can make the edits directly on the release note of the draft release.

• Once everything is ready, the shipit job can be triggered. The publish-binaries job will convert your draft release into a final release including the body of your draft release (which will persist any changes you made to the draft release body). Subsequently, the promote concourse job will run automatically. The publish-docs job runs automatically, as long as the version is actually the latest version available.

• The helm-chart pipeline is used to bump & then publish the chart.

  • (Optional) Merge the release/ branch into master by making a PR
  • Next, run the concourse-app-bump job (bumps the app version and image to point to the latest release): https://ci.concourse-ci.org/teams/main/pipelines/helm-chart?vars.version=7&group=dependencies
  • Run the k8s-smoke job
  • Finally, run the publish-chart-{major|minor|patch} job, depending on what has changed in the chart
  • If you make a major bump, be sure to update the CHANGELOG.md in the concourse-chart repo