Platform Changelog

feedsince 2026-10-08patches hidden unless security or breaking

2026-10-292 days ago

Tektonv1.18.0minor+****Pipeline release v1.18.0 "Ukrainian Levkoy Ultron LTS"Tekton Pipelines v1.18.0 was released. The release adds a continueAndFail option on step.onError. Fixes include making controller-managed labels immutable via a webhook, fixing truncation of large Tekton bundles resolved from OCI images, fixing early PVC cleanup for pipelines-in-pipelines child pipelines, and bumping the plumbing ko image to Go 1.27.3.platform teamsTeams running Tekton can use continueAndFail to let a pipeline keep going after a step error, which changes failure handling in existing pipelines. The label immutability webhook and PVC cleanup fix affect controller behavior, so teams should review those when upgrading.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-283 days ago

Jenkins2.588minorsecurity!Jenkins weekly release 2.588 shipped with three changes: one security item and two other changes. The release notes say multiple security fixes were made and point to a separate security advisory dated 2026-10-28 for details. The source text does not list the specific vulnerabilities or affected components.platform teamsPlatform teams running Jenkins should review the linked security advisory and plan to upgrade to 2.588 to pick up the fixes. The source does not say whether the flaws are in Jenkins core or in plugins.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-274 days ago

Kargov1.9.16patch*Kargo v1.9.16 was released. The condensed notes list 16 changes, of which one is a fix: publishing best-releases.json on 1.9 releases. The remaining 15 are maintenance items such as dependency bumps, CI, tests and docs.platform teamsPlatform teams running Kargo 1.9 see a fix to release metadata publication, with no change to deployment behavior described in the notes. Nothing in the source indicates a breaking change.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-265 days ago

Fluxv2.10.0minorbreaking++~~~~~~~~~~~~~~~*Flux v2.10.0 shipped with 94 changes: 10 added, 73 changed, 4 fixed, and 4 marked breaking. Breaking changes include object identity always on with a narrowed default RBAC (no create on serviceaccounts/token), notification Alert and Provider APIs promoted to v1 with dropped v1beta3 fields, the artifact storage backend becoming the default for ImageRepository tag database, and a change to kubeConfig audiences key. The release also adds SPIFFE mTLS between controllers, OCIRepository as a HelmRelease chart source, and Zoom, incident.io and Mastodon notification providers, and updates Kubernetes to 1.37 and Go to 1.27.platform teamsPlatform teams upgrading Flux must bind a ClusterRole with serviceaccounts/token create permission to the controller ServiceAccount if they rely on default RBAC, and migrate v1beta3 notification resources to v1. Expect a full ImageRepository rescan after upgrade unless FluxStorage=false is set.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-238 days ago

Tektonv1.17.1patch*Pipeline release v1.17.1 "Egyptian Mau Robocop"Tekton Pipelines released v1.17.1. The release notes list one fix, which bumps the plumbing ko image to Go 1.27.3, and one other change updating examples to v1.17.1.platform teamsThe fix only changes the build toolchain image used for plumbing, so runtime behavior of Tekton Pipelines is not described as changed. Platform teams can treat this as a routine patch upgrade.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Tektonv1.15.5patch*Pipeline release v1.15.5 "Toyger Orisa" LTSTekton Pipelines v1.15.5, an LTS patch release, was published. The condensed notes list one fix that bumps the plumbing ko image to Go 1.27.3, plus an examples update, with 15 maintenance changes omitted.platform teamsThe only fix is a toolchain bump in build plumbing, not a change to pipeline runtime behavior, so platform teams on the v1.15 LTS line can take it as a routine patch. The source text does not describe any security content.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Tektonv1.12.3patch**Pipeline release v1.12.3 "Exotic Shorthair Elektrobots LTS"Tekton Pipelines v1.12.3 was released. The condensed notes list 53 changes, of which 50 are maintenance items such as dependency bumps, CI, tests and docs. The two fixes are a change to the release process that copies the vendor tarball into kodata instead of using a symlink, and a bump of the plumbing ko image to Go 1.27.3.platform teamsTeams running Tekton get a patch release with no new features or breaking changes listed in the notes. The Go toolchain bump is a build-time change to the plumbing image, and the release-process fix affects how the release artifacts are packaged.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Tektonv1.9.9patch**Pipeline release v1.9.9 "Devon Rex Dreadnought"Tekton Pipelines v1.9.9 was released. The condensed notes list two fixes: the release process now copies the vendor tarball into kodata instead of using a symlink, and the plumbing ko image was bumped to Go 1.27.3. The release also includes an Examples update, and 14 maintenance changes were omitted from the notes.platform teamsPlatform teams running Tekton can take this as a routine patch with no described change to pipeline behavior or APIs. The Go toolchain bump affects build tooling rather than the runtime features teams use.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Tektonv1.6.8patch**Pipeline release v1.6.8 "Sphynx Sentinels"Tekton Pipelines v1.6.8 shipped with two fixes on the release-v1.6.x branch. One change copies the vendor tarball into kodata instead of using a symlink, and the other bumps the plumbing ko image to Go 1.27.3. The release also includes an examples update and eleven maintenance changes such as dependency bumps, CI, tests and docs.platform teamsPlatform teams running Tekton v1.6.x get build-process fixes with no described change to pipeline behavior or APIs. The Go toolchain bump affects the build tooling only, so no action is indicated beyond routine upgrading.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-229 days ago

Argo CDv3.3.18patchsecurity!Argo CD v3.3.18 was released with two changes listed: one security item and one maintenance change. The security item is titled as an Emudhra CA certificates compromise for release 3.3. The source text gives no further detail on what was affected or how it was fixed.platform teamsPlatform teams running Argo CD 3.3 should review the release notes and apply the patch release. The source does not say whether the fix is in Argo CD code or only in bundled certificate data.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-2011 days ago

Jenkins2.587minor*****Jenkins 2.587 was released with five bug fixes. The fixes cover help text for the quiet-down block, caching of label expressions for load statistics, concise error display on form validation failures during page load, job name matching in global search suggestions, and preservation of ANSI colours in the live console after output pauses.platform teamsTeams running Jenkins controllers get fixes to UI behaviour and console output, with no changes to pipeline APIs or configuration called out in the source. Label-related load statistics now share cached results, which may matter for teams with heavy label usage.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-1516 days ago

OpenFeaturev0.18.0minorbreaking+++++~~~flagd: v0.18.0

Helmv3.22.1patchsecurity~~~!Helm v3.22.1 was released with a security item that bumps dependencies to remove Go package vulnerabilities. Other changes update the k8s.io Go packages to v0.37.1 and the OpenTelemetry OTLP trace exporters to v1.45.0. The notes also state that the next patch releases for Helm 4.3.2 and 3.22.2 are scheduled for November 11, 2026, and that Helm 4.4.0 is scheduled for January 13, 2027.platform teamsPlatform teams running Helm 3 get dependency-level CVE fixes in this release, but the source does not name the affected packages or the tool's own code. The notes say there will be no further Helm 3 minor releases after this line, so teams should plan migration to Helm 4.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

OpenFeaturev0.17.1patchsecurity!flagd: v0.17.1

GitLab19.5minorGitLab 19.5 was released on October 15, 2026. The GitLab MCP server and GitLab Secrets Manager are now generally available, and the MCP server gives external agents such as Claude Code and Cursor access to a wider set of GitLab tools. The release also adds beta support for connecting externally connected agents to AI Governance, plus non-default branch vulnerability tracking and several GitLab Duo CLI features.platform teamsPlatform teams can scope CI secrets per job by environment and branch and get audit logs for each secret operation, using existing GitLab permissions. Security teams can see sessions from agents running outside GitLab, with audit events sent to a SIEM, though this ECA capability is in beta.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-1318 days ago

Jenkins2.586minor+++++****Jenkins 2.586 was released with nine changes: five additions and four fixes. Added items include standardised shadows and focus rings for controls, removal of the Manage Jenkins breadcrumb menu, updated User settings pages, and a warning about unsafe authorization strategy. Fixes cover readOnlyMode propagation in dropdown fragments, locale handling in the search index, log recorder level updates, and dialog width limits.platform teamsPlatform teams running Jenkins controllers get UI changes and a warning when the authorization strategy is unsafe, which may prompt a review of their security configuration. The release notes list no breaking changes to pipelines or APIs.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-1219 days ago

Argo Rolloutsv1.10.1patchbreaking**Argo Rollouts v1.10.1 ships two fixes cherry-picked to the 1.10 line. The Rollouts dashboard now binds only to the local interface by default, which is marked as a breaking change. The release also allows Bidirectional mountPropagation on privileged containers, fixing issue #3130.platform teamsTeams that reached the Rollouts dashboard over a non-local address will need to expose it explicitly or port-forward after upgrading. Teams running privileged workloads that need bidirectional mount propagation can now use that setting on this version.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Argo Rollouts1.9.2patchbreakingsecurity*!Argo Rollouts v1.9.2 changes the Rollouts dashboard to bind only to the local interface by default. The release notes mark this as a breaking change for users who expose the dashboard through a custom Helm chart or another method. The release also lists a security fix, but the notes do not describe its details.platform teamsTeams that reach the Rollouts dashboard through a custom Helm chart or ingress must now explicitly configure exposure, or the dashboard will be unreachable from outside the local interface. Teams should review their dashboard access setup before upgrading.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Argo Rolloutsv1.8.5patchbreaking**Argo Rollouts v1.8.5 ships two fixes. The Rollouts dashboard now binds only to the local interface by default, which is marked as a breaking change. A yarn.lock file was also updated with correct dependencies.platform teamsTeams that reach the Rollouts dashboard over the network by default will need to expose it explicitly or port-forward to it after upgrading. The yarn.lock fix is a build-level correction with no stated effect on runtime behavior.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Kargov1.12.4patchKargo released v1.12.4 on 2026-10-12. The release notes list five changes, one of which is a security item bumping the step-security/harden-runner GitHub Action from 2.21.1 to 2.22.0. The other four are maintenance changes such as dependency bumps, CI, tests and docs.platform teamsThe only security-related change is a CI action dependency bump, not a fix in Kargo's own code, so teams running Kargo see no concrete behavior change from the notes provided. Teams may still want to confirm the full changelog before upgrading.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Kargov1.11.8patchKargo v1.11.8 was released with 7 changes, including one security item bumping the step-security/harden-runner GitHub Action from 2.21.1 to 2.22.1. The other six changes are maintenance items such as dependency bumps, CI, tests and docs, which the source condenses and omits.platform teamsPlatform teams running Kargo in their delivery pipelines get a patch release with a CI hardening action bump; the source does not describe any change to runtime behavior, configuration, or APIs. The security change is to a build-pipeline action, not a vulnerability fix in Kargo's own code.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-0922 days ago

Argo Workflowsv4.1.5patchsecurity**************!!Argo Workflows v4.1.5 was published with two changes, one added and one other, and one of them is marked as breaking. The release notes in the source are condensed and do not name the specific changes, pointing readers to the upgrading guide and the project's changelog.platform teamsPlatform teams running Argo Workflows should read the upgrading guide before rolling out v4.1.5, since a breaking change is flagged. The source text does not say what the breaking change is.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Argo Workflowsv4.0.13patchsecurity*******!Argo Workflows v4.0.13 was released with two changes, one marked as breaking and one added feature. The release notes in the source do not describe the specific changes and point to the upgrading guide and GitHub issues for details.platform teamsPlatform teams running Argo Workflows should read the upgrading guide for the breaking change before upgrading. The source text does not name the affected behavior.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

older entries

daily email

statuslast 30 days for lines

tools tracked43releases in registry964released in the last 30 days106entries published335breaking change lines18security lines84

change typestwo-column gutter, like git status

+addedNew functionality.
~changedExisting behavior changed.
-deprecatedStill works, scheduled for removal.
-removedDecommissioned, gone in this version.
*fixedA defect corrected.
!securityA vulnerability closed or a dependency patched for one.
!breakingFlag in the first column; the change needs action before upgrading.

filter

categoryall idp & portals ai agents on platform ci/cd observability supply chain cost & governance reports & dx data enterprise app platforms

showmajor only releases case studies postmortems include patches

Platform Changelog: what shipped in platform engineering, developer experience and DevOps