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

add inter-package version safety check #1265

Merged
merged 5 commits into from
Oct 25, 2022
Merged

add inter-package version safety check #1265

merged 5 commits into from
Oct 25, 2022

Conversation

ef4
Copy link
Contributor

@ef4 ef4 commented Oct 18, 2022

Now that our release process isn't all lockstep, it's easy to get this wrong, so I'm just preemptively adding a test for it.

Now that our release process isn't all lockstep, it's easy to get this wrong, so I'm just preempting adding a test for it.
Adopting code-equality-assertions so that we don't get burned by non-semantic changes in output formats.

In order to adopt it, I had to upgrade jest because jest brings its own resolver (sigh) that didn't understand newer node `exports` in package.json.

I had to use resolutions to deduplicate graceful-fs because jest pulled that in and it breaks support for `process.chdir` when there's more than one copy.
@ef4 ef4 merged commit bae39b7 into main Oct 25, 2022
@ef4 ef4 deleted the versions-check branch October 25, 2022 20:44
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.

1 participant