- Issue created by @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 theinfo.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-223311These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.4
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.3
- Status changed to Needs review
6 months ago 12:07am 16 July 2024 - First commit to issue fork.
- Status changed to RTBC
5 months ago 11:36pm 12 August 2024 - 🇺🇸United States BenStallings
once I resolved the merge conflict, this worked fine!
- 🇦🇺Australia VladimirAus Brisbane, Australia
VladimirAus → changed the visibility of the branch project-update-bot-only to hidden.
- 🇦🇺Australia VladimirAus Brisbane, Australia
VladimirAus → changed the visibility of the branch 3461681-automated-drupal-11 to hidden.
- 🇦🇺Australia VladimirAus Brisbane, Australia
VladimirAus → changed the visibility of the branch 3461681-drupal11 to hidden.
- 🇦🇺Australia VladimirAus Brisbane, Australia
Maintainers, your branch is oncorrect, hemce new MRs are not workign properly.
Please, create 2.0.x branch so it would be possible to create proper Drupal 11 merge request. - Status changed to Postponed: needs info
5 months ago 1:53pm 13 August 2024 - 🇦🇺Australia VladimirAus Brisbane, Australia
VladimirAus → changed the visibility of the branch 3461681-drupal11-release to hidden.
- Status changed to Needs work
5 months ago 1:54pm 13 August 2024 - 🇬🇧United Kingdom mcdruid 🇬🇧🇪🇺
@VladimirAus could you please explain why a new 2.0.x branch would be needed?
According to: https://www.drupal.org/docs/develop/git/git-for-drupal-project-maintaine... →
...it's not mandatory to use
{major}.{minor}.x
Thanks!
- 🇬🇧United Kingdom mcdruid 🇬🇧🇪🇺
As far as I can see, the changes that the bot is proposing are already in 2.x (the version constraint in the info file is not exactly the same, but D11 has been added).
The changes were committed a few weeks ago: https://git.drupalcode.org/project/seckit/-/commit/39d3d64cf9b64f2c41fec...
So two questions:
1) Is there actually anything left to do before we can create a D11 release for seckit?
2) Is the problem mentioned in #10 that the Project Update Bot is not compatible with a branch called 2.x as opposed to
{major}.{minor}.x
?If there are good reasons to create a new branch following the z.x.y naming convention for D11 support, we can do that.. but I don't necessarily want to create maintenance burden and potential confusion for the project's users if the only reason is that the bot doesn't understand the naming convention.
- Status changed to Closed: duplicate
5 months ago 10:22am 14 August 2024 - 🇮🇳India ankitv18
This module is already D11 compatible and all the fixes are done https://www.drupal.org/project/seckit/issues/3434417 📌 Automated Drupal 11 compatibility fixes for seckit Fixed
Current 2.x-dev pipeline: https://git.drupalcode.org/project/seckit/-/pipelines/229020 (Shows all the deprecations and other required fixes are done and pipelines are clean now)
Reason ProjectUpdateBot opened this issue as previous issue didn't have tag ProjectUpdateBotD11 that's why this issue is opened last month.
Hence I'm closing this one as duplicate.