Closed (fixed)
Project:
Gatsby Integration
Version:
2.0.x-dev
Component:
Code
Priority:
Critical
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
23 Jan 2025 at 19:30 UTC
Updated:
2 Jul 2025 at 04:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #4
tbadaczewski commentedAre people actively maintaining this project? I don't mean maintainer open to PRs, but actually responding to issues?
This is a very important module for our web application, and not having it compatible with Drupal 11 is holding us back from upgrading.
Comment #5
larowlan@tbadaczewski hey I'm still here but I wear a lot of hats
My advice would be to look to move away from Gatsby in general - the health of the Drupal project isn't the issue - the health of the Javascript project is - e.g. see https://github.com/gatsbyjs/gatsby/issues/38696
Drupal 10 is supported until mid/late 2026 so there's not as much urgency to get a D11 version out.
We have moved all our Drupal+Gatsby projects to something that isn't Gatsby so don't have any client projects where this update is pressing.
What this means is I'm happy to review MRs if things are ready but I'm unlikely to have time to dedicate to authoring them.
Comment #6
tbadaczewski commented@larowlan thanks for the strait talk info, I do appreciate it. We have been looking to shift from GatsbyJS to NextJS, but we were hoping to upgrade the Drupal 10 backend to Drupal 11 first. I'm hoping that this module already supports Drupal 11, but just needs a version bump in the info file. I'll do my own testing to see what problems arise. Once again, thanks for the response.
Comment #7
larowlanNo worries, happy to merge stuff to unblock.
Comment #8
tbadaczewski commentedI created a patch that solves the only PHP errors I had when testing this module with a Drupal 11 on a PHP 8.4 install. I also was able to install this on my current Drupal 10.4 update without any issues.
It also updates the core versions to ^11.
I'd love some feedback.
Comment #9
larowlan@tbadaczewski nothing in that patch looks out of place to me, would committing this to HEAD make things easier?
Comment #10
tbadaczewski commentedSorry, this is my first time submitting a patch so not sure next steps. Did you want me to commit the updated code to the 'gatsby-3501829' branch directly? I did request push access just in case.
Comment #11
larowlanNo sorry mate, I'm asking if I should commit this for you - would that make further improvements easier?
I'm not working on the module but I don't want to block fine folks like yourself who are
Comment #12
tbadaczewski commented@larowlan Yes please! Thanks.
Comment #13
larowlanThe patch doesn't apply to 8.x-1.x - needs a reroll
Comment #14
tbadaczewski commentedComment #15
tbadaczewski commentedThat was my fault, I always intended this issue to be in the context of the 2.0.0-X version. I updated the issue to reflect that.
Could you try again?
Comment #16
tbadaczewski commentedComment #17
tbadaczewski commentedThis patch has been updated to also address the "drupal/upgrade_status" scan module finding of a depreciated function call.
Comment #19
larowlanThanks I've committed and pushed that change to the 2.0.x branch
Comment #20
tbadaczewski commentedAdded two addtional PHP modifications so that the entire codebase adheres to the "NullableTypeForNullDefaultValue" standard. Without these changes you would get "Deprecated" warnings when running on PHP 8.4.X.
Comment #21
larowlanCan you provide just the new changes? I can't apply the current patch - thanks
Comment #22
tbadaczewski commentedHere is a patch that just has the additional changes for:
FYI, I've since upgrade my production site last week to Drupal 11 and this module is working great with these patches applied!
Comment #23
tbadaczewski commentedComment #24
abhineshTested and working fine with drupal 11.For now, I'm marking this issue as RTBC, for visibility.
Comment #25
abhineshComment #27
larowlanCommitted that to 2x thanks!
Comment #28
larowlanI cut a 2.0.0-rc7 tag with this
Comment #29
tbadaczewski commentedI'm so pumped that this made it to a release candidate! Thanks @larowlan!
Comment #30
larowlanAll you mate 🙌 thanks again
Comment #31
abhineshHi,
Still I see core_version_requirement: ^9 || ^10 in the info.yml that needs to be changed.
Comment #32
larowlanHi @abhinesh could you open an MR for that? thanks!
Comment #34
abhineshHi @larowlan,
Done, waiting for the new release.
Comment #35
abhineshComment #37
larowlanThanks, will cut another release