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

21.x pull in 21.3 commits #3538

Merged
merged 116 commits into from
Mar 19, 2024
Merged

21.x pull in 21.3 commits #3538

merged 116 commits into from
Mar 19, 2024

Conversation

dondonz
Copy link
Member

@dondonz dondonz commented Mar 19, 2024

This brings up the 21.x branch up to date with the last commit included in the 21.3 release, which was 42efd9b2 on master 42efd9b

You can verify this PR correctly pulls in all master commits up to git tag 21.3 by comparing the last commit on this branch vs the 21.3 commit on master
https://github.com/graphql-java/graphql-java/compare/42efd9b2..a79bebf

This PR is necessary because we previously released 21.3 off the master branch

bbakerman and others added 30 commits February 25, 2022 18:54
Use the non deprecated method in the example.
Add max depth option to ExecutableNormalizedOperationFactory
…now in valueresolver - with tests from spec
Signed-off-by: Arthur Chan <arthur.chan@adalogics.com>
dondonz and others added 28 commits September 12, 2023 06:18
Previously, the graphql-java build would always produce a new version
number based on the current date and time in local development. Because
the version number would always be different between 2 Gradle
invocations, some tasks, such as `javadoc` or `jar` could never be
cached because they depend on the version number.

With this patch, the version number will no longer include the date and
time when the Git workspace is clean, because the commit hash is
sufficient to uniquely identify the state of the workspace. This allows
the tasks that depend on the version number to be properly cached.
Previously, the cache key of the antlr task would be computed using
(among other things) the absolute paths of its input files. Because the
absolute paths were part of the cache key, the build cache would rarely
be hit.

With this patch, the task is configured to use relative paths
when computing the cache key.
…tion result in order to enforce directives in schema diff
Allow schema diff to use SDL document to enforce directives
…location-of-a-schema-elk

The ability to get the source location of a schema element
Bumps [com.fasterxml.jackson.core:jackson-databind](https://github.com/FasterXML/jackson) from 2.15.2 to 2.15.3.
- [Commits](https://github.com/FasterXML/jackson/commits)

---
updated-dependencies:
- dependency-name: com.fasterxml.jackson.core:jackson-databind
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
…erxml.jackson.core-jackson-databind-2.15.3

Bump com.fasterxml.jackson.core:jackson-databind from 2.15.2 to 2.15.3
…lds-aliaes-should-be-prevented

Issue 3332 - overlapping aliases should be prevented
…tives

#3267 clear directives schema usage bug fix
…locking

removed synchronised from code base as much as possible for VT
…tch_operation_to_schema_mismatch

A test to show that validation rules do not catch a mutation query to schema mismatch
…_validate-catch_operation_to_schema_mismatch

Revert "A test to show that validation rules do not catch a mutation query to schema mismatch"
…l-in-21.3-commits

# Conflicts:
#	build.gradle
#	src/test/groovy/graphql/introspection/IntrospectionTest.groovy
#	src/test/groovy/graphql/schema/idl/SchemaPrinterTest.groovy
@dondonz dondonz merged commit 5876cc8 into 21.x Mar 19, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet