Skip to content

RC 0.0.47#53

Merged
technophile-04 merged 38 commits intomainfrom
rc-0.0.47
Jun 14, 2024
Merged

RC 0.0.47#53
technophile-04 merged 38 commits intomainfrom
rc-0.0.47

Conversation

@carletex
Copy link
Member

Since we have a few things to merge, we thought it'd be nice to test a couple of things:

  1. Use of release candidate branch (that we will merge to main) and we can test all the changes together
  2. Publishing a beta package in npm.

This PR includes #2 #3 #14 #45 #47 #50 #51

dependabot bot and others added 30 commits April 25, 2024 10:30
Bumps [semver](https://github.com/npm/node-semver) from 5.7.1 to 5.7.2.
- [Release notes](https://github.com/npm/node-semver/releases)
- [Changelog](https://github.com/npm/node-semver/blob/v5.7.2/CHANGELOG.md)
- [Commits](npm/node-semver@v5.7.1...v5.7.2)

---
updated-dependencies:
- dependency-name: semver
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [tar](https://github.com/isaacs/node-tar) from 6.1.13 to 6.2.1.
- [Release notes](https://github.com/isaacs/node-tar/releases)
- [Changelog](https://github.com/isaacs/node-tar/blob/main/CHANGELOG.md)
- [Commits](isaacs/node-tar@v6.1.13...v6.2.1)

---
updated-dependencies:
- dependency-name: tar
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [ip](https://github.com/indutny/node-ip) from 2.0.0 to 2.0.1.
- [Commits](indutny/node-ip@v2.0.0...v2.0.1)

---
updated-dependencies:
- dependency-name: ip
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [braces](https://github.com/micromatch/braces) from 3.0.2 to 3.0.3.
- [Changelog](https://github.com/micromatch/braces/blob/master/CHANGELOG.md)
- [Commits](micromatch/braces@3.0.2...3.0.3)

---
updated-dependencies:
- dependency-name: braces
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
removed by running following command:

yarn remove husky && git config --unset core.hooksPath
@carletex
Copy link
Member Author

Beta version published on:

npx create-eth@0.0.47-beta.1

More info about pre-releases here: https://github.com/changesets/changesets/blob/main/docs/prereleases.md (we should all of this stuff on #6) . Also add the more verbose option to use npx: npm create eth@<version> (the space between create and eth should be there, not a typo.)

@carletex
Copy link
Member Author

Thinking about merging vs squash and merging here (with this release branch model).

I think if squash and merge, the existing PRs won't close (but they history will be clean). If we just merge, the PRs will close... but the git history 😓

But then...I'm thinking that if we are using this system, we should be merging always against a release branch, not main.... so we shouldn't have this problem, right?

So maybe test this, squash & merge... and close the PRs manually?

@rin-st
Copy link
Member

rin-st commented Jun 14, 2024

If we just merge, the PRs will close...

Not sure I understand how it works. Why they will close? Because all the commits will already be on main? If yes, everything else seems reasonable. Only one question

But then...I'm thinking that if we are using this system, we should be merging always against a release branch, not main.... so we shouldn't have this problem, right?

We don't know at the start if it will be patch, minor or major. So maybe use dev branch? Merge to dev and then torc branches from dev when ready? After it squash rc to main.

btw, A new commit added to #45 . Not sure it's completed though

@carletex
Copy link
Member Author

Why they will close? Because all the commits will already be on main?

Yep!

We don't know at the start if it will be patch, minor or major. So maybe use dev branch? Merge to dev and then torc branches from dev when ready? After it squash rc to main.

Yeah, not sure. Let's keep exploring as we go and decide. Thanks!

btw, A new commit added to #45 . Not sure it's completed though

Renaming the file? Yep, that was added here.


Also added the eip712 curated extension in this PR.

@rin-st
Copy link
Member

rin-st commented Jun 14, 2024

Renaming the file? Yep, that was added here.

hmm, I don't see that commit and see this in files tree

image

Also added the eip712 curated extension in this PR.

nit: maybe name it eip-712 instead of eip712? So it will be consistent with branch name on extensions and with naming here?


tested #50, #51, -e eip712 and also #45 and everything works well for me

@carletex
Copy link
Member Author

hmm, I don't see that commit and see this in files tree

Oh sorry, created this after Shiv pushed, but forgot to pull it first :D Thanks for adding it Shiv!

nit: maybe name it eip-712 instead of eip712? So it will be consistent with branch name on extensions and with naming here?

Yeah, this makes sense.

Copy link
Collaborator

@technophile-04 technophile-04 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested nicely and everything works nicely !! also all the extensions, also tried out :

 npx create-eth@0.0.47-beta.1 -e technophile-04/eip-5792:foundry

works nicely ! Thanks all !!

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.

3 participants