<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Breaking-Change on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/breaking-change/</link><description>Recent content in Breaking-Change on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 26 Aug 2026 11:21:00 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/breaking-change/index.xml" rel="self" type="application/rss+xml"/><item><title>GCP Cloud SDK 582.0.0 removes Cloud SQL Proxy V1 and several gcloud commands</title><link>https://curadevops.metacog.co.kr/insights/2026-08-26-august-25-2026/</link><pubDate>Wed, 26 Aug 2026 11:21:00 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-26-august-25-2026/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Cloud SQL Proxy V1 (&amp;lsquo;cloud_sql_proxy&amp;rsquo;) is removed from gcloud SDK 582.0.0 — audit infrastructure automation and connection scripts for V1 references and migrate to &amp;lsquo;cloud-sql-proxy&amp;rsquo; V2 before upgrading gcloud to 582.0.0.&lt;/li>
&lt;li>&lt;strong>CI/CD — Plan:&lt;/strong> If pipelines use gcloud to establish Cloud SQL connections or reference the removed api-registry MCP commands, they will break on upgrade to gcloud 582.0.0 — audit pipeline scripts and update to Cloud SQL Auth Proxy V2 before rolling out the new SDK version.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> breaking-change flagged&lt;/li>
&lt;/ul></description></item><item><title>Backstage v1.54.0 — three breaking changes including OAuth auth</title><link>https://curadevops.metacog.co.kr/insights/2026-08-24-v1-54-0/</link><pubDate>Mon, 24 Aug 2026 12:43:44 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-24-v1-54-0/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> If you operate Backstage, three breaking changes require pre-upgrade review: OAuth redirect URI wildcard semantics changed (audit any custom allowlist patterns before upgrading), the deprecated &lt;code>config.schema&lt;/code> extension option is removed (update any custom plugins using it), and the early Connections API contract shifted. Schedule the audit and upgrade this quarter.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> deprecation mentioned (no explicit date found)&lt;/li>
&lt;/ul></description></item><item><title>Prometheus 3.14.0: API deprecations and PromQL behavioral changes</title><link>https://curadevops.metacog.co.kr/insights/2026-08-24-3-14-0-2026-08-17/</link><pubDate>Mon, 24 Aug 2026 12:43:44 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-24-3-14-0-2026-08-17/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Three behavioral changes affect running Prometheus deployments: the stats query-parameter deprecation (other values still work but will be rejected in the next major), the __meta_hetzner_datacenter label drop for hcloud targets, and PromQL duration expressions now enabled by default. Review your relabeling configs, any Hetzner service-discovery rules, and PromQL queries before upgrading; no hard deadline yet since rejection is deferred to the next major release.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> deprecation/EOL deadline mentioned: 2026-08-17&lt;/li>
&lt;/ul></description></item><item><title>Jenkins 2.568.2 released with breaking changes noted</title><link>https://curadevops.metacog.co.kr/insights/2026-08-10-2-568-2/</link><pubDate>Mon, 10 Aug 2026 13:02:04 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-10-2-568-2/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>CI/CD — Plan:&lt;/strong> Jenkins 2.568.2 carries a breaking-change flag; review the upgrade guide before updating the Jenkins controller to avoid pipeline regressions.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> Jenkins 2.568 supported · breaking-change flagged&lt;/li>
&lt;/ul></description></item><item><title>GCP Cloud SDK 578.0.0 breaks database migration default behavior</title><link>https://curadevops.metacog.co.kr/insights/2026-07-29-july-28-2026/</link><pubDate>Wed, 29 Jul 2026 12:56:53 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-29-july-28-2026/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Cloud SDK 578.0.0 makes &amp;ndash;auto-commit the default for gcloud database-migration seed/convert/import-rules commands; audit any automation or runbooks that call these operations and add &amp;ndash;no-auto-commit explicitly before upgrading the SDK.&lt;/li>
&lt;li>&lt;strong>CI/CD — Plan:&lt;/strong> If pipelines invoke gcloud database-migration commands, upgrading to Cloud SDK 578.0.0 silently changes commit behavior; pin the SDK version or add &amp;ndash;no-auto-commit flags before the next runner/image update pulls this version in.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> breaking-change flagged&lt;/li>
&lt;/ul></description></item><item><title>etcd v3.6.14 patch release flagged with breaking change</title><link>https://curadevops.metacog.co.kr/insights/2026-07-27-v3-6-14/</link><pubDate>Mon, 27 Jul 2026 14:28:32 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-27-v3-6-14/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> etcd is the Kubernetes control plane&amp;rsquo;s backing store — a breaking-change flag in even a patch release means reviewing the upgrade guide before rolling this out to production clusters. No deadline is given, but operators should validate against their environment this quarter before routine patching.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> breaking-change flagged&lt;/li>
&lt;/ul></description></item><item><title>etcd v3.7.1 patch release flagged with breaking change</title><link>https://curadevops.metacog.co.kr/insights/2026-07-27-v3-7-1/</link><pubDate>Mon, 27 Jul 2026 14:28:32 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-27-v3-7-1/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> etcd backs every Kubernetes control plane, and a breaking change in a patch release is unusual — review the v3.7.1 CHANGELOG and upgrade guide before applying this update to any cluster, and validate in a non-production environment first. No hard deadline exists, but the breaking-change flag makes this a planned, careful upgrade rather than routine patching.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> breaking-change flagged&lt;/li>
&lt;/ul></description></item><item><title>GCP Batch enforces job-location constraint by July 31, 2026</title><link>https://curadevops.metacog.co.kr/insights/2026-07-21-july-20-2026/</link><pubDate>Tue, 21 Jul 2026 12:20:39 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-21-july-20-2026/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Act:&lt;/strong> GCP Batch will reject jobs whose &lt;code>allowedLocations[]&lt;/code> field lists regions or zones outside the job&amp;rsquo;s own location; the deadline is July 31, 2026 for most projects (June 30, 2027 for projects that already submitted a cross-region job before that date). Audit all Batch workloads for cross-region &lt;code>allowedLocations[]&lt;/code> entries and restrict them to the job&amp;rsquo;s location before July 31, 2026.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>Backstage v1.53.0: Three Breaking Changes in Auth, Config, and MCP</title><link>https://curadevops.metacog.co.kr/insights/2026-07-20-v1-53-0/</link><pubDate>Mon, 20 Jul 2026 14:01:18 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-20-v1-53-0/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Teams running Backstage need to audit OAuth redirect URI allowlist patterns (wildcards no longer cross host/path boundaries), validate config schema imports that may now fail to load, and migrate any MCP clients off the removed SSE transport to the Streamable HTTP endpoint before upgrading to v1.53.0.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> deprecation mentioned (no explicit date found)&lt;/li>
&lt;/ul></description></item><item><title>GCP July 14: gcloud SDK 576.0.0 breaking change + CVE patch</title><link>https://curadevops.metacog.co.kr/insights/2026-07-15-july-14-2026/</link><pubDate>Wed, 15 Jul 2026 12:10:55 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-15-july-14-2026/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> gcloud SDK 576.0.0 changes &lt;code>gcloud storage rsync&lt;/code> to decompress gzip downloads by default, which can silently break any operational scripts relying on the previous behavior; audit usage and add &lt;code>--do-not-decompress&lt;/code> or pin SDK version before upgrading. The bundled Python update for CVE-2026-34182 (EPSS 0.00, not KEV) adds low-urgency motivation to upgrade.&lt;/li>
&lt;li>&lt;strong>CI/CD — Plan:&lt;/strong> If pipelines invoke &lt;code>gcloud storage rsync&lt;/code> to pull artifacts, the 576.0.0 default-decompress behavior change will alter what lands in the workspace; pin the gcloud SDK version or add &lt;code>--do-not-decompress&lt;/code> before rolling out the upgrade across runners.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> BigQuery conversational analytics now carries HIPAA compliance support, broadening Gemini-in-BigQuery eligibility for regulated-industry workloads — worth factoring into GCP data platform strategy for healthcare or other compliance-sensitive verticals.&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> GA announcement · breaking-change flagged · CVE-2026-34182 — CISA KEV: not listed, EPSS 0.00&lt;/li>
&lt;/ul></description></item><item><title>Jenkins 2.568.1 released with breaking changes</title><link>https://curadevops.metacog.co.kr/insights/2026-07-13-2-568-1/</link><pubDate>Mon, 13 Jul 2026 14:29:28 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-13-2-568-1/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>CI/CD — Plan:&lt;/strong> Jenkins 2.568.1 carries a breaking-change flag; review the upgrade guide before updating your Jenkins controller to avoid pipeline or configuration regressions.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> breaking-change flagged&lt;/li>
&lt;/ul></description></item></channel></rss>