Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix V3 scans for client-side & generate separate VSCode notices bundle #146

Conversation

t1m0thyj
Copy link
Member

@t1m0thyj t1m0thyj commented Sep 26, 2024

  • Moved the notices for zowe-explorer-vscode into a separate zip artifact. Previously the VSCode notices were being included with the zos components.
  • Added --ignore-scripts flag to npm/yarn/pnpm install commands. Since the --prod flag was added in Support PNPM, Respect Lockfiles #145, the prepare script fails for some repos if it requires a dev dep (e.g. husky).
  • Added step to install pnpm in workflow because it was missing from PATH. Not sure why the install script added to Dockerfile in Support PNPM, Respect Lockfiles #145 didn't work.
  • Updated version of ORT in Dockerfile and published a snapshot with test-timothy tag. V15 had several errors causing it to fail parsing Cargo (CLI daemon) and PNPM (ZE) projects that were fixed by upgrading.

@awharn @zFernand0 @traeok Please review the CLI and VSCode artifacts generated by the license workflow.

jackjia-ibm and others added 30 commits January 29, 2021 15:41
Add component level test suite for Explorer APIs
Signed-off-by: Jack (T.) Jia <[email protected]>
…client/node-notifier-8.0.1

Bump node-notifier from 8.0.0 to 8.0.1 in /performance/client
Signed-off-by: Jack (T.) Jia <[email protected]>
Signed-off-by: Jack (T.) Jia <[email protected]>
Signed-off-by: Jack (T.) Jia <[email protected]>
Signed-off-by: Jack (T.) Jia <[email protected]>
Signed-off-by: Jack (T.) Jia <[email protected]>
Signed-off-by: Jack (T.) Jia <[email protected]>
Signed-off-by: Jack (T.) Jia <[email protected]>
Signed-off-by: Jack (T.) Jia <[email protected]>
Signed-off-by: Jack (T.) Jia <[email protected]>
Signed-off-by: MarkAckert <[email protected]>
dependabot bot and others added 9 commits September 10, 2024 18:30
Bumps [path-to-regexp](https://github.com/pillarjs/path-to-regexp) to 0.1.10 and updates ancestor dependency [express](https://github.com/expressjs/express). These dependencies need to be updated together.


Updates `path-to-regexp` from 0.1.7 to 0.1.10
- [Release notes](https://github.com/pillarjs/path-to-regexp/releases)
- [Changelog](https://github.com/pillarjs/path-to-regexp/blob/master/History.md)
- [Commits](pillarjs/path-to-regexp@v0.1.7...v0.1.10)

Updates `express` from 4.19.2 to 4.20.0
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/master/History.md)
- [Commits](expressjs/express@4.19.2...4.20.0)

---
updated-dependencies:
- dependency-name: path-to-regexp
  dependency-type: indirect
- dependency-name: express
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
…/server/multi-ceff1a497b

Bump path-to-regexp and express in /performance/server
Bumps [send](https://github.com/pillarjs/send) to 0.19.0 and updates ancestor dependency [express](https://github.com/expressjs/express). These dependencies need to be updated together.


Updates `send` from 0.18.0 to 0.19.0
- [Release notes](https://github.com/pillarjs/send/releases)
- [Changelog](https://github.com/pillarjs/send/blob/master/HISTORY.md)
- [Commits](pillarjs/send@0.18.0...0.19.0)

Updates `express` from 4.20.0 to 4.21.0
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/4.21.0/History.md)
- [Commits](expressjs/express@4.20.0...4.21.0)

---
updated-dependencies:
- dependency-name: send
  dependency-type: indirect
- dependency-name: express
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
…/server/multi-cf87d80143

Bump send and express in /performance/server
@t1m0thyj t1m0thyj force-pushed the user/timothy/separate-vscode-notices branch from 8b4d7ec to 3ccd9ad Compare September 26, 2024 21:38
@t1m0thyj t1m0thyj marked this pull request as ready for review September 27, 2024 13:01
@t1m0thyj t1m0thyj changed the title Generate a separate VSCode notices bundle Fix V3 scans for client-side, generate a separate VSCode notices bundle Sep 27, 2024
@t1m0thyj t1m0thyj changed the title Fix V3 scans for client-side, generate a separate VSCode notices bundle Fix V3 scans for client-side & generate a separate VSCode notices bundle Sep 27, 2024
@t1m0thyj t1m0thyj changed the title Fix V3 scans for client-side & generate a separate VSCode notices bundle Fix V3 scans for client-side & generate separate VSCode notices bundle Sep 27, 2024
Copy link
Member

@traeok traeok left a comment

Choose a reason for hiding this comment

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

LGTM, thanks Timothy for the fixes!

Not related, but I see we have a couple "android"-related deps in the dependency tree 😂 not quite sure where that's coming from, but the licenses & dependency list seems accurate

image

container:
image: zowe-docker-release.jfrog.io/ompzowe/zowecicd-license-base:latest
image: zowe-docker-snapshot.jfrog.io/ompzowe/zowecicd-license-base:test-timothy
Copy link
Member

Choose a reason for hiding this comment

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

Do we still plan on using the test-timothy tag for the container image? No request for changes here, just wondering 😋

Copy link
Member

Choose a reason for hiding this comment

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

Please revert the image to release/latest before merging in 👍

env:
APP_NOTICES_SCAN: true
APP_LICENSE_SCAN: true
ZOWE_MANIFEST_BRANCH: ${{ env.ZOWE_RELEASE_BRANCH }}
working-directory: ${{ env.DEPENDENCY_SCAN_HOME }}
run: |
# Rustup is set to default in the container, but it's not picked up in this run block
rustup default stable
rustup default stable
npm install -g pnpm@8
Copy link
Member

Choose a reason for hiding this comment

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

Can we move this pnpm install to the docker build?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants