platformchangelog.dev
43 tools

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

feedbefore 2026-09-23all releases, patches included
newest entries
The operations gap between deploying an application and running it foreverannouncementAWS announced Elastic Beanstalk Cluster Mode, which accepts an application as source code, a Dockerfile, or a pre-built container image from Amazon ECR and runs it on Amazon EKS. The source says AWS handles deployment, scaling, patching, monitoring and upgrades for the life of the application, with automatic rollback when health checks fail. The service is available in all commercial AWS Regions where Elastic Beanstalk is offered, with no additional Elastic Beanstalk service fee beyond underlying resources.platform teamsPlatform teams evaluating managed hosting for a mixed portfolio could consolidate containerized and legacy apps under one operational model with AWS-run environments. The post is vendor-written and gives no performance or cost figures, so the cost and reliability benefits it describes are unverified.AWS Containers Blog ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Implement per-pod image pull permissions with ECR repository policies on Amazon EKSpostAWS describes a walkthrough for scoping Amazon ECR image pull permissions to individual Kubernetes pods on Amazon EKS. The approach uses KEP 4412 per-pod credential support in kubelet, with the ecr-credential-provider assuming a team IAM role through a service account annotation and ECR repository policies enforcing access. The post states the feature needs Kubernetes 1.34 or later, with full support on EKS v1.35 or later.platform teamsPlatform teams on multi-tenant EKS can give each namespace its own ECR pull role instead of relying on the shared node role, but they must create a ClusterRole and ClusterRoleBinding for the sts.amazonaws.com audience before nodes join, and must update node credential provider configuration. Pods without the annotation fall back to the node role.AWS Containers Blog ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
How GitLab reduced code-per-agentic-flow ratio by 45%postGitLab describes Flow Registry, a declarative YAML framework that compiles into LangGraph flows for its Duo Agent Platform, built from reusable components, routers and a shared state structure. GitLab says using it cut its own code-per-agentic-flow by 45%. The article is partial in the feed and does not include independent measurements.platform teamsPlatform teams building or evaluating agent workflows on GitLab could define agents and routing in YAML instead of hand-written graphs, which may reduce maintenance work. The 45% figure is GitLab's own internal metric and is not independently verified.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
How to design GitLab for enterprise scalepostGitLab's blog publishes a guide on designing GitLab for enterprise scale, covering choosing between GitLab.com, GitLab Dedicated and Self-Managed, runner scope and executor choice, and availability targets. It also covers measuring queued duration, job duration and runner utilization to find pipeline bottlenecks. The excerpt provided is cut off before the Kubernetes and checklist sections.platform teamsPlatform teams evaluating GitLab at scale get a checklist of sizing inputs, including runner scope, executor choice and RTO/RPO targets to define before rollout. Nothing in the excerpt changes GitLab product behavior.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Salesforce DevOps tools: why the highest-performing teams don’t stop at deploymentreportGearset publishes an analysis based on its State of Salesforce DevOps 2026 report, arguing that teams covering more of the six DevOps lifecycle stages report fewer bugs, less rework and less downtime. The post says high adopters are nearly twice as likely to keep error rates below 5%, spend 56% fewer hours on rework and lose 62% less time to downtime. It also reports that observe and operate are the least covered stages, and that 43% of teams apply no extra review to AI-generated changes.platform teamsPlatform teams running Salesforce can use the stage-by-stage coverage model to audit their own toolchain, particularly the observe and operate stages. The post is written by a vendor selling a competing DevOps product and the survey methodology is not described in the source text.Gearset Blog ↗GearsetSalesforce Platformwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-211 month ago
Backstagev1.55.1patch**
Kubernetes v1.37: Tracking When a PersistentVolumeClaim Was Last Used (Beta)postKubernetes v1.37 promotes the PersistentVolumeClaimUnusedSinceTime feature gate to Beta and enables it by default. The PVC protection controller now sets an Unused condition on each PVC, with status True and reason NoPodsUsingPVC when no non-terminated pod references it. The condition's lastTransitionTime records when the PVC became idle.platform teamsPlatform teams can list idle PVCs with kubectl and jq instead of cross-referencing pods and volumes with custom scripts, which helps find orphaned storage that drives cloud costs. The feature is on by default in v1.37, and the project intends to reach GA in a later release.Kubernetes Blog ↗editorCorrection 2026-10-20: this was listed as a Amazon EKS v1.37 release by mistake. It is Kubernetes Blog coverage, not release notes from the project.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Extend Server Logic with Power Automate Cloud Flows in Power PagesannouncementMicrosoft announced support for invoking Power Automate cloud flows from Server Logic in Power Pages. The feature lets website server-side logic call existing cloud flows. Microsoft says this gives access to more than 1,400 connectors in Power Automate.platform teamsPlatform teams that govern Power Pages can reuse existing cloud flows and their connector governance instead of building separate integrations. The post gives no details on permissions, deployment, or limits, so teams should check the documentation before relying on it.Microsoft Power Platform Blog ↗Microsoft Power Platformwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-171 month ago
Rate limits on GitLab.com are changingannouncementGitLab.com is changing its API rate limits so they depend on subscription tier. Free accounts and unauthenticated requests are limited starting October 19, 2026, with preview windows on October 7 and October 14, and Premium and Ultimate limits change in January 2027. Unauthenticated requests are capped at 60 per hour per IP address, and exceeding a limit returns HTTP 429 with a Retry-After header.platform teamsPlatform teams whose pipelines, bots, or agents call the GitLab.com API without credentials will hit the 60 requests per hour anonymous cap and should move calls to personal access, OAuth, or job tokens. Teams should check RateLimit-Remaining headers against their plan's published limits before the October 19 change, and self-managed and Dedicated instances are not affected.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
See who spent your AI credits and set fair caps per teamannouncementGitLab 19.4 adds per-user management of GitLab Credits, letting admins set a flat per-user cap, add overrides for individuals, and see spend. Admins can also export per-event usage data covering up to 31 days, delivered by email as a summary, per-event file and manifest. Usage syncs periodically, so spend already in flight can cross a cap before enforcement catches up.platform teamsPlatform teams can allocate AI agent budgets per team and per developer, map namespace IDs to cost centers for showback, and pull session-level records for investigating spikes. Teams should account for the periodic sync delay when setting caps.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
New MCP tools help platform teams scale automationpostGitLab 19.4 substantially expands the GitLab MCP server tool set with CI/CD, merge request, work item, vulnerability and project tools, currently in beta. Read-only actions run without a human in the loop by default, while writing, merging or deleting actions wait for a reviewer the team chose. A new Merge request created trigger lets a flow or external agent run when an MR is opened once the diff is generated.platform teamsPlatform teams can let agents retry pipelines, read job logs, open and update MRs, and merge when checks pass, with approval gates set per action. Vulnerability tools require the Ultimate tier, and the MR created trigger requires Premium or Ultimate with GitLab Duo Agent Platform enabled.GitLab Blog ↗GitLabeditorCorrection 2026-10-20: this was listed as a GitLab 19.4 release by mistake. It is GitLab Blog coverage, not release notes from the project.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-161 month ago
Kubernetes v1.37: Hardening Container Storage with Bind Mount Options and EmptyDir PermissionspostKubernetes v1.37 adds alpha support for bindMountOptions on volume mounts, letting users set noexec, nosuid and nodev on the bind mount the container runtime creates. It also adds an alpha mode field for emptyDir volumes, so permissions such as 01777 or 0750 can be set natively instead of via init containers. Both features sit behind the VolumeBindMountOptions and EmptyDirVolumeMode feature gates.platform teamsPlatform teams can enforce noexec and sticky-bit emptyDir permissions in pod specs, but must enable both alpha gates on the API server and kubelet and confirm runtimes advertise the mount_options runtime feature, since kubelets reject pods on nodes lacking support.Kubernetes Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Jenkins Security Advisory 2026-09-16announcementJenkins published a security advisory dated 2026-09-16 listing 13 affected plugins, including Bitbucket Push and Pull Request, Bitbucket Server Integration, Coverage, Gitee, GitLab, Gradle, Keycloak Authentication, OWASP Dependency-Check, Pipeline: Groovy Libraries, Pipeline: Multibranch, Robot Framework, Script Security, and Warnings. The source text does not describe the vulnerabilities, their severity, or the fixed versions.platform teamsTeams running Jenkins with any of the listed plugins should check whether they have them installed and consult the full advisory for affected and fixed versions. The source text gives no details to confirm the scope of exposure.Jenkins security advisories ↗Jenkinswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-151 month ago
Crossplane2.4.1patchsecurity+*!!!!Crossplane v2.4.1 updates the Go toolchain to 1.26.7, google.golang.org/grpc to v1.83.2, and golang.org/x/crypto to v0.56.0 to pick up upstream CVE fixes, including the gRPC advisory GHSA-2v4p-qf9q-27wj. It also bumps the Crossplane apis module to v2.4.0. The release changes how package revisions take control of established objects, so an incoming revision can take over CRDs from the revision it replaces.platform teamsPlatform teams upgrading to v2.4.1 get the dependency CVE fixes without changes to their own configuration. Package upgrades that previously could leave a new provider unhealthy with a cannot establish control of object error should now hand off automatically, without deleting the stale revision or editing CRD owner references by hand.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Crossplanev2.3.6patchsecurity+*!!!!Crossplane v2.3.6 updates the Go toolchain to 1.26.7 and bumps google.golang.org/grpc to v1.83.2 and golang.org/x/crypto to v0.56.0, which the release notes say pick up upstream CVE fixes, including a gRPC advisory. It also fixes a package revision hand-off bug where an outgoing revision could fail to release CRD control, leaving the incoming provider stuck with cannot establish control of object and no pod created.platform teamsPlatform teams running Crossplane packages should pick up this patch, since providers stuck on a replaced revision previously needed manual CRD owner-reference edits or deletion of the stale revision. The security content is dependency bumps only, not a vulnerability in Crossplane's own code.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Crossplanev2.2.6patchsecurity+*!!!!Crossplane v2.2.6 updates the Go toolchain to 1.26.7 and bumps google.golang.org/grpc to v1.83.2 and golang.org/x/crypto to v0.56.0, including a gRPC advisory fix. It also changes package revision handoff so a new revision takes control of CRDs from the revision it replaces, fixing a case where the incoming provider's pod was never created and needed manual cleanup.platform teamsPlatform teams upgrading to v2.2.6 get dependency CVE fixes, and provider package upgrades no longer stall with a cannot establish control of object error that previously required deleting the stale revision or editing CRD owner references by hand. The security content is dependency bumps only, not a vulnerability in Crossplane's own code.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Kubernetes v1.37: Pod-Level Resource Managers graduated to BetapostKubernetes v1.37 graduates the Pod-Level Resource Managers feature to Beta, disabled by default and controlled by the PodLevelResourceManagers feature gate. The Topology Manager, CPU Manager and Memory Manager can now use pod-level resource declarations when making hardware placement decisions. The v1 PodResources gRPC service also adds top-level cpu_ids and memory fields for pod-level exclusive assignments.platform teamsPlatform teams running latency-sensitive workloads can reserve exclusive NUMA-aligned CPU and memory for primary containers while placing non-Guaranteed sidecars in a pod-isolated shared pool. Teams that opt in should check monitoring and device plugins that read PodResources, since they can now query pod-level assignments without double-counting containers.Kubernetes Blog ↗editorCorrection 2026-10-20: this was listed as a Amazon EKS v1.37 release by mistake. It is Kubernetes Blog coverage, not release notes from the project.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Kubernetes v1.37: Native Histograms Graduates to BetapostKubernetes v1.37 graduates native histogram support for Kubernetes metrics to Beta and enables it by default. Components expose classic histogram buckets alongside Prometheus native histogram spans in the same Protobuf payload, using a bucket factor of 1.1 and a cap of 160 buckets. Prometheus 3.x users can enable scraping per job with scrape_native_histograms and keep classic series with always_scrape_classic_histograms.platform teamsPlatform teams running Prometheus should plan to migrate dashboards and alerts from _bucket queries to native histogram queries while keeping always_scrape_classic_histograms true during transition. Rollback is available by setting scrape_native_histograms to false or disabling the feature gate.Kubernetes Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
daily email

One short email each morning: what shipped, what breaks, and a link to each change. Unsubscribe in one click. Privacy.

statuslast 30 days for lines
tools tracked43releases in registry964released in the last 30 days105entries published336breaking 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
categoryallidp & portalsai agents on platformci/cdobservabilitysupply chaincost & governancereports & dx dataenterprise app platforms
showmajor onlyreleasescase studiespostmortemsinclude patches