Skip to content

Conversation

amysorto
Copy link
Contributor

Fixes #29577

@amysorto amysorto marked this pull request as ready for review August 29, 2024 16:22
@amysorto amysorto requested a review from a team as a code owner August 29, 2024 16:22
@amysorto amysorto requested review from mmalerba, wagnermaciel and andrewseguin and removed request for a team August 29, 2024 16:22
@amysorto amysorto force-pushed the color-role-mappings branch from 42cd0e5 to 40a2d35 Compare August 29, 2024 18:05
@amysorto amysorto added action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release labels Aug 29, 2024
@amysorto amysorto merged commit 4771931 into angular:main Aug 29, 2024
24 of 26 checks passed
amysorto added a commit that referenced this pull request Aug 29, 2024
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: material/core area: theming target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug(core-theming): get-theme-color($theme, $role-color) returns incorrect shades for 4 colors
2 participants