refactor: Bump crypto-js and parse #344
Open
Conversation
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
Bumps [crypto-js](https://github.com/brix/crypto-js) to 4.2.0 and updates ancestor dependency [parse](https://github.com/parse-community/Parse-SDK-JS). These dependencies need to be updated together. Updates `crypto-js` from 4.1.1 to 4.2.0 - [Commits](brix/crypto-js@4.1.1...4.2.0) Updates `parse` from 3.5.1 to 6.1.1 - [Release notes](https://github.com/parse-community/Parse-SDK-JS/releases) - [Changelog](https://github.com/parse-community/Parse-SDK-JS/blob/alpha/CHANGELOG.md) - [Commits](parse-community/Parse-SDK-JS@3.5.1...6.1.1) --- updated-dependencies: - dependency-name: crypto-js dependency-version: 4.2.0 dependency-type: indirect - dependency-name: parse dependency-version: 6.1.1 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
|
I will reformat the title to use the proper commit message syntax. |
parse-github-assistant
bot
changed the title
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Join our Discord community for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Bumps crypto-js to 4.2.0 and updates ancestor dependency parse. These dependencies need to be updated together.
Updates
crypto-jsfrom 4.1.1 to 4.2.0Commits
808f499Merge branch 'release/4.2.0'd5af3aeUpdate release notes.9496e07Bump version.421dd53Change default hash algorithm and iteration's for PBKDF2 to prevent weak secu...d1f4f4dUpdate grunt.c755289Discontinued1da3dabDiscontinued4dcaa7aMerge pull request #380 from Alanscut/dev762feb2chore: rename BF to Blowfishfb81418feat: blowfish supportUpdates
parsefrom 3.5.1 to 6.1.1Release notes
Sourced from parse's releases.
... (truncated)
Commits
26d5cc9chore(release): 6.1.1 [skip ci]ca30be3build: Release (#2554)3b19832Merge branch 'release' into build/release-2025040409202f5empty commit to trigger CI8692022chore(release): 6.1.0-alpha.5 [skip ci]c7015bafix: Remove unused optionsessionTokenfromParse.Query.aggregate(#2547)451ad04docs: Improve Typescript JSDocs support (#2549)6bc3feechore(release): 6.1.0-alpha.4 [skip ci]44eeacdfix: Security upgrade tar-fs from 2.1.1 to 2.1.2 (#2540)6fceea4refactor: Bump@babel/runtime-corejs3from 7.26.10 to 7.27.0 (#2536)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 this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.