Skip to content
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 zustand from 4.5.2 to 5.0.3 in /frontend #50

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 7, 2025

Bumps zustand from 4.5.2 to 5.0.3.

Release notes

Sourced from zustand's releases.

v5.0.3

ExtractState is a type util to extract state type from store type.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v5.0.2...v5.0.3

v5.0.2

This fixes some issues in middleware.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v5.0.1...v5.0.2

v5.0.1

This fixes shallow function for some edge cases.

What's Changed

New Contributors

Full Changelog: pmndrs/zustand@v5.0.0...v5.0.1

v5.0.0

... (truncated)

Commits
  • 3f9127f 5.0.3
  • 6eff6e7 chore(deps): update dev dependencies (#2944)
  • 4378abe fix(build): alias entries in rollup config (#2942)
  • d2ac820 feat(types): Make ExtractState public (#2935)
  • 929b547 docs(create-store.md): fix incorrect usage of create function in example (#...
  • efaf416 docs(create.md): fix state selector syntax in troubleshooting example (#2938)
  • 07b32d6 change prettier to fix:format (#2936)
  • 6759fcb chore(.github/workflows): change 'node-version' to 'lts/*' in 'actions/setup-...
  • 2e6d881 chore(eslint): change 'dist' area in 'ignores', sort rules (#2924)
  • 55a7d0a chore(eslint): migrate to flat config and simplify (#2912)
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Summary by Sourcery

Enhancements:

  • Upgrade Zustand from v4.5.2 to v5.0.3 in the frontend.

Bumps [zustand](https://github.com/pmndrs/zustand) from 4.5.2 to 5.0.3.
- [Release notes](https://github.com/pmndrs/zustand/releases)
- [Commits](pmndrs/zustand@v4.5.2...v5.0.3)

---
updated-dependencies:
- dependency-name: zustand
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jan 7, 2025
Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 7, 2025

Dependabot tried to add @drosetti as a reviewer to this PR, but received the following error from GitHub:

POST https://api.github.com/repos/khulnasoft/ThreatPot/pulls/50/requested_reviewers: 422 - Reviews may only be requested from collaborators. One or more of the users or teams you specified is not a collaborator of the khulnasoft/ThreatPot repository. // See: https://docs.github.com/rest/pulls/review-requests#request-reviewers-for-a-pull-request

Copy link

sourcery-ai bot commented Jan 7, 2025

Reviewer's Guide by Sourcery

This PR upgrades the zustand library from version 4.5.2 to 5.0.3. This upgrade includes several fixes and improvements, such as making ExtractState public, fixing some edge cases in the shallow function, and fixing some issues in middleware.

Class diagram showing ExtractState type utility addition

classDiagram
    class Store {
        +State state
        +SetState setState
        +GetState getState
        +Subscribe subscribe
    }
    class ExtractState {
        <<type utility>>
        +Extract state type from store
    }
    note for ExtractState "New public type utility
for extracting state type
from store type"
Loading

State diagram for zustand version upgrade changes

stateDiagram-v2
    [*] --> Zustand_4.5.2
    Zustand_4.5.2 --> Zustand_5.0.0: Major version upgrade
    Zustand_5.0.0 --> Zustand_5.0.1: Fix shallow function
    Zustand_5.0.1 --> Zustand_5.0.2: Fix middleware issues
    Zustand_5.0.2 --> Zustand_5.0.3: Make ExtractState public
    note right of Zustand_5.0.1: Fixed edge cases in shallow comparison
    note right of Zustand_5.0.2: Fixed devtools and persist middleware
    note right of Zustand_5.0.3: Added ExtractState type utility
Loading

File-Level Changes

Change Details Files
Upgraded zustand from 4.5.2 to 5.0.3
  • Updated the zustand dependency version in package.json
  • Updated the zustand dependency and lockfile in package-lock.json
frontend/package.json
frontend/package-lock.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time. You can also use
    this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

coderabbitai bot commented Jan 7, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

deepsource-io bot commented Jan 7, 2025

Here's the code health analysis summary for commits ec088f9..1c4dd53. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource Python LogoPython✅ SuccessView Check ↗

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!

@gitworkflows
Copy link
Contributor

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

Copy link

CI Failure Feedback 🧐

Action: frontend-tests / Run node.js tests (20, javascript)

Failed stage: Add dependencies [❌]

Failure summary:

The action failed due to a dependency conflict in npm packages:

  • [email protected] requires @types/react@>=18.0.0
  • But the project has @types/[email protected] installed, which is required by other dependencies
  • This creates an unresolvable version conflict between React type definitions
  • The error can be fixed by either:
    1. Updating other dependencies to support React 18
    2.
    Downgrading zustand to a version compatible with React 17
    3. Using --force or --legacy-peer-deps
    flag (not recommended)

  • Relevant error logs:
    1:  ##[group]Operating System
    2:  Ubuntu
    ...
    
    230:  �[36;1mif [[ 'true' != 'false' ]]; then�[0m
    231:  �[36;1m  npm i -D --package-lock-only prettier�[0m
    232:  �[36;1mfi�[0m
    233:  �[36;1mif [[ 'false' != 'false' ]]; then�[0m
    234:  �[36;1m  npm i -D --package-lock-only stylelint�[0m
    235:  �[36;1mfi�[0m
    236:  shell: /usr/bin/bash -e {0}
    237:  ##[endgroup]
    238:  npm error code ERESOLVE
    239:  npm error ERESOLVE could not resolve
    240:  npm error
    241:  npm error While resolving: [email protected]
    242:  npm error Found: @types/[email protected]
    243:  npm error node_modules/@types/react
    244:  npm error   peerOptional @types/react@">=16.8" from [email protected]
    245:  npm error   node_modules/@certego/certego-ui/node_modules/zustand
    246:  npm error     zustand@"^4.0.0-rc.0" from @certego/[email protected]
    247:  npm error     node_modules/@certego/certego-ui
    248:  npm error       @certego/certego-ui@"^0.1.10" from the root project
    249:  npm error   peerOptional @types/react@"^16.9.0 || ^17.0.0" from @testing-library/[email protected]
    250:  npm error   node_modules/@testing-library/react-hooks
    251:  npm error     dev @testing-library/react-hooks@"^8.0.1" from the root project
    252:  npm error   2 more (@types/react-dom, @types/react-transition-group)
    253:  npm error
    254:  npm error Could not resolve dependency:
    255:  npm error peerOptional @types/react@">=18.0.0" from [email protected]
    256:  npm error node_modules/zustand
    257:  npm error   zustand@"^5.0.3" from the root project
    258:  npm error
    259:  npm error Conflicting peer dependency: @types/[email protected]
    260:  npm error node_modules/@types/react
    261:  npm error   peerOptional @types/react@">=18.0.0" from [email protected]
    262:  npm error   node_modules/zustand
    263:  npm error     zustand@"^5.0.3" from the root project
    264:  npm error
    265:  npm error Fix the upstream dependency conflict, or retry
    266:  npm error this command with --force or --legacy-peer-deps
    267:  npm error to accept an incorrect (and potentially broken) dependency resolution.
    268:  npm error
    269:  npm error
    270:  npm error For a full report see:
    271:  npm error /home/runner/.npm/_logs/2025-01-07T16_50_21_153Z-eresolve-report.txt
    272:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-01-07T16_50_21_153Z-debug-0.log
    273:  ##[error]Process completed with exit code 1.
    

    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"
    

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    1 participant