Add npm registry proxy in CI to test publication/installation #3157
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cgewecke
changed the title
nivida
approved these changes
Oct 30, 2019
This was referenced Oct 31, 2019
Merged
|
This is great @cgewecke 😍 |
This was referenced Feb 16, 2023
This was referenced Feb 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(Continuation of #3098)
Adds the ability to publish the monorepo to an ephemeral virtual registry in CI and install Web3's latest state in an arbitrary target project. This lets us run other projects' unit tests to verify that no breaking changes have been introduced.
Includes:
One thing to note about this is that it doesn't work very well when the target requires that installation be done with yarn. (Getting Truffle to work with this format was a little challenging.)
Truffle's tests are run as an "allowed failure" and CI will turn green without waiting for them to finish. This is done because these tests are mostly a pre-publication sanity check which might help us track breaking changes down to a specific PR if they occur.