-
Notifications
You must be signed in to change notification settings - Fork 0
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
Bump payload from 2.0.14 to 2.22.2 #119
Conversation
Bumps [payload](https://github.com/payloadcms/payload/tree/HEAD/packages/payload) from 2.0.14 to 2.22.2. - [Release notes](https://github.com/payloadcms/payload/releases) - [Changelog](https://github.com/payloadcms/payload/blob/main/CHANGELOG.md) - [Commits](https://github.com/payloadcms/payload/commits/payload/2.22.2/packages/payload) --- updated-dependencies: - dependency-name: payload dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/payload@2.0.14 |
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat are trivial packages?Packages less than 10 lines of code are easily copied into your own project and may not warrant the additional supply chain risk of an external dependency. Removing this package as a dependency and implementing its logic will reduce supply chain risk. What's wrong with minified code?This package contains minified code. This may be harmless in some cases where minified code is included in packaged libraries, however packages on npm should not minify code. In many cases minified code is harmless, however minified code can be used to hide a supply chain attack. Consider not shipping minified code on npm. What is environment variable access?Package accesses environment variables, which may be a sign of credential stuffing or data theft. Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. What is dynamic require?Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution. Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable code. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
Superseded by #120. |
Bumps payload from 2.0.14 to 2.22.2.
Release notes
Sourced from payload's releases.
... (truncated)
Changelog
Sourced from payload's changelog.
... (truncated)
Commits
320dcc0
chore(release): payload/2.22.2 [skip ci]ea18735
fix: return exp and strategy from auth (#6943)2d35d69
chore(release): payload/2.22.1 [skip ci]bb911cc
fix(payload): #6800, #5108 - graphql query concurrency issues (#6857)8747743
fix: sends cropped image pixel values to server instead of percent values (#6...b230da3
chore(release): payload/2.22.0 [skip ci]58427ff
fix: adjust json field schema for defaultValue (#6872)3364385
fix: cannot use empty string in defaultValue on text-like fields (#6842)025306f
fix: unflattening json objects containing keys with periods (#6834)9a17d66
Revert "chore(deps): bump nodemailer from 6.9.8 to 6.9.9 in /packages/payload...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 rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)