Bump io.github.deweyjose:graphqlcodegen-maven-plugin from 1.61.5 to 3.10.0 in /backend

[dependabot]

Bumps io.github.deweyjose:graphqlcodegen-maven-plugin from 1.61.5 to 3.10.0.

Release notes

Sourced from io.github.deweyjose:graphqlcodegen-maven-plugin's releases.

graphqlcodegen-maven-plugin-3.10.0

Highlights

• schemaJarFilesFromDependencies now supports classifiers (#351, thanks @​RienderieN) — reference a classified schema jar directly:

<schemaJarFilesFromDependencies>
  <param>com.example:my-schemas:schema:1.0.0</param>
</schemaJarFilesFromDependencies>

The coordinate form is groupId:artifactId:[classifier:]version — the classifier is optional, so existing 3-part refs keep working.

• Fixed: SNAPSHOT coordinates never matched (#351) — matching now uses the artifact's base version, so com.example:foo:1.0.0-SNAPSHOT correctly matches an artifact resolved to a timestamped build such as 1.0.0-20260101.120000-3. Previously these silently failed to match.

• Fixed: non-deterministic jar selection (#351) — when a project depended on both a classified and an unclassified artifact at the same groupId:artifactId:version, matching could pick either one depending on iteration order, so codegen could read the wrong jar between builds.

• Unmatched coordinates now log a warning (#351) — a coordinate in schemaJarFilesFromDependencies that matches no dependency was previously ignored in silence; it now emits a WARN naming the coordinate.

⚠️ Behavior change

A 3-part groupId:artifactId:version ref now matches only artifacts with no classifier. Previously it matched any artifact at that coordinate, ignoring the classifier — the source of the non-deterministic selection bug above.

If your only dependency at that coordinate carries a classifier and you wrote the ref without it, you were matching by accident and will now be skipped. The fix is to add the classifier to the ref; the new WARN will name any coordinate that stops matching.

What's Changed

• Bump junit.version from 6.0.3 to 6.1.2 by @​dependabot[bot] in deweyjose/graphqlcodegen#345
• Bump com.fasterxml.jackson.core:jackson-databind from 2.15.0 to 2.22.0 by @​dependabot[bot] in deweyjose/graphqlcodegen#330
• Modernize examples: Spring Boot 4.0.7 + DGS framework 12.0.1 + JUnit 6 by @​dependabot[bot] in deweyjose/graphqlcodegen#342
• fix schemaJarFilesFromDependencies artifactRef version matching and add artifact classifier support by @​RienderieN in deweyjose/graphqlcodegen#351

New Contributors

• @​RienderieN made their first contribution in deweyjose/graphqlcodegen#351

Full Changelog: deweyjose/graphqlcodegen@graphqlcodegen-maven-plugin-3.9.0...graphqlcodegen-maven-plugin-3.10.0

graphqlcodegen-maven-plugin-3.9.0

Highlights

• graphql-dgs-codegen-core 8.5.0 → 8.6.0 (#337, #338)
• New jacksonVersions parameter — choose the Jackson major version(s) targeted by generated code: 2 (com.fasterxml.jackson, the default) and/or 3 (tools.jackson). Currently affects the builder deserialization annotations (@JsonDeserialize / @JsonPOJOBuilder) on Kotlin classes generated with generateKotlinNullableClasses. Existing builds are unaffected by default.

<jacksonVersions>
  <jacksonVersion>3</jacksonVersion>
</jacksonVersions>

• New kotlin-jackson3 example module proving Jackson 3 deserialization of generated Kotlin end to end in CI.

... (truncated)

Commits

• c8c2a90 Bump version to 3.10.0
• e146e51 Merge pull request #351 from RienderieN/main
• 68bcdf9 remove jakarta nullable transifive import
• da3870b Fix PR review and update github workflows actions/setup-XXX to v6
• 90a2721 fix schemaJarFilesFromDependencies artifactRef version matching and add artif...
• 04f823d Fix coverage-badge push race between concurrent workflow runs
• 6aecedd Merge pull request #342 from deweyjose/dependabot/maven/com.netflix.graphql.d...
• 3163d71 Modernize examples reactor for DGS 12: Spring Boot 4.0.7, JUnit 6, managed Ja...
• 2b6e1da Merge main (3.9.0, DGS 8.6.0, kotlin-jackson3 example, junit/jackson plugin b...
• 0117a07 Merge pull request #330 from deweyjose/dependabot/maven/com.fasterxml.jackson...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)