Skip to content

chore(deps): update dependency concourse/concourse to v8#499

Open
renovate[bot] wants to merge 1 commit intodevelopfrom
renovate/concourse-concourse-8.x
Open

chore(deps): update dependency concourse/concourse to v8#499
renovate[bot] wants to merge 1 commit intodevelopfrom
renovate/concourse-concourse-8.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Feb 3, 2026

This PR contains the following updates:

Package Update Change
concourse/concourse major 7.14.38.1.1

Release Notes

concourse/concourse (concourse/concourse)

v8.1.1

Compare Source

What's Changed

🐞 Bug Fixes
🛠️ Misc. Changes

📦 Bundled Resource Types

Details

Full Changelog: concourse/concourse@v8.1.0...v8.1.1

v8.1.0

Compare Source

What's Changed

✈️ Features
🐞 Bug Fixes
🛠️ Misc. Changes
❗ Known Issues
  • There's a regression in the latest lib/pq release that we indirectly use via Dex. If you're using a Client key and certificate to connect to Postgresql, make sure the file permissions are set to 0640 or 0600. Any other setting (higher or lower) will result in the error error: failed to perform migrations: creating migration table: pq: private key has world access; permissions should be u=rw,g=r (0640) if owned by root, or u=rw (0600), or less
    • If you're using the Helm chart to deploy Concourse, the latest version 20.1.0 changes the file permissions of the Client key and cert to 0600. Previously it was 0400, which is how we discovered this issue.
    • lib/pq issue: lib/pq#1257

📦 Bundled Resource Types

Details

New Contributors

Full Changelog: concourse/concourse@v8.0.2...v8.1.0

v8.0.2

Compare Source

What's Changed

  • We updated our build process to bring in newly compiled versions of the Linux container runtime dependencies (containerd, runc, CNI plugins, etc.). We grab most of these from Wolfi's APK repository. For runc, we needed a statically compiled version, so we compile that ourselves (pipeline here). The motivation for this was to clear out CVE's related to the version of Go that each of those binaries were compiled with. If you scan the Linux tarball in this release you should find no CVE's (at the time of publishing at least)
  • Fix task caches by reverting #​9330 but keep using sha256 instead of sha1 by @​taylorsilva #​9429
    • As a side-note, you can define absolute paths for your task caches. See concourse/docs#583 for details

📦 Bundled Resource Types

Details

Full Changelog: concourse/concourse@v8.0.1...v8.0.2

v8.0.1

Compare Source

What's Changed

📦 Bundled Resource Types

Details

Full Changelog: concourse/concourse@v8.0.0...v8.0.1

v8.0.0

Compare Source

Thank you to all the people that contributed to this release! You can read this blog post for an overview of the changes:

https://concourse-ci.org/blog/2026-01-15-v8---new-year-new-concourse-release/

What's Changed

🚨 Breaking Changes
✈️ Features
🐞 Bug Fixes
🛠️ Misc. Changes

📦 Bundled Resource Types

Details

New Contributors


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/concourse-concourse-8.x branch 4 times, most recently from 9b4b099 to aa8c907 Compare February 3, 2026 17:12
@renovate renovate Bot force-pushed the renovate/concourse-concourse-8.x branch from aa8c907 to 1ad11cc Compare February 19, 2026 22:51
@renovate renovate Bot force-pushed the renovate/concourse-concourse-8.x branch from 1ad11cc to 4dd2fcf Compare March 4, 2026 16:35
@renovate renovate Bot force-pushed the renovate/concourse-concourse-8.x branch from 4dd2fcf to 2268582 Compare March 17, 2026 22:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant