-
Notifications
You must be signed in to change notification settings - Fork 9
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
feat(NODE-6588): add ssdlc to zstd #43
Conversation
176a2d3
to
5073612
Compare
# - name: Install Node and dependencies | ||
# uses: mongodb-labs/drivers-github-tools/node/setup@v2 | ||
# with: | ||
# ignore_install_scripts: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we ignore the install scripts here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do the same for kerberos and mongodb-client-encryption.
By default, npm i
on our packages with native bindings downloads a prebuilt copy of our C++ code (there is an install
script) or attempts to compile the bindings. All we need for this step is the JS dependencies
Description
What is changing?
A passing SSDLC release run is available here: https://github.com/mongodb-js/zstd/actions/runs/12056025639
Note that we can't actually confirm everything looks right until we do an actual release and can inspect the contents of the SSDLC report in s3. Once this PR merges, I can run the beta release and we can confirm.
Is there new documentation needed for these changes?
What is the motivation for this change?
Double check the following
npm run format:js && npm run format:rs
scripttype(NODE-xxxx)[!]: description
feat(NODE-1234)!: rewriting everything in coffeescript