Skip to content

Conversation

@padamstx
Copy link
Contributor

@padamstx padamstx commented Jun 4, 2025

I got lucky... all I had to do is run npm install in my local sandbox to re-load dependencies, and the tar-fs dependency got bumped to the fixed version without needing to do anything else.

@padamstx padamstx self-assigned this Jun 4, 2025
@padamstx padamstx requested a review from pyrooka June 4, 2025 15:18
Signed-off-by: Phil Adams <phil_adams@us.ibm.com>
# warranted by the new commits being built).

name: Build/Test/Publish
name: build
Copy link
Contributor Author

Choose a reason for hiding this comment

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

While monitoring the builds for this PR initially, I realized that I had not yet updated the job names in the workflows like I have done recently in the other github.com projects (cores, sdks, etc.), so I went back and made those changes, then pushed an amended commit...

Copy link
Member

@pyrooka pyrooka left a comment

Choose a reason for hiding this comment

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

LGTM!

@padamstx padamstx merged commit 4b1ce8b into main Jun 4, 2025
7 checks passed
@padamstx padamstx deleted the fix-vuln branch June 4, 2025 17:25
@ibm-devx-sdk
Copy link

🎉 This PR is included in version 1.31.2 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

@ibm-devx-sdk
Copy link

🎉 This PR is included in version 1.35.3 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants