build: fix staging release checks after auto-generating material-experimental package json
#24846
Conversation
This file contains hidden or 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
…erimental` package json We recently started auto-generating the material-experimental package.json file to avoid duplicating the MDC version/deps across multiple places. The staging checks assume a `package.json` file to be visible in the source files. For our checks it is sufficient to use the handwritten base package.json file.
devversion
added
merge safe
target: major
andrewseguin
approved these changes
Apr 28, 2022
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We recently started auto-generating the material-experimental
package.json file to avoid duplicating the MDC version/deps
across multiple places.
The staging checks assume a
package.jsonfile to be visible in thesource files. For our checks it is sufficient to use the handwritten
base package.json file.
Note: We do have actual generated
package.jsontests, but these testsare quick sanity checks that run before actually releasing (giving a quick
heads-up before doing too much unnecessary work)