Conversation
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
….0.3' into rc-0.0.47
|
Beta version published on:
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: |
|
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? |
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
We don't know at the start if it will be patch, minor or major. So maybe use btw, A new commit added to #45 . Not sure it's completed though |
Yep!
Yeah, not sure. Let's keep exploring as we go and decide. Thanks!
Renaming the file? Yep, that was added here. Also added the eip712 curated extension in this PR. |
hmm, I don't see that commit and see this in files tree
nit: maybe name it tested #50, #51, -e |
Oh sorry, created this after Shiv pushed, but forgot to pull it first :D Thanks for adding it Shiv!
Yeah, this makes sense. |

Since we have a few things to merge, we thought it'd be nice to test a couple of things:
betapackage in npm.This PR includes #2 #3 #14 #45 #47 #50 #51