Remove component API console deprecation warnings #7309
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Removes warnings for component API deprecations released in `5.17.0`.
jscheiny
previously approved these changes
Mar 4, 2025
jscheiny
approved these changes
Mar 4, 2025
Missed oneBuild artifact links for this commit: documentation | landing | table | demoThis is an automated comment from the deploy-preview CircleCI job. |
ggdouglas
added a commit
that referenced
this pull request
Mar 4, 2025
This reverts #7309 to reenable omponent API console deprecation warnings.
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Removes warnings for component API deprecations released in
5.17.0. The intention here is to temporarily disable and cut a release without the warnings. We will then follow up by re-enabling the deprecation warnings in a separate5.xpatch release. That way, consumers will be able to incrementally opt-in to these warnings by pinning to the release that does not include the console warnings.