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

chore(deps): update dependency drupal/search_api_lunr to v3 #476

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 6, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
drupal/search_api_lunr (source) 2.0.1 -> 3.1.0 age adoption passing confidence

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies label Sep 6, 2023
@renovate renovate bot force-pushed the renovate/drupal-search_api_lunr-3.x branch from 1bfe083 to 9ccef05 Compare December 14, 2023 03:55
Copy link
Contributor Author

renovate bot commented Dec 14, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: drupal/composer.lock
Command failed: composer update drupal/search_api_lunr:3.0.1 --with-dependencies --ignore-platform-req='ext-*' --ignore-platform-req='lib-*' --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - drupal/search_api[1.31.0, ..., 1.x-dev] require drupal/core ^10.0 -> found drupal/core[10.0.0-alpha1, ..., 10.2.x-dev] but these were not loaded, likely because it conflicts with another require.
    - drupal/search_api_lunr 3.0.1 requires drupal/search_api ^1.31 -> satisfiable by drupal/search_api[1.31.0, 1.x-dev].
    - Root composer.json requires drupal/search_api_lunr 3.0.1 -> satisfiable by drupal/search_api_lunr[3.0.1].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Copy link

coderabbitai bot commented Dec 14, 2023

Walkthrough

The primary change involves upgrading the drupal/search_api_lunr package from version 2.0.1 to 3.1.0 in the composer.json file. This update likely brings enhancements, including new features and bug fixes, improving overall functionality. However, detailed implications of this upgrade would require reviewing the specific release notes for version 3.1.0.

Changes

Files Change Summary
drupal/composer.json Updated drupal/search_api_lunr from 2.0.1 to 3.1.0

Poem

In fields of code where bunnies hop,
A package upgraded, the old to drop.
With features bright and bugs erased,
We celebrate change, our code embraced!
Hooray for Lunr, our search so swift,
A leap to the future, a wonderful gift! 🐇✨


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.

@renovate renovate bot force-pushed the renovate/drupal-search_api_lunr-3.x branch from 9ccef05 to 667ecd6 Compare August 12, 2024 00:36
Copy link
Contributor Author

renovate bot commented Aug 12, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: drupal/composer.lock
Command failed: composer update drupal/search_api_lunr:3.1.0 --with-dependencies --ignore-platform-req='ext-*' --ignore-platform-req='lib-*' --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/search_api_lunr 3.1.0 -> satisfiable by drupal/search_api_lunr[3.1.0].
    - drupal/search_api_lunr 3.1.0 requires drupal/core ^10.2 || ^11 -> found drupal/core[10.2.0-alpha1, ..., 10.4.x-dev, 11.0.0-alpha1, ..., 11.x-dev] but these were not loaded, likely because it conflicts with another require.
  Problem 2
    - longwave/laminas-diactoros[2.14.2, ..., 2.14.x-dev] require php ^7.3 || ~8.0.0 || ~8.1.0 || ~8.2.0 -> your php version (8.3.10) does not satisfy that requirement.
    - drupal/core-recommended 9.5.10 requires longwave/laminas-diactoros ~2.14.2 -> satisfiable by longwave/laminas-diactoros[2.14.2, 2.14.x-dev].
    - drupal/core-recommended is locked to version 9.5.10 and an update of this package was not requested.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Copy link

@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 1aecb1e and 667ecd6.

Files selected for processing (1)
  • drupal/composer.json (1 hunks)
Additional comments not posted (1)
drupal/composer.json (1)

30-30: Verify the compatibility and impact of drupal/search_api_lunr version update.

The drupal/search_api_lunr package has been updated from 2.0.1 to 3.1.0. Ensure that this new version is compatible with your current Drupal setup and does not introduce breaking changes. Review the release notes for version 3.1.0 to understand the changes and any migration steps that might be necessary.

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

Successfully merging this pull request may close these issues.

0 participants