Skip to content

Commit 259fa7b

Browse files
committed
2.0.17
1 parent 3d247bf commit 259fa7b

2 files changed

Lines changed: 50 additions & 1 deletion

File tree

CHANGELOG.md

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,33 @@
1010

1111
### Bug fixes
1212

13+
# 2.0.17 (14 February 2022)
14+
15+
### Breaking changes
16+
17+
- Enums: require at least one value in a definition #4278
18+
19+
### New features
20+
21+
- Enums: support `nil` as a Ruby value #4311
22+
23+
### Bug fixes
24+
25+
- Don't re-encode ASCII strings as UTF-8 #4319, #4343
26+
- Fix `handle_or_reraise` with arguments validation #4341
27+
- Performance: Remove error handling from `Lazy#value` (unused) #4335
28+
- Performance: Use codegen instead of dynamic dispatch in `Language::Visitor` and `Analysis::AST::Visitor` #4338
29+
- Performance: reduce indirection in `#introspection?` and `#graphql_name` #4327
30+
- Clean up thread-based state after running queries #4329
31+
- JSON types: don't pass raw NullValue AST nodes to `coerce_input` #4324, #4320
32+
- Performance: reduce `.is_a?` calls at runtime #4318
33+
- Performance: cache interface type memberships #4311
34+
- Performance: eagerly define some type instance variables for Shape friendliness #4300 #4295 #4297
35+
- Performance: reduce argument overhead, don't scope introspection by default, reduce duplicate call to Field#type #4317
36+
- Fix anonymous `eval` usage #4288
37+
- Authorization: fix field auth fail call after lazy #4289
38+
- Subscriptions: fix `loads:`/`as:`
39+
1340
# 2.0.16 (19 December 2022)
1441

1542
### Breaking changes
@@ -223,6 +250,28 @@ Oops, this version was accidentally released to RubyGems as "2.10.0". I yanked i
223250
- __None, ideally.__ If you have an application that ran without warnings on v1.13, you should be able to update to 2.0.0 without a hitch. If this isn't the case, please [open an issue](https://github.com/rmosolgo/graphql-ruby/issues/new?template=bug_report.md&title=[2.0%20update]%20describe%20your%20problem) and let me know what happened! I plan to maintain 1.13 for a while in order to ensure a smooth transition.
224251
- But, many legacy code components were removed, so if there are any more references to those, there will be name errors! See #3729 for a list of removed components.
225252

253+
# 1.13.19 (2 February 2023)
254+
255+
### Bug fixes
256+
257+
- Performance: don't re-encode schema member names #4323
258+
- Performance: fix a duplicate field.type call #4316
259+
- Performance: use `scope: false` for introspection types #4315
260+
- Performance: improve argument coercion and validation #4312
261+
- Performance: improve interface type membership lookup #4309
262+
263+
# 1.13.18 (10 January 2023)
264+
265+
### New Features
266+
267+
- `hash_key:`: perform `[...]` lookups even when the underlying object isn't a Hash #4286
268+
269+
# 1.13.17 (17 November 2022)
270+
271+
### Bug fixes
272+
273+
- Handle ExecutionErrors from prepare hooks when calculating complexity #4248
274+
226275
# 1.13.16 (31 August 2022)
227276

228277
### New Features

lib/graphql/version.rb

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
11
# frozen_string_literal: true
22
module GraphQL
3-
VERSION = "2.0.16"
3+
VERSION = "2.0.17"
44
end

0 commit comments

Comments
 (0)