[legacy gov] Preparations for epoch 5 #4814
Workflow file for this run
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
| name: "Validate package-lock.json" | |
| on: [pull_request] | |
| jobs: | |
| check: | |
| runs-on: ubuntu-latest | |
| steps: | |
| - uses: actions/checkout@v3 | |
| - uses: actions/setup-node@v3 | |
| with: | |
| node-version: 16 | |
| # Step necessary for making sure that the developer correctly updated | |
| # dependencies using npm workspaces, e.g.: npm i -w packages/core-js some-dependency | |
| # More info: https://docs.npmjs.com/cli/v7/using-npm/workspaces | |
| - name: Check package-lock.json files are not present on packages/* | |
| run: bin/check-packages | |
| # The following steps are for checking the validity of the package-lock.json edits. | |
| # This will make sure that the file has not been tempered with, nor the developer | |
| # forgot to update it. | |
| - name: Check package-lock.json was correctly submmitted by the user | |
| run: | | |
| cp package-lock.json package-lock.original.json | |
| npm i --package-lock-only | |
| - uses: GuillaumeFalourd/diff-action@v1 | |
| with: | |
| first_file_path: package-lock.json | |
| second_file_path: package-lock.original.json | |
| expected_result: PASSED |