platformchangelog.dev
43 tools

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

feedbefore 2026-10-08all releases, patches included
newest entries
2026-10-0526 days ago
Scaling Kubernetes Workloads with Node SwappostThe Kubernetes blog reports benchmarks of node swap backed by Local NVMe SSDs across a Linux kernel build, headless Chrome sandboxes under runc, gVisor and Kata, and Python sandboxes. Node swap reached General Availability in Kubernetes v1.34 and is configured through the kubelet with LimitedSwap. The post reports pod density gains of up to 3x in these tests, with the latency cost mainly attributed to CPU competition at peak density.platform teamsPlatform teams running memory-heavy CI or agent sandbox workloads can evaluate swap on Local SSD nodes to raise pod density, but must set workloads to Burstable QoS and size swap for burst rather than steady-state use. The results come from Google Cloud test nodes and the post does not give independent methodology beyond linked repositories.Kubernetes Blog ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-10-011 month ago
Implementing feature flags in container environments with AWS AppConfigpostAWS Containers Blog published a walkthrough of using AWS AppConfig with its agent running as a sidecar in Amazon ECS tasks and Amazon EKS pods to serve feature flags. The application reads flags from a localhost HTTP endpoint, and the agent handles polling and caching. The post includes sample manifests, a task definition, and a discount flag example.platform teamsPlatform teams can change feature flag values at runtime without rebuilding or redeploying containers, using the same sidecar pattern on both ECS and EKS. Teams should still plan for service-level API throttling at high agent counts, which the post notes.AWS Containers Blog ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Amazon EKS Auto Mode now supports advanced compute configurationannouncementAmazon EKS Auto Mode now lets users set kubelet settings, Linux kernel sysctls, and hugepages through a new advancedCompute field in the NodeClass resource. The settings are applied declaratively via the Kubernetes API, validated, applied at node boot, and kept through scaling and upgrades. The feature is available in all AWS Regions where EKS Auto Mode is offered.platform teamsPlatform teams can run workloads that need node tuning, such as user namespaces for rootless builds, eviction thresholds, and hugepages, without maintaining EC2 launch templates, custom AMIs, or privileged DaemonSets. Teams running EKS Auto Mode should evaluate whether this replaces their existing node customization.What's New with AWS ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-301 month ago
Salesforce CLI2.152.14minorsecurity+~***!Salesforce CLI 2.152.14 adds --debug-level and --category-level flags to the apex run command for controlling anonymous Apex debug logs, and the two flags are mutually exclusive. It removes a Hyperforce/JWT gate that blocked sf org create user on Hyperforce orgs when the Dev Hub used JWT authentication. The release also fixes sf org open exiting before the browser launched, a broken sf-trust bin path in @salesforce/plugin-trust, and adds support for the ReferralIntakeConfiguration metadata type in DX projects. A security fix bumps the npm version pinned in npm-shrinkwrap.json to pull in a patched tar.platform teamsTeams running anonymous Apex from the CLI can set debug log levels per predefined level or per category. Teams that run user creation on Hyperforce orgs with JWT Dev Hubs can now use that command, and the npm install failure from the broken bin path is resolved.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
AI-powered EKS migration assessment with Amazon Bedrock AgentCorepostAWS published a walkthrough for building a migration assessment agent with Amazon Bedrock AgentCore and the Strands Agents SDK. The agent reads application source code and container artifacts from platforms such as OpenShift, Azure and on-premises Kubernetes, then produces a readiness score, ranked blockers and a migration plan for Amazon EKS. The source text was cut off before the deployment steps.platform teamsPlatform teams assessing many applications for EKS migration could automate the first-pass readiness review, with the output still needing engineer review. The post describes a reference implementation rather than a shipped product feature.AWS Containers Blog ↗Amazon EKSAWS DevOps Agentwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
What is the Agentic Development Lifecycle and do you need it?postThe author argues that the Agentic Development Lifecycle (ADLC) maps almost stage for stage onto the existing software development lifecycle (SDLC). He says Agentforce agents are deployed as metadata, so existing release and version control practices apply, and that metadata types have changed over the past year, such as Agent Planner bundles becoming Agent Script. He recommends limiting agents to analysis and building while deterministic CI/CD, testing, review and backups handle the rest.platform teamsPlatform teams running Salesforce should keep applying existing release governance, change failure rate and DORA measurement to AI-produced changes, and track Agentforce metadata format changes in release notes. Nothing new is shipped that changes tooling.Gearset Blog ↗GearsetSalesforce PlatformAgentforceDORA State of DevOps / AI-assisted development reportwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-291 month ago
Terraform Provider for SAP BTP1.27.0minor+****SAP released version 1.27.0 of the Terraform Provider for SAP BTP. The release notes list one added action, action_update_global_account, and four fixes covering function label extraction for legacy labels, failing early when an amount is set on non-quota entitlement plans, drift resolution for role collection assignments with custom IAS origins, and an auto_create_shadow_users option in the globalaccount trust configuration.platform teamsPlatform teams managing SAP BTP through Terraform get a new action for updating global accounts and fixes that reduce configuration drift for role collections and trust settings. Teams using entitlement plans should note that amount on non-quota plans now fails at plan time instead of being silently accepted.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-251 month ago
One Amazon EKS, many edges: How to choose your edge container strategy on AWSpostAWS published a guide on running Amazon EKS as one standard across many edge locations, with the deployment model chosen per site. The post proposes a two-step method: first check whether a site has a reliable connection to an AWS Region, then choose between EKS Hybrid Nodes, EKS on Outposts, or EKS Anywhere based on existing infrastructure. It also lists pricing for each model and notes that Windows workloads are supported only on Outposts.platform teamsPlatform teams running many edge sites can use the connectivity-gated decision flow to standardize on one Kubernetes API and pipeline while varying the deployment model per site. Teams should check the pricing table and the Windows and Linux-only constraints before choosing a model.AWS Containers Blog ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
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
Salesforce CLI2.151.7minor++****Salesforce CLI 2.151.7 shows deploy notifications in both JSON and human-readable table output, and adds Refresh Token Rotation support so simultaneous commands no longer fail with a token-processing error. It also fixes plugin install, uninstall and update failures on Windows paths with spaces, false-positive diffs for Aura CSS edits, handling of AiAgentDefinitionVersion names containing #, and ENOENT errors on standalone Unix tarball installs.platform teamsPipelines that run project deploy start now see deploy-level notifications such as ApexApiVersionRetirement in the table output, and connected apps with RTR enabled work without extra flags. Teams using AI agent metadata can deploy and retrieve versioned agent definitions without the earlier delimiter errors.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-221 month ago
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
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-181 month ago
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-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
2026-09-101 month ago
Kubernetes v1.37: Scheduler Preemption for In-Place Pod Resize (Alpha)postKubernetes v1.37 adds an Alpha feature behind the InPlacePodVerticalScalingSchedulerPreemption feature gate that lets the kube-scheduler preempt lower-priority Pods on the same node so that a running Pod's deferred in-place resize can be actuated. Previously a Deferred resize could remain pending indefinitely until node capacity freed up. The Kubelet delegates this preemption decision to the scheduler rather than evicting locally.platform teamsPlatform teams bin-packing lower-priority batch workloads can allow higher-priority Pods to scale up in place without restarts, but must enable the gate across kube-apiserver, kube-scheduler and kubelet on v1.37 clusters. The feature is Alpha, and the new spec.podPreemptionPolicy node field lets controllers opt specific nodes out of resize preemption.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-021 month ago
Salesforce CLI2.150.6minor***
2026-08-282 months ago
Two views, one org: mapping business processes to Salesforce metadatapostThe post argues that Salesforce teams need a map linking business processes to the metadata that implements them, because org documentation goes stale and changes carry risk. It describes three traditional discovery methods (talking to the business, reviewing regression tests, and reviewing historical tickets) and notes that dependency tooling is limited by API restrictions. It then presents Gearset's Agent and Org Intelligence as a way to generate a live, dependency-aware map of org metadata.platform teamsPlatform teams running Salesforce may find dependency mapping before changes useful, but the post gives no measured results and the claimed benefits are the vendor's own. The post also notes that AI reads implementation rather than intent, so changes still need review against business requirements.Gearset Blog ↗GearsetSalesforce Platformwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-08-262 months ago
Salesforce CLI2.149.9minor++***
2026-08-212 months ago
A virtual teammate vs a copilot: what’s the difference?postGearset argues that AI coding tools differ between copilots, which assist a developer step by step, and virtual teammates, which take a ticket and return a review-ready pull request. The post lists questions for evaluating tools, including whether they hold org context, are shared across a team, adapt to feedback, and work within existing governance. It closes by promoting the Gearset Agent.platform teamsPlatform teams evaluating agents for Salesforce delivery should check whether an agent runs through the same tests, security checks and review gates as human changes, and whether it has org context. The post itself gives no measured results and no concrete product change.Gearset Blog ↗GearsetSalesforce Platformwritten 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