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

build(deps-dev): bump eslint-plugin-promise from 6.1.1 to 7.1.0 #286

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

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 7, 2024

Bumps eslint-plugin-promise from 6.1.1 to 7.1.0.

Release notes

Sourced from eslint-plugin-promise's releases.

v7.1.0

7.1.0 (2024-08-06)

🌟 Features

  • catch-or-return, prefer-await-to-then: do not report Cypress commands (#495) (943f162)
  • prefer-await-to-then: ignore constructor scope unless with strict option (#496) (7bffb7a)
  • new rule spec-only to check for non-spec Promise methods (#502) (d6e9de1)

📚 Documentation

🧹 Chores

v7.0.0

7.0.0 (2024-07-24)

BREAKING CHANGES

  • Requires Node.js: ^18.18.0 || ^20.9.0 || >=21.1.0

v6.6.0

6.6.0 (2024-07-21)

Bug Fixes

  • always-return: treat process.exit() or process.abort() as an acceptable "return" (#493) (f368c5a)

Features

  • add strict option to disallow then or catch following await or yield (#494) (fa482cc)

v6.5.1

6.5.1 (2024-07-20)

... (truncated)

Changelog

Sourced from eslint-plugin-promise's changelog.

7.1.0 (2024-08-06)

🌟 Features

  • catch-or-return, prefer-await-to-then: do not report Cypress commands (#495) (943f162)
  • prefer-await-to-then: ignore constructor scope unless with strict option (#496) (7bffb7a)
  • new rule spec-only to check for non-spec Promise methods (#502) (d6e9de1)

📚 Documentation

🧹 Chores

6.0.2

  • Added tests for @​typescript-eslint/parser support

6.0.1

  • Fixed @​typescript-eslint/parser issue #331, #205

6.0.0

5.2.0

  • Updated param-names rule to allow for unused params

5.1.1

  • Updated docs to include no-callback-in-promise reasons #215

5.1.0

  • Included catch() and finally() in prefer-await-to-then #196
  • Added some additional tests and upgraded some dev deps #196
  • Exempted array methods in prefer-await-to-callbacks

... (truncated)

Commits
  • d0ff43f chore(main): release 7.1.0 (#510)
  • adc4a85 ci: fix feedback on release-please (#531)
  • 94c9834 refactor: file extension missing (#519)
  • ab8e7a0 chore(deps-dev): bump husky from 9.1.1 to 9.1.2 (#516)
  • 1e13293 ci: add pr title format validation (#509)
  • 030a3be docs: fixes the CI readme badge (#511)
  • 7bffb7a feat(prefer-await-to-then): ignore constructor scope unless with strict o...
  • d6e9de1 feat: new rule spec-only to check for non-spec Promise methods (#502)
  • 943f162 feat(catch-or-return, prefer-await-to-then): do not report Cypress comman...
  • e1ce2ad ci: swap release process to release-please (#508)
  • 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 CodeRabbit

  • Chores
    • Updated the eslint-plugin-promise package to the latest version, which may provide enhanced performance and improved promise handling capabilities.

Bumps [eslint-plugin-promise](https://github.com/eslint-community/eslint-plugin-promise) from 6.1.1 to 7.1.0.
- [Release notes](https://github.com/eslint-community/eslint-plugin-promise/releases)
- [Changelog](https://github.com/eslint-community/eslint-plugin-promise/blob/main/CHANGELOG.md)
- [Commits](eslint-community/eslint-plugin-promise@v6.1.1...v7.1.0)

---
updated-dependencies:
- dependency-name: eslint-plugin-promise
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Aug 7, 2024
Copy link
Contributor

coderabbitai bot commented Aug 7, 2024

Walkthrough

The update involves a change in the package.json file, specifically upgrading the version of the eslint-plugin-promise from ^6.1.1 to ^7.1.0. This upgrade could bring important enhancements such as bug fixes, improved performance, and new features that improve promise handling in JavaScript. No other dependencies were altered, ensuring stability in the project's overall setup while benefiting from the latest features of the plugin.

Changes

Files Change Summary
package.json Updated eslint-plugin-promise version from ^6.1.1 to ^7.1.0

Poem

🐰 In the garden where promises bloom,
A new version hops, dispelling the gloom.
With fixes and features, it dances with glee,
Upgrading our code, oh, what joy to see!
So let’s cheer for the change, a leap in the night,
For code that is clearer, and futures so bright! 🌟


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

sonarqubecloud bot commented Aug 7, 2024

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7daad22 and 3282a6d.

Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
Files selected for processing (1)
  • package.json (1 hunks)
Additional comments not posted (1)
package.json (1)

187-187: Upgrade eslint-plugin-promise to ^7.1.0.

The version of eslint-plugin-promise has been updated from ^6.1.1 to ^7.1.0. Ensure to verify the new features and changes introduced in this version, such as the new spec-only rule and changes to catch-or-return and prefer-await-to-then rules, and update the configuration if necessary.

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants