---
title: March 2023
---

# Release Notes March 2023 (2023-03-13)

:::danger
This release contains **breaking changes**
:::

See TypeSpec Core [release notes](https://typespec.io/docs/release-notes/release-2023-03-13)

See [Cadl to TypeSpec rename and migration FAQ](./cadl-typespec-migration.md)

## New Features

### typespec-azure-core

- Added `getLroMetadata` helper for resolving LROs in client generation code
- Added documentation of semantic models for LROs
- Fixed issues with OperationStatus templates

### typespec-azure-resource-manager

- Update operation templates to conform with new ARM RPC requirements

### typespec-client-generator-core

- Export embedded models in Array/List/Model for `getAllModels`.
- fix getAllModels when there are no models

## Breaking Changes

### Package Renaming (Cadl -> TypeSpec)

Packages now use `typespec` instead of `cadl` in package names.

| Old Package Name                         | New Package Name                             |
| ---------------------------------------- | -------------------------------------------- |
| @azure-tools/cadl-autorest               | @azure-tools/typespec-autorest               |
| @azure-tools/cadl-azure-core             | @azure-tools/typespec-azure-core             |
| @azure-tools/cadl-azure-resource-manager | @azure-tools/typespec-azure-resource-manager |
| @azure-tools/cadl-DPG                    | @azure-tools/typespec-client-generator-core  |
| @azure-tools/cadl-diff                   | @azure-tools/typespec-diff                   |

The `migrate` package can be used to migrate specs to using the new package imports and namespaces.
For more information about migrating to new TypeSpec packages, see the [note on Cadl to TypeScript Migration](https://azure.github.io/typespec-azure/docs/next/release-notes/cadl-typespec-migration).
