diff --git a/graphql-java-20.2.tar.gz b/graphql-java-20.2.tar.gz
deleted file mode 100644
index 1ec242b..0000000
--- a/graphql-java-20.2.tar.gz
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:ae7eae6b5fc87a77f18f48c0b78231d202dd78ace79278c7d9d6bbec282822b9
-size 2083643
diff --git a/graphql-java-20.2.pom b/graphql-java-21.0.pom
similarity index 96%
rename from graphql-java-20.2.pom
rename to graphql-java-21.0.pom
index 0bc8935..28a8e03 100644
--- a/graphql-java-20.2.pom
+++ b/graphql-java-21.0.pom
@@ -3,7 +3,7 @@
4.0.0com.graphql-javagraphql-java
- 20.2
+ 21.0com.graphql-java
@@ -20,7 +20,7 @@
org.slf4jslf4j-api
- 1.7.35
+ 2.0.7runtime
diff --git a/graphql-java-21.0.tar.gz b/graphql-java-21.0.tar.gz
new file mode 100644
index 0000000..1fdb7a3
--- /dev/null
+++ b/graphql-java-21.0.tar.gz
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:782b6f6e5e98d2427e5a90cf439323dd20abdd8e6b9f4d15fa69434acaa761fa
+size 2109945
diff --git a/graphql-java.changes b/graphql-java.changes
index 3a7bf52..06a7f4b 100644
--- a/graphql-java.changes
+++ b/graphql-java.changes
@@ -1,3 +1,182 @@
+-------------------------------------------------------------------
+Fri Jul 14 13:48:23 UTC 2023 - Anton Shvetz
+
+- Update to v21.0
+ * Breaking Changes
+ + Upgraded to Java 11. graphql-java now requires Java 11 as a
+ minimum version. See the blog announcing the change. For
+ those who need time to upgrade to Java 11, keep in mind we
+ will support graphql-java 20.x (with Java 8) for a short
+ period as per our release policy. If you are wondering why we
+ are not on a later version, graphql-java has always been
+ conservative on its base JVM version to allow the widest
+ possible set of consumers.
+ + Reverted stricter scalar parseValue coercion, added
+ monitoring and interceptor callback. v20.0 introduced a
+ stricter set of scalar parseValue coercions - for example
+ previously an Integer would accept a string if it parsed into
+ a number but that was removed and a more strict system was
+ put in place. While technically more correct, and consistent
+ with the graphql-js reference implementation, in practice
+ this proved problematic for some consumers. So this more
+ stricter parseValue coercion was reverted in v20.3. We would
+ like to re-introduce this more strict scalar parseValue
+ conversion in the future and to that end we have introduced a
+ graphql.execution.values.InputInterceptor callback that
+ allows you to observe what values you are receiving and
+ potentially do special tweaking of those values. A
+ graphql.execution.values.legacycoercing.LegacyCoercingInputInterceptor
+ implementation will convert old less strict values into then
+ more strict values for example. If you had problems with
+ scalar values we urge you to use the new InputInterceptor to
+ learn what less strict values are coming into your systems
+ and fix them up. That way, when a future version
+ re-introduces the more strict (and more correct) coercion
+ then you will be prepared.
+ + Static recordLike() methods no longer supported. In v20, the
+ PropertyDataFetcher would read property values from
+ recordLike() methods on objects even if they were static
+ methods. This caused problems for some users and after
+ considering how to fix it and talking to some our major
+ consumers like the Spring team, we decided to remove this
+ behavior. On balance we think this will lead to a better
+ outcome over the long term. This is a breaking change for
+ those who might have relied on a static recordLike() method
+ being called for a property.
+ * Removal of old deprecated methods and classes
+ + The following PRs removed old deprecated methods and class.
+ The changes are breaking ones but these have been deprecated
+ for a long time.
+ ~ #3232
+ ~ #3231
+ + Other small breaking changes. A very minor breaking change is
+ that graphql.execution.ExecutionStrategy had a protected
+ method protected Iterable