Skip to content
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.

CI-lons: Fix issue with package-lock and solc 0.5.17, try to ensure it doesn't happen again #567

Merged
merged 2 commits into from
Apr 7, 2020

Conversation

Shadowfiend
Copy link
Contributor

We were using npm install, which failed to catch an issue with the PR
that moved us to solc 0.5.17 (#565) where the lockfile had an incorrect
SHA hash for the new version (likely due to an aggressive find/replace on
my part). This PR both fixes the lockfile hash and moves the build to use
npm ci, which will solely reference the lockfile and blow up if things
aren't properly aligned.

Using npm install can, amongst other things, lead to misses when
dependencies update and the lockfile is not updated alongside, as with
the recent issue where the lockfile was incorrect for solc 0.5.17 and
didn't fail the PR build, but did fail the merge build.
@Shadowfiend Shadowfiend marked this pull request as ready for review April 7, 2020 16:55
Copy link
Contributor

@NicholasDotSol NicholasDotSol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's do it

@NicholasDotSol NicholasDotSol merged commit 818812b into master Apr 7, 2020
@NicholasDotSol NicholasDotSol deleted the ci-lons branch April 7, 2020 18:57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants