Upgrade to NextJS 11 to fix CVEs#171
Merged
Merged
Conversation
Signed-off-by: SamMayWork <sam.may@kaleido.io>
Signed-off-by: SamMayWork <sam.may@kaleido.io>
Signed-off-by: SamMayWork <sam.may@kaleido.io>
Signed-off-by: SamMayWork <sam.may@kaleido.io>
Contributor
Author
|
Noting that the Docker build is failing due to issues w/ Trivy download which is strange considering the ERC20 PR is just fine. I am noticing a large number of 500's coming from GitHub so wondering if there are other issues going on. |
Contributor
|
Have re-run the jobs |
EnriqueL8
approved these changes
Dec 11, 2025
Contributor
There was a problem hiding this comment.
Thanks for the great work here @SamMayWork - testing and explaining why the Nest 11 upgrade is safe and fixes loads of CVEs 🙇🏼
See the explanation here hyperledger/firefly-tokens-erc20-erc721#189 (comment)
This was referenced Dec 11, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ref: hyperledger/firefly-tokens-erc20-erc721#189
Similar to what we did for the erc20/erc721 token connector, this PR suggests bumping to NestJS 11 to resolve a number of CVEs in the application.
For more information on the migrations and features of NestJS 11 see:
Buuuuut at a high-level, NestJS 11 brings a newer version of express/fastify and with it some changes to how wildcard routes are defined w/ some breaking changes to niche query features that we are not using within this application.
...and for sake of completeness, the full list of CVEs that this PR addresses is: