platformchangelog.dev
43 tools

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

feedbefore 2026-09-26all releases, patches included
newest entries
2026-09-241 month ago
How to deploy data kits in Salesforce Data 360postGearset's blog explains that Salesforce Data 360 data kits can deploy without their contained components, because retrieving a DataPackageKitDefinition returns only the list of contents. It describes a Gearset workflow that builds the package with dependencies, validates the kit, and adds a post-deployment activation step that runs Salesforce's separate publish process. The post also notes that Direct Deploy is available for some Data 360 components outside of kits, but not in automated CI jobs.platform teamsPlatform teams deploying Data 360 config through pipelines need a publish or activation step per environment, since a deployment can report success while data streams stay inert. Teams using a different tool would need to handle component retrieval, dependency ordering and activation themselves.Gearset Blog ↗GearsetSalesforce Platformwritten 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-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
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
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
2026-09-141 month ago
Argo CDv3.5.3patch**********
Kubernetes v1.37: Introducing Node Lifecycle ConditionspostKubernetes v1.37 reserves five well-known Node condition types: DrainInProgress, Drained, MaintenancePlanned, MaintenanceInProgress, and GracefulNodeShutdownInProgress. It also adds an Alpha NodeLifecycleConditions feature gate, disabled by default, which the release describes as a no-op in v1.37 since no core component reads the conditions yet. Administrators or authorized controllers are responsible for setting and clearing them.platform teamsPlatform teams can start publishing these conditions today from drain and maintenance automation to give dashboards, alerts and tooling a common status signal. No core controller changes behavior based on them in this release, so scheduling and eviction still rely on existing mechanisms.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
2026-09-081 month ago
Kubernetes v1.37: Advancing Workload-Aware SchedulingpostKubernetes v1.37 graduates the core Workload and PodGroup APIs, which enable gang scheduling, to Beta, along with workload-aware preemption and shared DRA ResourceClaims for PodGroups. The release adds a CompositePodGroup API for multi-level hierarchical scheduling, and makes minCount mutable so controllers can resize gangs. The alpha v1alpha2 API was replaced by v1alpha3, and the disruptionMode values were renamed from PodGroup and Pod to all and single.platform teamsPlatform teams running batch or AI/ML workloads on Kubernetes should plan for the v1alpha2 to v1alpha3 breaking change and the disruptionMode rename if they use the alpha APIs. Teams can also begin evaluating native gang scheduling and hierarchical scheduling for JobSet and LeaderWorkerSet workloads.Kubernetes Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-041 month ago
Investigate DMS migration issues with AWS DevOps AgentpostAWS published a guide on extending AWS DevOps Agent with a sample MCP server that provides read-only, DMS-specific tools and 46 runbooks for investigating database migration issues. The server is deployed on AWS Lambda behind an IAM-authenticated function URL and registered with a DevOps Agent Space. The post describes five investigation scenarios run against a test migration from RDS MySQL to Aurora PostgreSQL.platform teamsPlatform teams running DMS migrations can evaluate a read-only MCP pattern for giving an agent migration-specific context, with tools restricted to Describe, Get, List, Lookup and TestConnection calls. Timing claims in the post come from the authors' own test runs and are not benchmarked.AWS DevOps Blog ↗AWS DevOps AgentAmazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-031 month ago
Kargov1.11.4patch
Automating the Experimentation Lifecycle with Kiro, AWS DevOps Agent, and LaunchDarklypostAWS describes a reference architecture where AWS DevOps Agent runs a scheduled custom agent that plans feature-flagged experiments, uses Kiro CLI in a custom MCP server to write code and open pull requests, and deploys through GitHub Actions and AWS Amplify. LaunchDarkly runs the experiments and Guarded Releases, which roll back flag state when error or latency guardrails are breached. The post says the architecture is a reference implementation and that a more turnkey version is planned.platform teamsA platform team evaluating agent-driven delivery would need to scope MCP tools, restrict repos, branches and allowed tools, and manage credentials and state outside the container. The post notes that the scoping lives in server code rather than prompts, and that MCP tool allowlists are recommended for production.AWS DevOps Blog ↗AWS DevOps AgentAmazon EKSGitHub ActionsKubernetes MCP Serverwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-021 month ago
Jenkins2.580minorsecurity!
Jenkins Security Advisory 2026-09-02incidentJenkins published a security advisory dated 2026-09-02 that lists affected components: Jenkins core, update-center2, and about 18 plugins including GitLab, LDAP, SAML, Microsoft Entra ID, Script Security, and Pipeline: Groovy Libraries. The source text lists only the affected components and does not describe the vulnerabilities, severity, or fixed versions.platform teamsPlatform teams running Jenkins controllers should check the advisory for fixed Jenkins core and plugin versions and review which installed plugins are affected. The source text does not give the fixed versions, so the advisory itself must be consulted before deciding on upgrades.Jenkins security advisories ↗Jenkinswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Automate planned lifecycle upgrades with AWS DevOps Agent and KiropostAWS describes a pattern in which AWS Health Planned Lifecycle Events for Amazon EKS trigger EventBridge and a Lambda function that starts AWS DevOps Agent to investigate the upgrade and produce a CDK change spec. The spec is validated in a GitHub Actions workflow, then Kiro CLI in headless mode edits a single stack file and a pull request is opened for human review. The post also describes an automated failure path that investigates failed deployments and opens a fix pull request, with one retry attempt.platform teamsPlatform teams running EKS on AWS could adapt this event-driven pattern to handle managed service end-of-support deadlines, with human review kept at the pull request. The source is a vendor blog post with sample code and does not report measured results.AWS DevOps Blog ↗Amazon EKSAWS DevOps AgentGitHub Actionswritten 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 days106entries 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