Hi 👋 — just a quick heads‑up.
I noticed this project appears to use AutoRest as part of its workflow. AutoRest has recently been deprecated, with retirement planned for July 1, 2026.
For context, I’m the engineering lead in charge of AutoRest, and we’re trying to proactively share this information with projects that may be impacted. This issue is purely informational, there’s no immediate action required.
📌 Deprecation details and background are tracked here:
Azure/autorest#5175
About next steps
Different projects may choose different paths. Some may continue using AutoRest even post retirement (everything will stay on NPM), or fork it as needed, while others may evaluate alternatives over time.
For additional context, at Microsoft we are personally replacing AutoRest with
TypeSpec for our own API description and code‑generation workflows. TypeSpec is a newer toolchain that can emit OpenAPI v2 and OpenAPI v3, which allows existing OpenAPI‑based workflows to continue after migration. Migrating typically involves rewriting OpenAPI v2 definitions into TypeSpec syntax.
That said, this is entirely optional, please feel free to ignore or close this issue if it’s not relevant to your setup.
Thank you, apologies for the noise if this doesn’t apply.
Hi 👋 — just a quick heads‑up.
I noticed this project appears to use AutoRest as part of its workflow. AutoRest has recently been deprecated, with retirement planned for July 1, 2026.
For context, I’m the engineering lead in charge of AutoRest, and we’re trying to proactively share this information with projects that may be impacted. This issue is purely informational, there’s no immediate action required.
📌 Deprecation details and background are tracked here:
Azure/autorest#5175
About next steps
Different projects may choose different paths. Some may continue using AutoRest even post retirement (everything will stay on NPM), or fork it as needed, while others may evaluate alternatives over time.
For additional context, at Microsoft we are personally replacing AutoRest with
TypeSpec for our own API description and code‑generation workflows. TypeSpec is a newer toolchain that can emit OpenAPI v2 and OpenAPI v3, which allows existing OpenAPI‑based workflows to continue after migration. Migrating typically involves rewriting OpenAPI v2 definitions into TypeSpec syntax.
That said, this is entirely optional, please feel free to ignore or close this issue if it’s not relevant to your setup.
Thank you, apologies for the noise if this doesn’t apply.