Closed arthurgousset closed 7 months ago
Latest commit: 6a5181680e273333a494cc7519b12518539e345f
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.
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
rainbowkit-with-celo | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Apr 24, 2024 9:32am |
Blocked by
Once all wallets are in the upstream repo and a simple migration guide exists, I'll update the README in this PR and merge it.
Maybe I should take the README commit out of this PR, so it can be merged and open a draft README PR for when we are ready to move forward with deprecating the package.
Maybe I should take the README commit out of this PR, so it can be merged and open a draft README PR for when we are ready to move forward with deprecating the package.
That's done ✅ I moved the incomplete disclaimer (in the README.md
file) that this package might be deprecated in the into a separate PR:
That should allow these changes to be merged without being blocked by the deprecation process.
Description
celo-org/developer-tooling
CONTRIBUTING.md
fileOther changes
None
Tested
Only docs changes.
Related issues
Backwards compatibility
Yes
Documentation
Yes