fix: updating json-schema requirement for jsprim to prevent vulnerability issue

6 jobs for !270 with msft/bugfix-another-json-schema in 2 minutes and 8 seconds (queued for 7 seconds)
latest detached
Status Name Job ID Coverage
  Review
failed trigger-trusted-tests #726798
osdu-small

00:02:08

failed trigger-trusted-tests #726788
osdu-small

00:02:00

 
  Build
skipped compile-and-unit-test #726789
osdu-medium
 
  Containerize
skipped push_runtime_image #726790
osdu-medium
 
  Scan
skipped lint #726791
osdu-small
skipped scan-for-secrets #726792
osdu-small
 
Name Stage Failure
failed
trigger-trusted-tests Review
needs to launch a protected pipeline, which by convention is prefixed with 'trusted-'. Only maintainers
can create protected branches. If you are not a maintainer, please ask one to create a trusted branch for
you. They will need to inspect your branch for proper handling of secret variables before applying the trusted label.
If you are a maintainer, you need to push a branch named 'trusted-msft/bugfix-another-json-schema', then re-run this pipeline.
----------------------------------------
If all else fails / something weird is going on, the logic in this script is maintained by:
David Diederich, @divido, d.diederich@opengroup.org
Cleaning up file based variables
ERROR: Job failed: exit code 1