Hetzner’s Cloud changelog records that the deprecated response field was removed on November 2, 2026 from endpoints returning images, server types and load balancer types. If an inventory tool still reads that field, review the replacement path before trusting its deprecation report.
Hetzner Cloud changelog: November 2 field removal
The replacement path depends on the resource
For images and load balancer types, the changelog directs clients to deprecation. For server types, it directs clients to the deprecation field of the respective entry in locations. That extra level matters when a tool summarizes a server type across several locations.
Treat the November entry as the removal-stage notice. It refers back to the September 8 announcement. An old migration ticket that only records the announcement date should be updated with the later change and the evidence used to review the consuming application.
Trace the field from response to report
Start with the code or configuration that reads the old name. Then follow what it produces: a dashboard badge, an inventory export, a purchasing filter or an alert. Fixing the parser alone does not demonstrate that every downstream report now represents the intended resource and location.
- List the consumers of the old field, including exports and scheduled inventory jobs.
- Separate image and load-balancer-type handling from server-type location handling.
- For each consumer, record the resource identifier and any location needed to interpret its result.
- Use controlled fixtures to inspect the parsed value and the final displayed or exported result.
- Record the reviewed application version and follow up on consumers whose behavior remains unverified.
Make the location distinction visible in a trial
Imagine a fictional inventory report with one row per server type. Its maintainer now needs to review location-specific metadata. A useful trial would select one server type, retain each location in the test record and inspect how the report presents the results. This is a proposed review method, not a claim about any particular Hetzner server type.
If the application collapses several locations into a single label, write down its aggregation rule and review that rule with the report’s owner. A missing legacy field should not silently become an unqualified “current” badge. Keep an unresolved parsing or interpretation question visible until it has a documented answer.
Keep the change record separate from account evidence
The changelog establishes the documented API change. Confirming a particular inventory tool requires evidence from that tool’s own response handling and output. No Hetzner account, live API request, SDK upgrade or deployment was tested for this guide, and no infrastructure was changed.