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

[SECURITY] Update drupal/core-recommended from 10.2.0 to 10.2.3 #265

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

Conversation

violinist-bot
Copy link
Contributor

If you have a high test coverage index, and your tests for this pull request are passing, it should be both safe and recommended to merge this update.

Updated packages

Some times an update also needs new or updated dependencies to be installed. Even if this branch is for updating one dependency, it might contain other installs or updates. All of the updates in this branch can be found here:

  • doctrine/deprecations: 1.1.3 (updated from 1.1.2)
  • doctrine/lexer: 2.1.1 (updated from 2.1.0)
  • drupal/core: 10.2.3 (updated from 10.2.0)
  • drupal/core-composer-scaffold: 10.2.3 (updated from 10.2.0)
  • drupal/core-project-message: 10.2.3 (updated from 10.2.0)
  • drupal/core-recommended: 10.2.3 (updated from 10.2.0)
  • symfony/console: v6.4.3 (updated from v6.4.1)
  • symfony/dependency-injection: v6.4.3 (updated from v6.4.1)
  • symfony/error-handler: v6.4.3 (updated from v6.4.0)
  • symfony/event-dispatcher: v6.4.3 (updated from v6.4.0)
  • symfony/filesystem: v6.4.3 (updated from v6.4.0)
  • symfony/http-foundation: v6.4.3 (updated from v6.4.0)
  • symfony/http-kernel: v6.4.3 (updated from v6.4.1)
  • symfony/mailer: v6.4.3 (updated from v6.4.0)
  • symfony/mime: v6.4.3 (updated from v6.4.0)
  • symfony/polyfill-php72: v1.29.0 (updated from v1.28.0)
  • symfony/polyfill-php80: v1.29.0 (updated from v1.28.0)
  • symfony/polyfill-php81: v1.29.0 (updated from v1.28.0)
  • symfony/process: v6.4.3 (updated from v6.4.0)
  • symfony/psr-http-message-bridge: v6.4.3 (updated from v6.4.0)
  • symfony/routing: v6.4.3 (updated from v6.4.1)
  • symfony/serializer: v6.4.3 (updated from v6.4.1)
  • symfony/service-contracts: v3.4.1 (updated from v3.4.0)
  • symfony/string: v6.4.3 (updated from v6.4.0)
  • symfony/translation-contracts: v3.4.1 (updated from v3.4.0)
  • symfony/validator: v6.4.3 (updated from v6.4.0)
  • symfony/var-dumper: v6.4.3 (updated from v6.4.0)
  • symfony/var-exporter: v6.4.3 (updated from v6.4.1)
  • symfony/yaml: v6.4.3 (updated from v6.4.0)

Release notes

Here are the release notes for all versions released between your current running version, and the version this PR updates the package to.

List of release notes

Changed files

Here is a list of changed files between the version you use, and the version this pull request updates to:

List of changed files
  composer.json

Changelog

Here is a list of changes between the version you use, and the version this pull request updates to:


This is an automated pull request from Violinist: Continuously and automatically monitor and update your composer dependencies. Have ideas on how to improve this message? All violinist messages are open-source, and can be improved here.

Copy link

coderabbitai bot commented Feb 7, 2024

Important

Auto Review Skipped

Review was skipped due to path filters

Files ignored due to path filters (1)
  • composer.lock is excluded by: !**/*.lock

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-tests for this file.
  • 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 tests 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 from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

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

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant