CNV-54903: upgrade showdown to fix cross-spawn on shared sdk

[upalatucci]

@openshift-console/plugin-shared uses a fixed version of showdown affected by cross-spawn CVE.

This do not fix the CVE issue in the console but at least do not propagate the issue on plugins that use @openshift-console/plugin-shared

Surely it's a step to fix the CVE on the console but it seems like we need to upgrade also jest.

The upgrade from 1.8.6 to 1.9.1 is not a big leap. They just added a new feature and fixed a couple of bugs
https://github.com/showdownjs/showdown/releases

[openshift-ci-robot]

@upalatucci: This pull request references CNV-54903 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the vulnerability to target the "4.19.0" version, but no target version was set.

In response to this:

@openshift-console/plugin-shared uses a fixed version of showdown affected by cross-spawn CVE.

This do not fix the CVE issue in console but at least do not propagate the issue on plugins that use @openshift-console/plugin-shared

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@upalatucci: This pull request references CNV-54903 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the vulnerability to target the "4.19.0" version, but no target version was set.

In response to this:

@openshift-console/plugin-shared uses a fixed version of showdown affected by cross-spawn CVE.

This do not fix the CVE issue in console but at least do not propagate the issue on plugins that use @openshift-console/plugin-shared

The upgrade from 1.8.6 to 1.9.1 is not a big leap. They just added a new feature and fixed a couple of bugs
https://github.com/showdownjs/showdown/releases

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@upalatucci: This pull request references CNV-54903 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the vulnerability to target the "4.19.0" version, but no target version was set.

In response to this:

@openshift-console/plugin-shared uses a fixed version of showdown affected by cross-spawn CVE.

This do not fix the CVE issue in the console but at least do not propagate the issue on plugins that use @openshift-console/plugin-shared

Surely it's a step to fix the CVE on the console but it seems like we need to upgrade also jest.

The upgrade from 1.8.6 to 1.9.1 is not a big leap. They just added a new feature and fixed a couple of bugs
https://github.com/showdownjs/showdown/releases

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[upalatucci]

/retest

[upalatucci]

/retest

[jhadvig]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhadvig, upalatucci

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• frontend/OWNERS [jhadvig]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[upalatucci]

/retest

[upalatucci]

/retest

[upalatucci]

/retest

[upalatucci]

/retest

[upalatucci]

/retest

[upalatucci]

/retest

[openshift-ci]

@upalatucci: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.