fix: broken package-lock.json #531
Conversation
smoya
requested review from
fmvilas,
magicmatatjahu,
jonaslagoni,
derberg and
asyncapi-bot-eve
as code owners
|
Kudos, SonarCloud Quality Gate passed!
|
There was a problem hiding this comment.
This can happen indeed when there is no branch protection ensuring the jobs must go through. Same with at least one review, i.e. I could merge this one right now, and so can you by using /rtm as it does not require anything.
Going forward with next-spec and next-major-spec this will be avoided as we no longer create branches as we go and no need to keep updating branch protection rules.
@derberg I dont have permission to change the branch protection, so you would need to do it, or give me permissions 😄
|
/rtm |
|
🎉 This PR is included in version 1.15.0-2022-04-release.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
A malformed
package-lock.jsonfile has been merged on https:/asyncapi/parser-js/pull/476/files#diff-053150b640a7ce75eff69d1a22cae7f0f94ad64ce9a855db544dda0929316519R63.We didn't realize it until it was merged. See https:/asyncapi/parser-js/runs/6110565450?check_suite_focus=true
I think the whole set of github actions didn't run on the PR, maybe due to the fact it was the first time the author made a PR (and owner had to approve, but didn't happen).
Anyway, this PR is fixing it.