Skip to content
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

fix: revert use of internal fast-stable-stringify in legacy library #2509

Merged
merged 1 commit into from
Apr 17, 2024

Conversation

lorisleiva
Copy link
Contributor

@lorisleiva lorisleiva commented Apr 17, 2024

Fix #2508

Copy link

changeset-bot bot commented Apr 17, 2024

⚠️ No Changeset found

Latest commit: 35cc050

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @lorisleiva and the rest of your teammates on Graphite Graphite

@lorisleiva lorisleiva marked this pull request as ready for review April 17, 2024 10:57
@lorisleiva lorisleiva merged commit 7d3adbb into master Apr 17, 2024
8 checks passed
@lorisleiva lorisleiva deleted the loris/fix-legacy-stringify branch April 17, 2024 11:01
Copy link
Contributor

🎉 This PR is included in version 1.91.6 🎉

The release is available on:

Your semantic-release bot 📦🚀

Copy link
Contributor

github-actions bot commented May 2, 2024

Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When I use yarn install libarry on github runer have a error
1 participant