diff --git a/CHANGELOG.md b/CHANGELOG.md
index 6e7e22853525..c64263073aaf 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,35 @@
+
+# 18.1.0-next.2 "ivory-infinity" (2024-06-12)
+### cdk
+| Commit | Type | Description |
+| -- | -- | -- |
+| [0bc6583892](https://github.com/angular/components/commit/0bc65838926e88723bfc677fc3e4de81826cfe5b) | feat | **drag-drop:** add mixed orientation support |
+### material
+| Commit | Type | Description |
+| -- | -- | -- |
+| [6f698fa4e2](https://github.com/angular/components/commit/6f698fa4e24ef4637b2c83f43cb608df967a78b5) | feat | **core:** add option to configure prefix of system variables ([#29139](https://github.com/angular/components/pull/29139)) |
+| [e7312037f7](https://github.com/angular/components/commit/e7312037f75dad5482b06868542ec2a715c116fc) | fix | **dialog:** Make autofocus work with animations disabled ([#29195](https://github.com/angular/components/pull/29195)) |
+| [3b32d0e7c9](https://github.com/angular/components/commit/3b32d0e7c95b358d30f8b7e6b0570ab8ba815a06) | fix | **dialog:** Make focus behavior consistent across zoneful/zoneless apps ([#29192](https://github.com/angular/components/pull/29192)) |
+| [566057b8f5](https://github.com/angular/components/commit/566057b8f58fab1b5328cbd4336b7b19ea412fd3) | fix | **divider:** non-text color contrast issues ([#28995](https://github.com/angular/components/pull/28995)) |
+| [e3abc65d7d](https://github.com/angular/components/commit/e3abc65d7d191f2adf1c294bdb84f532d4eac05c) | fix | **radio:** mark radio-group for check on touch ([#29203](https://github.com/angular/components/pull/29203)) |
+| [3da43230e6](https://github.com/angular/components/commit/3da43230e62c8983af5c21c4c1fc66ea2e5e7d52) | fix | **schematics:** estimate missing hues in M3 schematic ([#29231](https://github.com/angular/components/pull/29231)) |
+| [d717de5150](https://github.com/angular/components/commit/d717de51501e04a0410217c07fc31929ff2e983a) | fix | **snack-bar:** fix overrides mixin name typo ([#29180](https://github.com/angular/components/pull/29180)) |
+
+
+
+
+# 18.0.3 "gossamer-glacier" (2024-06-12)
+### material
+| Commit | Type | Description |
+| -- | -- | -- |
+| [f6b993fdb7](https://github.com/angular/components/commit/f6b993fdb7fbdcfbe0297d320a5961097002308d) | fix | **dialog:** Make autofocus work with animations disabled ([#29195](https://github.com/angular/components/pull/29195)) |
+| [6dd1689b51](https://github.com/angular/components/commit/6dd1689b519abf287098d30f7698fc37197e3db0) | fix | **dialog:** Make focus behavior consistent across zoneful/zoneless apps ([#29192](https://github.com/angular/components/pull/29192)) |
+| [81d4527f91](https://github.com/angular/components/commit/81d4527f9130605f69dea31a092a60261bde25db) | fix | **radio:** mark radio-group for check on touch ([#29203](https://github.com/angular/components/pull/29203)) |
+| [0f4d1862d3](https://github.com/angular/components/commit/0f4d1862d30366978176a4a87b7799915d3caedd) | fix | **schematics:** estimate missing hues in M3 schematic ([#29231](https://github.com/angular/components/pull/29231)) |
+| [faf348438d](https://github.com/angular/components/commit/faf348438d57db80e8ac5187ffe3900fe398fe77) | fix | **snack-bar:** fix overrides mixin name typo ([#29180](https://github.com/angular/components/pull/29180)) |
+
+
+
# 18.1.0-next.1 "velvet-violoncello" (2024-06-05)
### cdk
diff --git a/guides/getting-started.md b/guides/getting-started.md
index e22bd13a45c4..642cb730f1bb 100644
--- a/guides/getting-started.md
+++ b/guides/getting-started.md
@@ -28,7 +28,7 @@ determine which features to include:
1. Choose a prebuilt theme name, or "custom" for a custom theme:
- You can choose from [prebuilt material design themes](https://material.angular.io/guide/theming#using-a-pre-built-theme) or set up an extensible [custom theme](https://material.angular.io/guide/theming#defining-a-theme).
+ You can choose from [prebuilt material design themes](https://material.angular.io/guide/theming#pre-built-themes) or set up an extensible [custom theme](https://material.angular.io/guide/theming#defining-a-theme).
2. Set up global Angular Material typography styles:
diff --git a/guides/schematics.md b/guides/schematics.md
index ab1b2cd44715..b12ddbd60a84 100644
--- a/guides/schematics.md
+++ b/guides/schematics.md
@@ -26,7 +26,7 @@ The Angular Material `ng add` schematic helps you set up an Angular CLI project
- Ensure [project dependencies](./getting-started#step-1-install-angular-material-angular-cdk-and-angular-animations) are placed in `package.json`
- Enable the [BrowserAnimationsModule](./getting-started#step-2-configure-animations) in your app module
-- Add either a [prebuilt theme](./theming#using-a-pre-built-theme) or a [custom theme](./theming#defining-a-custom-theme)
+- Add either a [prebuilt theme](./theming#pre-built-themes) or a [custom theme](./theming#defining-a-custom-theme)
- Add Roboto fonts to your `index.html`
- Add the [Material Icon font](./getting-started#step-6-optional-add-material-icons) to your `index.html`
- Add global styles to
diff --git a/guides/theming.md b/guides/theming.md
index bd204dfb19f6..633edf3d268f 100644
--- a/guides/theming.md
+++ b/guides/theming.md
@@ -91,8 +91,28 @@ more about these terms):
##### Pre-built themes
-There are a number of color palettes available in `@angular/material` that can be
-used with the `primary` and `tertiary` options:
+Angular Material includes several pre-built theme CSS files, each with different palettes selected.
+You can use one of these pre-built themes if you don't want to define a custom theme with Sass.
+
+| Theme | Light or dark? | Specification |
+|------------------------|----------------|----------------------------------|
+| `azure-blue.css` | Light | Material Design 3 |
+| `rose-red.css` | Light | Material Design 3 |
+| `cyan-orange.css` | Dark | Material Design 3 |
+| `magenta-violet.css` | Dark | Material Design 3 |
+| `deeppurple-amber.css` | Light | Material Design 2 |
+| `indigo-pink.css` | Light | Material Design 2 |
+| `pink-bluegrey.css` | Dark | Material Design 2 |
+| `purple-green.css` | Dark | Material Design 2 |
+
+These files include the CSS for every component in the library. To include only the CSS for a subset
+of components, you must use the Sass API detailed in [Defining a theme](#defining-a-theme) above.
+You can [reference the source code for these pre-built themes](https://github.com/angular/components/blob/main/src/material/core/theming/prebuilt) to see examples of complete theme definitions.
+
+##### Pre-defined palettes
+
+The pre-built themes are based on a set of pre-defined palettes that can be used with the `primary`
+and `tertiary` options:
- `$red-palette`
- `$green-palette`
diff --git a/guides/v15-mdc-migration.md b/guides/v15-mdc-migration.md
deleted file mode 100644
index 5f4663b1f151..000000000000
--- a/guides/v15-mdc-migration.md
+++ /dev/null
@@ -1,683 +0,0 @@
-# Migrating to MDC-based Angular Material Components
-
-In Angular Material v15 and later, many of the components have been refactored to be based on the official
-[Material Design Components for Web (MDC)](https://github.com/material-components/material-components-web).
-The components from the following imports have been refactored:
-
-| Import path | Summary of changes |
-|------------------------------------|------------------------------------------------------|
-| @angular/material/autocomplete | Style changes only |
-| @angular/material/button | Style changes, API changes |
-| @angular/material/card | Style changes only |
-| @angular/material/checkbox | Style changes, changes to event behavior |
-| @angular/material/chips | Complete rewrite |
-| @angular/material/core | Style changes only |
-| @angular/material/dialog | Style changes, changes to change detection behavior |
-| @angular/material/form-field | Style changes, some appearances removed, API changes |
-| @angular/material/input | Style changes only |
-| @angular/material/list | Style changes, API changes |
-| @angular/material/menu | Style changes, API changes |
-| @angular/material/paginator | Style changes only |
-| @angular/material/progress-bar | Style changes only |
-| @angular/material/progress-spinner | Style changes only |
-| @angular/material/radio | Style changes only |
-| @angular/material/select | Style changes only |
-| @angular/material/slide-toggle | Style changes only |
-| @angular/material/slider | Complete rewrite |
-| @angular/material/snack-bar | Style changes, API changes |
-| @angular/material/table | Style changes only |
-| @angular/material/tabs | Style changes, API changes |
-| @angular/material/tooltip | Style changes only |
-
-The refactored components offer several benefits over the old implementations, including:
-* Improved accessibility
-* Better adherence to the Material Design spec
-* Faster adoption of future versions of the Material Design spec, due to being based on common
- infrastructure
-
-## What has changed?
-
-The new components have different internal DOM and CSS styles. However, most of the TypeScript APIs
-and component/directive selectors for the new components have been kept as close as possible to the
-old implementation. This makes it straightforward to migrate your application and get it running
-with the new components.
-
-Due to the new DOM and CSS, you will likely find that some styles in your application need to be
-adjusted, particularly if your CSS is overriding styles on internal elements on any of the migrated
-components.
-
-There are a few components with larger changes to their APIs that were necessary in order to
-integrate with MDC. These components include:
-* form-field
-* chips
-* slider
-* list
-
-See below for a [comprehensive list of changes](#comprehensive-list-of-changes) for all components.
-
-The old implementation of each new component is now deprecated, but still available from a "legacy"
-import. For example, you can import the old `mat-button` implementation can be used by importing the
-legacy button module.
-
-```ts
-import {MatLegacyButtonModule} from '@angular/material/legacy-button';
-```
-
-## How to Migrate
-
-You can start your migration by running Angular Material's automated refactoring tool. This tool,
-implemented as an [Angular Schematic](https://angular.io/guide/schematics), updates the majority
-your code to the new component versions. While some follow-up is necessary, you can reduce the
-manual effort by following these best practices:
-
-You can reduce the amount of manual effort needed by ensuring that your application follows good
-practices before migrating.
-* Avoid overriding styles on internal Angular Material elements in your CSS as much as possible. If
- you find yourself frequently overriding styles on internal elements, consider using a component
- that is designed for more style customization, such as the ones available in the
- [Angular CDK](/cdk).
-* Use [component harnesses](/guide/using-component-harnesses) to interact with Angular Material
- components in tests rather than inspecting internal elements, properties, or methods of the
- component. Using component harnesses makes your tests easier to understand and more robust to
- changes in Angular Material
-
-### 1. Update to Angular Material v16
-
-Angular Material includes a schematic to help migrate applications to use the new MDC-based
-components. To get started, upgrade your application to Angular Material 16.
-
-```shell
-ng update @angular/material@16
-```
-
-As part of this update, a schematic will run to automatically move your application to use the
-"legacy" imports containing the old component implementations. This provides a quick path to getting
-your application running on v16 with minimal manual changes.
-
-### 2. Run the migration tool
-
-After upgrading to v16, you can run the migration tool to switch from the legacy component
-implementations to the new MDC-based ones.
-
-```shell
-ng generate @angular/material:mdc-migration
-```
-
-This command updates your TypeScript, styles, and templates to the new implementations, updating as
-much as it can automatically.
-
-#### Running a Partial Migration
-
-Depending on the size and complexity of your application, you may want to migrate a single component
-or small group of components at a time, rather than all components at once.
-
-You may also want to migrate your app one module at a time instead of all together. You can use both
-the old implementation and new implementation in the same application, as long as they aren't used
-in the same `NgModule`.
-
-The script will prompt you for the directory and components you want to migrate.
-
-### 3. Check for TODOs left by the migration tool.
-
-In situations where the migration tool is not able to automatically update your code, it will
-attempt to add comments for a human to follow up. These TODO comments follow a common format, so
-they can be easily identified.
-
-```ts
-// TODO(mdc-migration): ...
-```
-
-To search for all comments left by the migration tool, search for `TODO(mdc-migration):` in your
-IDE.
-
-### 4. Verify Your Application
-
-After running the migration and addressing the TODOs, manually verify that everything is working
-correctly.
-
-Run your tests and confirm that they pass. It's possible that your tests depended on internal DOM or
-async timing details of the old component implementations and may need to be updated. If you find
-you need to update some tests, consider using [component harnesses](./using-component-harnesses) to
-make the tests more robust.
-
-Run your application and verify that the new components look right. Due to the changes in internal
-DOM and CSS of the components, you may need to tweak some of your application's styles.
-
-## Comprehensive List of Changes
-
-### Library-wide Changes
-
-* Component size, color, spacing, shadows, and animations all change slightly across the board.
- These changes generally improve spec-compliance and accessibility.
-
-* The DOM structure for all components has changed to improve accessibility and better follow the
- Material Design spec.
-
-* CSS classes applied to components use the `mat-mdc-` prefix, whereas before it was simply a `mat-`
- prefix. Elements that roughly correspond to element in the old implementation have been given the
- same class name (aside from the prefix). For example, the button’s host class is `mat-mdc-button`
- instead of `mat-button`. However, not all elements in the previous implementation have an
- equivalent element in the new implementation.
-
-* The styles associated with the `mat-typography` class are no longer generated automatically. You
- have to include them using the `mat.typography-hierarchy` mixin.
-
-### Theming
-
-* Default typography levels defined by `mat.define-typography-config` have been updated to reflect
- changes to the Material Design spec.
-
-* All components now have themeable density. Styles for the default density level (0) will be
- included by default when you include a theme mixin.
-
- ```scss
- @use '@angular/material' as mat;
-
- $theme: mat.define-light-theme((
- color: ...
- ));
-
- // Adds density level 0 styles
- @include mat.all-component-themes($theme);
- ```
-
- If you prefer a different default density level, you can set it in your theme config:
-
-
- ```scss
- $theme: mat.define-light-theme((
- color: ...,
- density: -1
- ));
- ```
-
-### Autocomplete
-
-* Long options now wrap instead of truncating.
-
-* Option heights are no longer capped at `48px`.
-
-* Option list now has an `8px` top and bottom padding.
-
-* Options list now has an animation when opening and closing.
-
-### Button
-
-* Icon button height and width are `48px` instead of `40px`.
-
-* State colors (hover, focus, active) are slightly different to improve text contrast ratios.
-
-* Letter-spacing is `1.25px` instead of `normal`.
-
-* FAB supports text with the `extended` input attribute.
-
-* Theming mixins are split into three separate mixins:
- - Normal button (default, raised, stroked, flat): `mat.mdc-button-theme`
- - Icon button: `mat.mdc-icon-button-theme`
- - FAB: `mat.mdc-fab-theme`
-
-* Icons in the button content are placed before the button text. Add the `iconPositionEnd` attribute to place them after the button text.
-
-* Icons in the button content inherit the text `font-size`. Buttons with only icons and no text do
- not align properly (this does not apply to the icon-button).
-
-### Card
-
-* By default, mat-card does not apply any internal padding. Instead, this padding is defined on the
- card content areas: ``, ``, and ``.
-
-* `` no longer sets any typography styles, users are free to add whatever
- typography styles make sense for their application, either to `` itself or any
- child elements as appropriate. For example:
-
- ```scss
- @use '@angular/material' as mat;
- @include mat.typography-hierarchy();
- ```
-
- ```html
-
- ...
-
- ```
-
-### Checkbox
-
-* Clicks on the checkbox now trigger directly on the native checkbox element rather than a shim div.
- Native checkboxes have bizarre behavior when calling `preventDefault` on their `click` event, so
- users should not call `preventDefault` on `click`.
-
-* Checkbox touch targets are larger, now 40px instead of 16px, which is more accessible. Be sure to
- allow enough space in your layout so that the touch target does not overlap other components. If
- you are not concerned with accessibility you can match the previous size by using density -1 for
- the checkbox.
-
- ```scss
- @use '@angular/material' as mat;
- @include mat.checkbox-density(-1);
- ```
-
-* Checkbox color may be changed to white or black due to a change in heuristics based on the
- application’s theme. Previously, the check’s color would be set to the theme’s background color.
- With MDC, it is determined by whether white or black has the most contrast against the primary
- color.
-
-* Focus state is slightly darker, improving contrast ratio.
-
-* Text styles are not inherited; you will need to specifically target the checkbox’s `label` to
- override typography properties.
-
-* After toggling a checkbox with the mouse, the ripple will remain visible instead of animating out.
-
-### Chips
-
-* Chips used to be directives, but they're now components. This means that they can't be applied to
- other components anymore.
-* The chips component has been split into multiple variants corresponding with more appropriate
- interaction patterns for accessibility. The original `mat-chip-list` used `role="listbox"`, but
- this interaction pattern is not suited for all use-cases. The new chips have:
-
- * `` with `` - this is the closest to the previous interaction
- pattern. This is the only variant that supports selection state for chips. This pattern aligns
- with the filter chips pattern specified in the Material Design spec. This pattern should be used
- when you want the user to select one or more values from a list of options.
-
- * `` with `` - this pattern should be used for any text input + chips
- interaction.
-
- * `` with `` - this variant has no accessibility pattern and assumes one
- will be applied at the application level. This allows the application to implement a custom
- accessibility pattern with the chips visuals.
-
-* The migration tool always changes the legacy `` to `` to minimize
- differences before and after. You should separately consider changing to `` or
- `` on a case-by-case basis. See [Chips Interaction Patterns](
- /components/chips/overview#interaction-patterns) for more guidence on
- choosing the appropriate component for your use case.
-
-### Dialog
-
-* The `.mat-dialog-container` does not contain a 24px padding anymore. Instead, the inner dialog
- directives are responsible for adding the right padding. This will be apparent if your dialog does
- not use any of the directives like ``.
-
-* `mat-dialog-content` uses the font-settings specified by the Material Design spec, which includes
- a rather roomy line-height. If you have an information-dense dialog that doesn't look good with
- these settings, you can avoid using `` and just use a div with custom padding,
- or use custom typography settings that can be applied with the `mat.mdc-dialog-typography` mixin.
-
-* The old dialog triggered an extra change detection, which may have masked change detection issues
- in your application that need to be fixed when migrating.
-
-### Form Field
-
-* The "legacy" and "standard" form-field appearance settings no longer exist, as these have been
- dropped from the Material Design spec.
-
-* The removed "legacy" appearance promoted input placeholders to the floating label if the label was
- not specified. All newer appearance settings require explicitly specifying a `` if one
- was not provided before. This change addresses an accessibility best practice of not using labels
- and placeholders interchangeably.
-
-* By default, MatFormField still reserves exactly one line of space below the field for hint or
- error text. However, there is a new option `@Input() subscriptSizing: 'fixed'|'dynamic'`. When
- this setting is set to `fixed` (default), the form-field reserves enough space in the layout to
- show one line of hint or error text. When set to `dynamic`, the form-field expands and contracts
- the amount of space it takes in the layout to fit the error / hint that is currently shown.
-
-* The text inside `` is larger and darker in order to meet W3C text guidelines.
-
-* While the previous form-field had a single directive for prefixes (`matPrefix`) and a single
- directive for suffixes (`matSuffix`), the MDC-based form-field distinguishes between text
- prefix/suffixes which are baseline aligned with the input text, and icon prefix/suffixes which are
- center aligned in the form-field. Use `matTextPrefix` or `matTextSuffix` to indicate a text
- prefix/suffix, and `matIconPrefix` or `matIconSuffix` to indicate an icon prefix/suffix. The old
- `matSuffix` and `matPrefix` APIs will behave like icons, though they are now deprecated.
-
-* The `floatLabel` input no longer accepts `'never'`. `floatLabel="never"` was only supported by the
- legacy form-field appearance which has been dropped. It was used to achieve a floating label that
- behaved like a placeholder. If you need this behavior, use the `placeholder` property on ``
- instead.
-
-* Custom form field controls may need their styles adjusted to account for the fact that the
- surrounding form field DOM and styles have changed.
-
-### Input
-
-* MatInput must be inside ``. Previously it was (unintentionally) possible to use an
- `` without the form field if the page loaded form field styles elsewhere.
-
-* The MDC-based MatInput hides the native calendar picker indicator associated with
- ``, if you want this indicator to appear for your inputs, use the
- following styles:
-
- ```scss
- input.mat-mdc-input-element::-webkit-calendar-picker-indicator {
- display: block;
- }
- ```
-
-### List
-
-* The API has been reworked to support text wrapping and better integration with the Material Design
- specification.
-
-* Previously, list items were commonly created using multiple `span` elements with the `matLine`
- directive applied. Each `span` resulting in a line, and the first one becoming the primary line.
- With the new API, the `matLine` directive has been split into two more granular and meaningful
- directives:
- * `matListItemTitle`
- * `matListItemLine`
-
-* Text outside of a `matListItemLine` (so-called "unscoped content") will result in an additional
- line being acquired (as if the content was put into a line).
-
- ```html
-
- Title
- Second line
-
- ```
-
-* The list automatically infers the number of lines of text content. For example, in the snippet
- above, the list item renders space for two lines. With the new API, you can set an explicit number
- of lines on the `` to manually control wrapping.
-
- ```html
-
- Title
- This text will wrap into the third line. Space for three lines is acquired by the
- list item.
-
- ```
-
- Note that text inside a `matListItemTitle` or `matListItemLine` will never wrap. Only unscoped
- content will wrap/take up the remaining space based on explicit number of lines provided.
-
-* Aside from the differences in how lines are composed, some other directives have been renamed to
- use more explicit naming:
- * `matListIcon` is now `matListItemIcon`
- * `matListAvatar` is now `matListItemAvatar`
-
-* Lastly, also a new directive (`matListItemMeta`) is available to put content into the meta section
- of a list item (usually the end of the list item). Previously unscoped content in a list item was
- put into the meta section.
-
-* Recommended migration steps for common use of a list item:
- 1. Change the first `matLine` to `matListItemTitle`
- 2. Change all other `matLine`'s to `matListItemLine`
- 3. Change all `matListIcon` to `matListItemIcon`
- 4. Change all `matListAvatar` to `matListItemAvatar`
- 5. Wrap all unscoped content (content outside a `matLine`) in a `matListItemMeta` container.
-
-### Menu
-
-* The icon for a menu item appears before the text, regardless of the order in the DOM.
-
- * If you have a piece of content such as an `` that you want to use in place of a
- `` use `ngProjectAs="mat-icon"` to project it into the icon slot.
-
- * If you need your icon to appear at the end of the item (not officially supported by the spec)
- you can wrap both the text and your icon in a span, for example:
-
- ```html
-
- Text
- end_icon
-
- ```
-
-* The text in menu items wraps instead of being hidden with an ellipses.
-
-* Menu item heights are no longer capped at `48px`.
-
-* Menu elevation starts from level 8, instead of level 4.
-
-### Option / Optgroup
-
-* Long options now wrap instead of truncating with an ellipsis.
-
-* Option heights are no longer capped at `48px`.
-
-### Paginator
-
-* The form-field inside of `mat-paginator` only supports the `appearance` options offered by the new
- form-field (`fill` and `outline`).
-
-### Progress Bar
-
-* Visibility on internal elements is now set to `visible`. Setting `visibility: hidden` will no
- longer hide all internal elements. Instead, style it with `opacity: 0`, `display: none`, or
- remove it completely with `ngIf`.
-
-* Height is always set to 4px and does not get shorter or taller using `height` styles.
-
-### Progress Spinner
-
-* Host element is no longer `display: block` which may affect layout. To fix layout issues add
- `display: block` back to the element.
-
-### Radio
-
-* Radio button labels are no longer `width: 100%`. This helps prevent users from accidentally
- selecting a radio when clicking on whitespace that appears inert on the page.
-
-* Labels are smaller and further away from the radio button to align with the Material Design spec.
-
-* The touch target is now much larger and more accessible. Be sure to allow enough space in your
- layout so that the touch target does not overlap other components. If you are not concerned with
- accessibility you can match the previous size by using density -1 for the radio.
-
- ```scss
- @use '@angular/material' as mat;
- @include mat.radio-density(-1);
- ```
-
-### Select
-
-* `MatSelect` no longer aligns the selected option in the dropdown menu with the trigger text.
-
-* Long options now wrap instead of truncating.
-
-* Option heights are no longer capped at `48px`.
-
-* Option list now has an `8px` top and bottom padding.
-
-* Option list animation has changed.
-
-* Previously the dropdown menu width could be wider than the parent form-field, but now the dropdown
- is the same width as the form-field
-
-### Slide Toggle
-
-* To improve accessibility, the MDC-based version uses `