chore: bump @fluentui/react-icons to ^2.0.301 to surface new icons on the docsite #34436
Conversation
This file contains hidden or 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
📊 Bundle size report
Unchanged fixtures
|
|
Pull request demo site: URL |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
TristanWatanabe
force-pushed
the
tristan/bump-react-icons-to-2.0.300
branch
from
067c923 to
c39f7e7
Compare
TristanWatanabe
changed the title
ValentinaKozlova
approved these changes
May 23, 2025
tudorpopams
approved these changes
May 27, 2025
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.
Changes
@fluentui/react-iconsto latest version^2.0.301to consume latest icon additions from package. This will allow the new icons to be surfaced in our docsite.Note: The
@fluentui/react-iconsdependency in the v9 packages has been deliberately left unchanged to avoid introducing unnecessary version churn to consumers, as the current version (2.0.245) satisfies all functional requirements and there is no immediate benefit or need to upgrading.