Contrib.social

Automated Drupal 11 compatibility fixes for views_ical

Open on Drupal.org →
Created on 25 March 2024, 10 months ago

Problem/Motivation

Hello project maintainers,

This is an automated issue to help make this module compatible with Drupal 11.

Changes will periodically be added to this issue that remove deprecated API uses. To stop further changes from being posted, change the status to anything other than Active, Needs review, Needs work or Reviewed and tested by the community. Alternatively, you can remove the "ProjectUpdateBotD11" tag from the issue to stop the bot from posting updates.

The changes will be posted by the Project Update Bot → official user account. This account will not receive any issue credit contributions for itself or any company.

Proposed resolution

You have a few options for how to use this issue:

  1. Accept automated changes until this issue is closed

    If this issue is left open (status of Active, Needs review, Needs work or Reviewed and tested by the community) and the "ProjectUpdateBotD11" tag is left on this issue, new changes will be posted periodically if new deprecation fixes are needed.

    As the Drupal Rector project improves and is able to fix more deprecated API uses, the changes posted here will cover more of the deprecated API uses in the module.

    Patches and/or merge requests posted by others are ignored by the bot, and general human interactions in the issue do not stop the bot from posting updates, so feel free to use this issue to refine bot changes. The bot will still post new changes then if there is a change in the new generated patch compared to the changes that the bot posted last. Those changes are then up to humans to integrate.

  2. Leave open but stop new automated changes.

    If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated changes, remove the "ProjectUpdateBotD11" tag from the issue and use it like any other issue (the status does not matter then). If you want to receive automated changes again, add back the "ProjectUpdateBotD11" tag.

  3. Close it and don't use it

    If the maintainers of this project don't find this issue useful, they can close this issue (any status besides Active, Needs review, Needs work and Reviewed and tested by the community) and no more automated changes will be posted here.

    If the issue is reopened, then new automated changes will be posted.

    If you are using another issue(s) to work on Drupal 11 compatibility it would be very useful to other contributors to add those issues as "Related issues" when closing this issue.

Remaining tasks

Using the patches

  1. Apply the latest patch in the comments by Project Update Bot → or human contributors that made it better.
  2. Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
  3. Provide feedback about how the testing went. If you can improve the patch, post an updated patch here.

Using the merge request

  1. Review the merge request and test it.
  2. Thoroughly test the changes. These changes are automatically generated so they haven't been tested manually or automatically.
  3. Provide feedback about how the testing went. If you can improve the merge request, create a new branch and merge request and work from there.

Warning: The 'project-update-bot-only' branch will always be overwritten. Do not work in that branch!

Providing feedback

If there are problems with one of the changes posted by the Project Update Bot → , such as it does not correctly replace a deprecation, you can file an issue in the Drupal Rector issue queue → . For other issues with the bot, for instance if the issue summary created by the bot is unclear, use the Project analysis issue queue → .

📌 Task
Status

Needs review

Component

Code

Created by

project update bot

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @project update bot
  • Comment 10 months ago →
    project update bot

    This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.

    It is important that any automated tests available are run and that you manually test the changes.

    Drupal 11 Compatibility

    According to the Upgrade Status module → these changes make this module compatible with Drupal 11! 🎉
    Therefore these changes update the info.yml file for Drupal 11 compatibility.

    Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.

    Debug information

    Bot run #11-127659

    These packages were used to generate the fixes:

    1. drupal/upgrade_status: 4.1.0
    2. mglaman/phpstan-drupal: 1.2.9
    3. palantirnet/drupal-rector: 0.20.1
  • Merge request !18Automated Project Update Bot fixes → (Open) created by project update bot
  • Status changed to RTBC 5 months ago
  • Comment 5 months ago →
    🇺🇦Ukraine ruslan piskarov Kyiv, Ukraine

    Reviewed. I believe we can have a new version for Drupal 11 as soon as possible. Thank you.

  • Comment 1 day ago →
    System Message
    • bburg → committed a12d29fa on 8.x-1.x 
      Issue #3435484: Automated Drupal 11 compatibility fixes for views_ical
  • Comment 1 day ago →
    🇺🇸United States bburg Washington D.C.

    It wouldn't let me merge the PR with another commit in the upstream, and I couldn't figure out how to get the bot to rebase it's branch, so I just went ahead and manually bumped the core compatibility on 8.x-1.x. to 11.

    Not tested per se.

  • Comment 1 day ago →
    🇨🇦Canada Liam Morland Ontario, CA 🇨🇦

    You could rebase the branch and force-push it.

  • Comment 1 day ago →
    🇺🇸United States bburg Washington D.C.

    That's exactly what I was trying to do, bit it was giving me an erro:

    $ git push --force-with-lease views_ical-3465114 views_ical-3465114/3465114-deprecated-function-creation 
Total 0 (delta 0), reused 0 (delta 0)
To git.drupal.org:issue/views_ical-3465114.git
 ! [remote rejected] views_ical-3465114/3465114-deprecated-function-creation -> views_ical-3465114/3465114-deprecated-function-creation (deny updating a hidden ref)

    Also with a plain --force

    $ git push --force views_ical-3465114 views_ical-3465114/3465114-deprecated-function-creation 
Total 0 (delta 0), reused 0 (delta 0)
To git.drupal.org:issue/views_ical-3465114.git
 ! [remote rejected] views_ical-3465114/3465114-deprecated-function-creation -> views_ical-3465114/3465114-deprecated-function-creation (deny updating a hidden ref)
error: failed to push some refs to 'git@git.drupal.org:issue/views_ical-3465114.git'

    I admit being a negligent maintainer has lead to me being out of practice with the Drupal gitlab.

  • Comment about 24 hours ago →
    🇨🇦Canada Liam Morland Ontario, CA 🇨🇦

    Interesting. What if you are on the feature branch that tracks the merge request branch in the issue fork and just run git push --force without any other params? That is what I usually do.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024