kpumuk opened a new pull request, #3724:
URL: https://github.com/apache/thrift/pull/3724

   ### Why?
   
   Dependabot cannot update the affected `js-yaml` copies used by the legacy 
JavaScript and TypeScript packages because their locked Grunt versions 
constrain them to the 3.14.x line. This addresses the remaining alerts 
[#284](https://github.com/apache/thrift/security/dependabot/284), 
[#303](https://github.com/apache/thrift/security/dependabot/303), and 
[#248](https://github.com/apache/thrift/security/dependabot/248) for `lib/js`, 
plus [#287](https://github.com/apache/thrift/security/dependabot/287), 
[#305](https://github.com/apache/thrift/security/dependabot/305), and 
[#249](https://github.com/apache/thrift/security/dependabot/249) for `lib/ts`.
   
   ### How?
   
   Refresh Grunt to 1.6.3 in both dependency trees, which permits `js-yaml` 
3.15.1 while retaining the existing Node.js 16 compatibility.
   
   - [ ] Did you create an [Apache 
Jira](https://issues.apache.org/jira/projects/THRIFT/issues/) ticket? ([Request 
account here](https://selfserve.apache.org/jira-account.html), not required for 
trivial changes)
   - [ ] If a ticket exists: Does your pull request title follow the pattern 
"THRIFT-NNNN: describe my issue"?
   - [x] Did you squash your changes to a single commit? (not required, but 
preferred)
   - [x] Did you do your best to avoid breaking changes? If one was needed, did 
you label the Jira ticket with "Breaking-Change"?
   - [ ] If your change does not involve any code, include `[skip ci]` anywhere 
in the commit message to free up build resources.
   
   <!--
     The Contributing Guide at:
     https://github.com/apache/thrift/blob/master/CONTRIBUTING.md
     has more details and tips for committing properly.
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to