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

[v-next] First version of the new core #5196

Merged
merged 1 commit into from May 13, 2024
Merged

[v-next] First version of the new core #5196

merged 1 commit into from May 13, 2024

Conversation

alcuadrado
Copy link
Member

No description provided.

Copy link

vercel bot commented May 10, 2024

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

Name Status Preview Comments Updated (UTC)
hardhat ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 13, 2024 5:58pm

Copy link

changeset-bot bot commented May 10, 2024

⚠️ No Changeset found

Latest commit: 230478a

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

@alcuadrado
Copy link
Member Author

As discussed, I'm merging this without a review

@alcuadrado alcuadrado merged commit ba8e7fe into v-next May 13, 2024
25 checks passed
@alcuadrado alcuadrado deleted the v-next-core branch May 13, 2024 18:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:ready This issue is ready to be worked on
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

1 participant