Proper release of json-schema-ref-parser

[lzgrzebski]

@apidevtools/json-schema-ref-parser@https://github.com/bcherny/json-schema-ref-parser.git#commit=984282d34a2993e5243aa35100fe32a63699164d: The remote archive doesn't match the expected checksum

Should we fork and release the version with proper version + tag instead of pointing to arbitrary refs?

[Kiran554]

This is not ideal. As it creates reference to github which might not be reachable for internal repositories. Please release another version to fix this.

[bradenneufeld]

+1, This is breaking our CodeBuild pipeline.

[Container] 2022/08/03 05:01:18 Running command npm ci
npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t ssh:https://[email protected]/bcherny/json-schema-ref-parser.git
npm ERR! 
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR! 
npm ERR! exited with error code: 128

[Quentigus]

+1, I can't use recent releases because of this reference :(

npm ERR! Error while executing:
npm ERR! git ls-remote -h -t https://github.com/bcherny/json-schema-ref-parser.git
npm ERR!
npm ERR! fatal: unable to access 'https://github.com/bcherny/json-schema-ref-parser.git/': Failed to connect to github.com port 443: Timed out
npm ERR!
npm ERR! exited with error code: 128

[bradenneufeld]

After reviewing npm/cli#2610, I was able to resolve in our CI/CD pipeline (AWS Codebuild) by updating our projects to use the new aws/codebuild/standard:6.0 image (node 16/npm 8) instead of aws/codebuild/standard:5.0 (node 14/npm 6).

[bcherny]

Forking json-schema-ref-parser for now. Will switch back to the upstream once APIDevTools/json-schema-ref-parser#272 is merged.

Published in 11.0.2.