Skip to content

refactor(multiple): deprecate exposed ripples #26914

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 12, 2023

Conversation

wagnermaciel
Copy link
Contributor

No description provided.

@wagnermaciel wagnermaciel marked this pull request as ready for review April 12, 2023 15:49
@wagnermaciel wagnermaciel added target: patch This PR is targeted for the next patch release action: merge The PR is ready for merge by the caretaker target: rc This PR is targeted for the next release-candidate and removed target: patch This PR is targeted for the next patch release labels Apr 12, 2023
@angular-robot angular-robot bot merged commit 708c971 into angular:main Apr 12, 2023
angular-robot bot pushed a commit that referenced this pull request Apr 12, 2023
* refactor(multiple): deprecate exposed ripples

* fixup! refactor(multiple): deprecate exposed ripples

(cherry picked from commit 708c971)
@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 Jun 6, 2023
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 target: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants