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

feat: [sc-25981] Fix endpoint for NameRank #514

Closed

Conversation

BanaSeba
Copy link
Collaborator

Copy link

changeset-bot bot commented Dec 30, 2024

⚠️ No Changeset found

Latest commit: f483cdd

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

vercel bot commented Dec 30, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
namekit.io ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 30, 2024 6:28pm
namerank.io ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 30, 2024 6:28pm
5 Skipped Deployments
Name Status Preview Comments Updated (UTC)
examples.nameguard.io ⬜️ Skipped (Inspect) Dec 30, 2024 6:28pm
namegraph.dev ⬜️ Skipped (Inspect) Dec 30, 2024 6:28pm
nameguard.io ⬜️ Skipped (Inspect) Dec 30, 2024 6:28pm
namehashlabs.org ⬜️ Skipped (Inspect) Dec 30, 2024 6:28pm
storybook.namekit.io ⬜️ Skipped (Inspect) Dec 30, 2024 6:28pm

@lightwalker-eth
Copy link
Member

@BanaSeba Thanks for this update 👍 I see @notrab submitted a fix for this too in #520 (review) I'll close this PR for us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants