-
Notifications
You must be signed in to change notification settings - Fork 0
Bump the npm_and_yarn group across 1 directory with 2 updates #19
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
base: main
Are you sure you want to change the base?
Bump the npm_and_yarn group across 1 directory with 2 updates #19
Conversation
Bumps the npm_and_yarn group with 2 updates in the /backend directory: [express](https://github.com/expressjs/express) and [nodemailer](https://github.com/nodemailer/nodemailer). Updates `express` from 4.21.2 to 4.22.1 - [Release notes](https://github.com/expressjs/express/releases) - [Changelog](https://github.com/expressjs/express/blob/v4.22.1/History.md) - [Commits](expressjs/express@4.21.2...v4.22.1) Updates `nodemailer` from 7.0.7 to 7.0.11 - [Release notes](https://github.com/nodemailer/nodemailer/releases) - [Changelog](https://github.com/nodemailer/nodemailer/blob/master/CHANGELOG.md) - [Commits](nodemailer/nodemailer@v7.0.7...v7.0.11) --- updated-dependencies: - dependency-name: express dependency-version: 4.22.1 dependency-type: direct:production dependency-group: npm_and_yarn - dependency-name: nodemailer dependency-version: 7.0.11 dependency-type: direct:production dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <[email protected]>
|
The files' contents are under analysis for test generation. |
Micro-Learning Topic: Stack overflow (Detected by phrase)Matched on "stack overflow"Also referred to as Stack buffer overflows. This vulnerability occurs when data received by a program is written to a memory location on the stack and the allocated space is not large enough to take the whole input. If proper boundary checks are not implemented, or unsafe functions like sprintf, fgets etc. are used which don't require a destination size limit the stack memory after the target buffer may be written to, allowing an attacker to alter the normal behaviour of the program. Most modern compilers now have a secure switch which may reorder stack variables and generate extra code to protect against this type of vulnerability. Try a challenge in Secure Code Warrior |
|
Review these changes at https://app.gitnotebooks.com/OneFineStarstuff/OneFineStarstuff.github.io/pull/19 |
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.
The changes in the PR look good overall, but there are a few points to address:
-
Missing Newline at End of File:
Ensure that all files end with a newline. This is a common convention and helps avoid issues with concatenation and version control systems. -
Versioning Consistency:
The change from fixed versions to tilde versions (e.g.,"body-parser": "1.20.3"to"body-parser": "~1.20.3") should be consistent across all dependencies. Ensure that this change is intentional and documented, as it affects how versions are resolved. -
Security Considerations:
Ensure that the updated versions ofexpressandnodemailerdo not introduce any new vulnerabilities. It is good practice to check the release notes and security advisories for these packages. -
Dependencies in
node_modules:
The addition ofnode_modules/express/node_modules/qsshould be verified to ensure it does not cause any conflicts or issues with the mainqspackage if it is used elsewhere in the project.
Please address these points before merging the PR.
|
View changes in DiffLens |
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
❌ Deploy Preview for onefinestarstuff failed.
|
Bumps the npm_and_yarn group with 2 updates in the /backend directory: express and nodemailer.
Updates
expressfrom 4.21.2 to 4.22.1Release notes
Sourced from express's releases.
Changelog
Sourced from express's changelog.
Commits
12fae144.22.15ddf311Revert "sec: security patch for CVE-2024-51999"49744ab4.22.0 (#6921)6e97452sec: security patch for CVE-2024-519996a23d34deps: use tilde notation forqs(#6919)8c12cdfdeps: [email protected] (#6909)7fea74fdeps: use tilde notation for certain dependencies (#6905)dac7a04chore: wider range for query test skip (#6513)997919bci: add node.js 24 to test matrix (#6506)36fb59cfix(ci): reordernpm isteps to fix ci for older node versions (#6336)Updates
nodemailerfrom 7.0.7 to 7.0.11Release notes
Sourced from nodemailer's releases.
Changelog
Sourced from nodemailer's changelog.
Commits
3d17dbechore(master): release 7.0.11 (#1783)15879f8Bumped dev dependenciesb61b9c0fix: prevent stack overflow DoS in addressparser with deeply nested groups4175e4bchore(master): release 7.0.10 (#1776)d882ccfMerge branch 'master' of github.com:nodemailer/nodemailer1d7e4f7Bumped deps10bd871chore: correct typo in variable name (#1773)28dbf3ffix: Increase data URI size limit from 100KB to 50MB and preserve content type92ae1c4chore(master): release 7.0.9 (#1769)c675d9eMerge branch 'master' of github.com:nodemailer/nodemailerMaintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for nodemailer since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.