{"diffoscope-json-version": 1, "source1": "/srv/reproducible-results/rbuild-debian/r-b-build.VMInz5Jq/b1/ruby-graphql_1.11.4-1_i386.changes", "source2": "/srv/reproducible-results/rbuild-debian/r-b-build.VMInz5Jq/b2/ruby-graphql_1.11.4-1_i386.changes", "unified_diff": null, "details": [{"source1": "Files", "source2": "Files", "unified_diff": "@@ -1,2 +1,2 @@\n \n- d945161a7abe3ad2642d4c342abbff2d 236304 ruby optional ruby-graphql_1.11.4-1_all.deb\n+ f0504f8e0a727184aa48245e356c4ac0 231880 ruby optional ruby-graphql_1.11.4-1_all.deb\n"}, {"source1": "ruby-graphql_1.11.4-1_all.deb", "source2": "ruby-graphql_1.11.4-1_all.deb", "unified_diff": null, "details": [{"source1": "file list", "source2": "file list", "unified_diff": "@@ -1,3 +1,3 @@\n -rw-r--r-- 0 0 0 4 2020-11-03 01:51:46.000000 debian-binary\n--rw-r--r-- 0 0 0 11000 2020-11-03 01:51:46.000000 control.tar.xz\n--rw-r--r-- 0 0 0 225112 2020-11-03 01:51:46.000000 data.tar.xz\n+-rw-r--r-- 0 0 0 11004 2020-11-03 01:51:46.000000 control.tar.xz\n+-rw-r--r-- 0 0 0 220684 2020-11-03 01:51:46.000000 data.tar.xz\n"}, {"source1": "control.tar.xz", "source2": "control.tar.xz", "unified_diff": null, "details": [{"source1": "control.tar", "source2": "control.tar", "unified_diff": null, "details": [{"source1": "./control", "source2": "./control", "unified_diff": "@@ -1,12 +1,12 @@\n Package: ruby-graphql\n Version: 1.11.4-1\n Architecture: all\n Maintainer: Debian Ruby Team \n-Installed-Size: 1538\n+Installed-Size: 1534\n Section: ruby\n Priority: optional\n Homepage: https://github.com/rmosolgo/graphql-ruby\n Description: GraphQL language and runtime for Ruby\n A plain-Ruby implementation of GraphQL.\n .\n Goals:\n"}, {"source1": "./md5sums", "source2": "./md5sums", "unified_diff": null, "details": [{"source1": "./md5sums", "source2": "./md5sums", "comments": ["Files differ"], "unified_diff": null}]}]}]}, {"source1": "data.tar.xz", "source2": "data.tar.xz", "unified_diff": null, "details": [{"source1": "data.tar", "source2": "data.tar", "unified_diff": null, "details": [{"source1": "file list", "source2": "file list", "unified_diff": "@@ -444,13 +444,13 @@\n -rw-r--r-- 0 root (0) root (0) 756 2020-11-03 01:51:46.000000 ./usr/lib/ruby/vendor_ruby/graphql/upgrader/schema.rb\n -rw-r--r-- 0 root (0) root (0) 70 2020-11-03 01:51:46.000000 ./usr/lib/ruby/vendor_ruby/graphql/version.rb\n -rw-r--r-- 0 root (0) root (0) 3636 2020-11-03 01:51:46.000000 ./usr/lib/ruby/vendor_ruby/graphql.rb\n drwxr-xr-x 0 root (0) root (0) 0 2020-11-03 01:51:46.000000 ./usr/share/\n drwxr-xr-x 0 root (0) root (0) 0 2020-11-03 01:51:46.000000 ./usr/share/doc/\n drwxr-xr-x 0 root (0) root (0) 0 2020-11-03 01:51:46.000000 ./usr/share/doc/ruby-graphql/\n -rw-r--r-- 0 root (0) root (0) 930 2020-11-03 01:51:46.000000 ./usr/share/doc/ruby-graphql/changelog.Debian.gz\n--rw-r--r-- 0 root (0) root (0) 5799 2020-08-25 14:24:39.000000 ./usr/share/doc/ruby-graphql/changelog.gz\n+-rw-r--r-- 0 root (0) root (0) 1445 2020-08-25 14:24:39.000000 ./usr/share/doc/ruby-graphql/changelog.gz\n -rw-r--r-- 0 root (0) root (0) 1504 2020-11-03 01:51:46.000000 ./usr/share/doc/ruby-graphql/copyright\n drwxr-xr-x 0 root (0) root (0) 0 2020-11-03 01:51:46.000000 ./usr/share/rubygems-integration/\n drwxr-xr-x 0 root (0) root (0) 0 2020-11-03 01:51:46.000000 ./usr/share/rubygems-integration/all/\n drwxr-xr-x 0 root (0) root (0) 0 2020-11-03 01:51:46.000000 ./usr/share/rubygems-integration/all/specifications/\n -rw-r--r-- 0 root (0) root (0) 26906 2020-11-03 01:51:46.000000 ./usr/share/rubygems-integration/all/specifications/graphql-1.11.4.gemspec\n"}, {"source1": "./usr/share/doc/ruby-graphql/changelog.gz", "source2": "./usr/share/doc/ruby-graphql/changelog.gz", "unified_diff": null, "details": [{"source1": "changelog", "source2": "changelog", "unified_diff": "@@ -1,709 +1,176 @@\n-# graphql-pro\n+# graphql-relay\n \n ### Breaking Changes\n \n ### Deprecations\n \n ### New Features\n \n ### Bug Fix\n \n-## 1.15.4 (28 July 2020)\n+## 0.12.0 (21 Jul 2016)\n \n-### New Features\n-\n-- Pundit: add `pundit_policy_class_for(object, context)` and `pundit_role_for(object, context)` for custom runtime lookups\n-\n-## 1.15.3 (17 July 2020)\n-\n-### Bug Fix\n-\n-- Subscriptions: don't send empty updates when subscriptions return `:no_update`\n-\n-## 1.15.2 (16 July 2020)\n-\n-### New Features\n-\n-- OperationStore: improve handling of archived operations in index views\n-\n-## 1.15.1 (16 July 2020)\n-\n-(Oops, bad release!)\n-\n-## 1.15.0 (15 July 2020)\n-\n-- OperationStore: Store & display `last_used_at` for operation store clients and operations. To upgrade, add the column to your ActiveRecord table:\n-\n- ```ruby\n- add_column :graphql_client_operations, :last_used_at, :datetime\n- ```\n-\n- (It works out-of-the-box with the Redis backend.)\n-\n- You can opt out of this feature by adding `use GraphQL::Pro::OperationStore, ... default_touch_last_used_at: false` to your schema setup.\n-\n-- OperationStore: Add archive/unarchive workflow for operations. To upgrade, add the column to your table:\n-\n- ```ruby\n- add_column :graphql_client_operations, :is_archived, :boolean, index: true\n- ```\n-\n- (It works out-of-the-box with the Redis backend.)\n-\n-- OperationStore: Fix indexing of enum values\n-\n-## 1.14.1 (29 June 2020)\n-\n-- CanCan: Accept `can_can_attribute:` configuration, which is passed as the third input to `.can?(...)`\n-\n-## 1.14.0 (13 June 2020)\n-\n-### New Features\n-\n-- Add PubnubSubscriptions\n-- Update subscription implementations to support `broadcast: true` when available\n-\n-### Bug Fix\n-\n-- More Ruby 2.7 warning fixes\n-\n-## 1.13.6 (8 June 2020)\n-\n-### Bug Fix\n-\n-- Return the proper `pageInfo` values when it's requested before `edges` or `nodes` (#2972)\n-\n-## 1.13.5 (11 May 2020)\n-\n-### Bug Fix\n-\n-- Fix some warnings on Ruby 2.7\n-\n-## 1.13.4 (17 Apr 2020)\n-\n-### Bug Fix\n-\n-- StableRelationConnection: properly return `hasNextPage: true` when `before` and `max_page_size` are used.\n-\n-## 1.13.3 (2 Apr 2020)\n-\n-### New Features\n-\n-- `GraphQL::Pro::OperationStore::Migration` can be used to copy persisted operations from one backend to another (eg, ActiveRecord to Redis). See the source file, `lib/graphql/pro/operation_store/migration.rb` for docs.\n-\n-## 1.13.2 (28 Mar 2020)\n-\n-### Deprecations\n-\n-- `GraphQL::Pro::Subscriptions` is deprecated; use `GraphQL::Pro::PusherSubscriptions` instead which works the same, but better (see below). This new name avoids confusion with the later-added `AblySubscriptions`.\n-\n-### New Features\n-\n-- `GraphQL::Pro::PusherSubscriptions` replaces `GraphQL::Pro::Subscriptions` and adds orphaned record cleanup. (No more dangling records in Redis.)\n-\n-## 1.13.1 (12 Mar 2020)\n-\n-- Use `nonce: true` when working with cursors in new stable connections\n-\n-## 1.13.0 (10 Feb 2020)\n-\n-### New Features\n-\n-- OperationStore supports a `redis:` backend\n-- OperationStore supports an arbitrary `backend_class:` for persistence operations\n-\n-### Bug Fix\n-\n-- Use a loop when clearing Redis subscription state to avoid large stack traces #2701\n-- Handle empty subscription keys when publishing updates #2061\n-\n-## 1.12.2 (22 Jan 2020)\n-\n-### Bug Fix\n-\n-- Improve backwards compat with OperationStore (Improve adding `.tracer`, use `.graphql_name` when indexing)\n-\n-## 1.12.1 (20 Jan 2020)\n-\n-### Bug Fix\n-\n-- Fix OperationStore on class-based schemas with query instrumenters that use the query string\n-\n-## 1.12.0 (20 Jan 2020)\n-\n-### Deprecations\n-\n-- `GraphQL::Pro::Monitoring` is deprecated; see Tracing for a replacement: https://graphql-ruby.org/queries/tracing.html\n-- `GraphQL::Pro::Repository` is deprecated; see OperationStore for a replacement: https://graphql-ruby.org/operation_store/overview.html\n-\n-### New Features\n-\n-- New stable connection support based on GraphQL-Ruby 1.10's new pagination implementation. New classes provide better handling of `NULL` values in order-by columns and they can be applied on a field-by-field basis(`GraphQL::Pro::SqliteStableRelationConnection`, `GraphQL::Pro::MySQLStableRelationConnection`, `GraphQL::Pro::PostgresStableRelationConnection`).\n-\n-### Bug Fix\n-\n-- Add the Access query analyzer to class-based schemas\n-\n-## 1.11.0 (10 Oct 2019)\n-\n-### New Features\n-\n-- Forwards-compatibility for graphql 1.10.0\n-- Support 1.10.0.pre1's input object argument `loads:` authorization\n-\n-## 1.10.8 (8 Oct 2019)\n-\n-### Bug Fix\n-\n-- Continue authorizing input object arguments\n-- Use millisecond-aware string format for datetimes in cursors\n-\n-## 1.10.7 (22 Jul 2019)\n-\n-### Bug Fix\n-\n-- Support multiple subscriptions in one document\n-\n-## 1.10.6 (27 Jun 2019)\n-\n-### New Features\n-\n-- Support custom `#can_can_ability` methods on query context for CanCanIntegration\n-- Support custom `#pundit_user` method on query context for PunditIntegration\n-\n-### Bug Fix\n-\n-- Fix off-by-one error when paginating backwards from the last item in a stable relation connection\n-\n-## 1.10.5 (11 May 2019)\n-\n-### New Features\n-\n-- Include expected HMAC digest in OperationStore debug output\n-\n-## 1.10.4 (26 Mar 2019)\n-\n-### Bug Fix\n-\n-- Include content-length and content-type headers in OperationStore JSON responses\n-\n-## 1.10.3 (13 Mar 2019)\n-\n-### Bug Fix\n-\n-- Support stable connections ordered by Arel SQL literals\n-\n-## 1.10.2 (11 Mar 2019)\n-\n-### Bug Fix\n-\n-- Support stable connections on realized views (which don't have primary keys)\n-\n-## 1.10.1 (8 Mar 2019)\n-\n-### Bug Fix\n-\n-- Pundit integration: support `pundit_policy_class` String names when scoping connections\n-\n-## 1.10.0 (5 Mar 2019)\n-\n-### New Features\n-\n-- Add `GraphQL::Pro::Defer`, implementing `@defer` for streaming responses\n-\n-## 1.9.13 (4 Mar 2019)\n-\n-### Bug Fix\n-\n-- Pundit integration: correctly authorize fields when Query root is nil\n-\n-## 1.9.12 (22 Feb 2019)\n-\n-### Bug Fix\n-\n-- Pundit integration: use overriden `pundit_policy_class` for scoping and mutation authorization\n-\n-## 1.9.11 (20 Feb 2019)\n-\n-### Bug Fix\n-\n-- Pundit integration: Fields use the owner's configured `pundit_policy_class` if there is one\n-- Pundit integration: avoid conflicts with `#initialize` for schema classes that don't need it\n-\n-## 1.9.10 (19 Feb 2019)\n-\n-### Bug Fix\n-\n-- Support inheritance with `pundit_policy_class(...)`\n-\n-## 1.9.9 (13 Feb 2019)\n-\n-### New Features\n-\n-- Support `pundit_policy_class(...)` and `pundit_policy_class:` to manually specify a class or class name.\n-\n-## 1.9.8 (30 Jan 2019)\n-\n-### New Features\n-\n-- Inject `context` into policy lookup hooks instead of just the user\n-\n-## 1.9.7 (30 Jan 2019)\n-\n-### New Features\n-\n-- Extract `pundit_policy` and `scope_by_pundit_policy` hooks for user override\n-\n-## 1.9.6 (18 Jan 2019)\n-\n-### Bug Fix\n-\n-- Properly render subscription context in dashboard\n-\n-## 1.9.5 (14 Jan 2019)\n-\n-## Bug Fix\n-\n-- Don't pass arrays to Pundit scopes (fixes https://github.com/rmosolgo/graphql-ruby/issues/2008)\n-\n-## 1.9.4 (11 Jan 2019)\n-\n-## Bug Fix\n-\n-- Prepare for future compat with graphql-ruby 1.9\n-\n-## 1.9.3 (3 Dec 2018)\n-\n-### Bug Fix\n-\n-- Include table name when adding a default order-by-id to ActiveRecord Relations\n-- Raise if a required cursor attribute is missing\n-- Improve `rake routes` output for operation store endpoint\n-- Support already-parsed queries in subscription RedisStorage\n-\n-## 1.9.2 (2 Nov 2018)\n-\n-### Bug Fix\n-\n-- Derp, remove the dummy app's `.log` files from the gem bundle\n-- Fix ordering bug when a SQL function call doesn't have an explicit order\n-\n-## 1.9.1 (1 Nov 2018)\n-\n-### Bug Fix\n-\n-- Fix Pusher reference in AblySubscriptions\n-\n-## 1.9.0 (27 Oct 2018)\n-\n-### New Features\n-\n-- Add `GraphQL::Pro::AblySubscriptions` for GraphQL subscriptions over Ably.io transport\n-\n-## 1.8.2 (22 Oct 2018)\n-\n-### Bug Fix\n-\n-- Support `NULLS LAST` in stable cursors\n-\n-## 1.8.1 (16 Oct 2018)\n-\n-### Bug Fix\n-\n-- Improve operation store models to work when `config.active_record.primary_key_prefix_type` is set\n-\n-## 1.8.0 (11 Oct 2018)\n-\n-### New Features\n-\n-- Support Rails 3.2 with OperationStore\n-- Use `.select` to filter items in CanCanIntegration\n-\n-### Bug Fix\n-\n-- Properly send an _ability_ and the configured `can_can_action` to `.accessible_by`\n-- Use a string (not integer) for `Content-Length` header in the dashboard\n-\n-## 1.7.13 (2 Oct 2018)\n+### Breaking Changes\n \n-### Breaking Change\n+- Don't cache a global node identification config #51\n \n-- `PunditIntegration`: instead of raising `MutationAuthorizationFailed` when an argument fails authorization, it will send a `GraphQL::UnauthorizedError` to your `Schema.unauthorized_object` hook. (This is what all other authorization failures do.) To retain the previous behavior, in your base mutation, add:\n+ To migrate, assign your node identification helper to the schema:\n \n ```ruby\n- def unauthorized_by_pundit(owner, value)\n- # Raise a runtime error to halt query execution\n- raise \"#{value} failed #{owner}'s auth check\"\n- end\n+ NodeIdentification = GraphQL::Relay::GlobalNodeIdentification.define { ... }\n+ MySchema.node_identification = NodeIdentification\n ```\n \n- Otherwise, customize the handling of this behavior with `Schema.unauthorized_object`.\n-\n-### Bug Fix\n-\n-- Auth: mutation arguments which have authorization constraints but _don't_ load an object from the database will have _mutation instance_ passed to the auth check, not the input value.\n-\n-## 1.7.12 (29 Aug 2018)\n-\n ### New Features\n \n-- Add `GraphQL::Pro::CanCanIntegration` which leverages GraphQL-Ruby's built-in auth\n-\n-## 1.7.11 (21 Aug 2018)\n+- Support lazy definition blocks from graphql-ruby 0.17\n+- Add `startCursor` and `endCursor` to `PageInfo` #60\n \n ### Bug Fix\n \n-- `PunditIntegration`: Don't try to authorize loaded objects when they're `nil`\n-\n-## 1.7.10 (10 Aug 2018)\n-\n-### New Features\n-\n-- Update `PunditIntegration` for arguments, unions, interfaces and mutations\n+- Support `field:` keyword for connection helper #58\n \n-## 1.7.9 (9 Aug 2018)\n+## 0.11.2 (6 Jul 2016)\n \n ### New Features\n \n-- Add a new `PunditIntegration` which leverages the built-in authorization methods\n-\n-## 1.7.8 (10 July 2018)\n-\n-### Bug Fix\n-\n-- Authorization: fix scoping lists of abstract type when there's no `#scope` method on the strategy\n+- Include description for built-in objects #55\n \n-## 1.7.7 (10 May 2018)\n+## 0.11.1 (24 Jun 2016)\n \n ### Bug Fix\n \n-- Fix ordering of authorization field instrumenter (put it at the end, not the beginning of the list)\n+- Correctly pass parent object to Connections #53\n \n-## 1.7.6 (2 May 2018)\n-\n-### New Features\n-\n-- Authorization: Add `view`/`access`/`authorize` methods to `GraphQL::Schema::Mutation`\n-\n-## 1.7.5 (19 Apr 2018)\n-\n-### New Features\n-\n-- Authorization: when a `fallback:` configuration is given, apply it to each field which doesn't have a configuration of its own or from its return type. _Don't_ apply that configuration at schema level (it's applied to each otherwise uncovered field instead).\n-\n-## 1.7.4 (16 Apr 2018)\n-\n-### New Features\n-\n-- Support Mongoid::Criteria in authorization scoping\n-\n-## 1.7.3 (12 Apr 2018)\n-\n-### Bug Fix\n-\n-- Fix authorization code for when `ActiveRecord` is not defined\n-\n-## 1.7.2 (10 Apr 2018)\n-\n-### Bug Fix\n-\n-- Use a more permissive regexp (`/^\\s*((?:[a-z._]+)\\(.*\\))\\s*(asc|desc)?\\s*$/im`) to parse SQL functions\n-\n-## 1.7.1 (4 Apr 2018)\n-\n-### Bug Fix\n-\n-- Fix route helpers to support class-based schemas\n-\n-## 1.7.0 (25 Mar 2018)\n-\n-### New Features\n-\n-- Support `1.8-pre` versions of GraphQL-Ruby\n-\n-### Bug Fix\n-\n-- Fix OperationStore when other query instrumenters need `.query_string`\n-\n-## 1.6.5 (7 Feb 2018)\n-\n-### Bug Fix\n-\n-- Support `LEAST(...)` in stable cursors\n-\n-## 1.6.4 (7 Feb 2018)\n-\n-### Bug Fix\n-\n-- Support `CASE ... END` in stable cursors\n-\n-## 1.6.3 (26 Jan 2018)\n-\n-### Bug Fix\n-\n-- Support `FIELD(...)` in stable cursors\n-\n-## 1.6.2 (13 Jan 2018)\n-\n-### Bug Fix\n-\n-- Improve detection of `OperationStore` for the dashboard\n-- Serve `Content-Type` and `Content-Length` headers with dashboard pages\n-- Better `Dashboard#inspect` for Rails routes output\n-- Use a string to apply order-by-primary-key for better Rails 3 support\n-\n-## 1.6.1 (22 Nov 2017)\n-\n-### New Features\n-\n-- Support `composite_primary_keys` gem\n-\n-## 1.6.0 (13 Nov 2017)\n+## 0.11.0 (19 Jun 2016)\n \n ### Breaking Changes\n \n-- `GraphQL::Pro::UI` renamed to `GraphQL::Pro::Dashboard`\n-\n-### Deprecations\n-\n-- Routing method `.ui` was renamed to `.dashboard`\n-\n-### New Features\n-\n-- Added `GraphQL::Pro::Subscriptions`\n-- Added subscriptions component to Dashboard\n-\n-## 1.5.9 (10 Oct 2017)\n-\n-### Bug Fix\n+- `BaseType.define_connection` no longer caches the result to use as the default `BaseType.connection_type`. Now, store the result of `.define_connection` in a variable and pass that variable into the schema:\n \n-- Don't crash when scoping lists of abstract types with Pundit\n+ ```ruby\n+ # Capture the returned type:\n+ SomethingCustomConnectionType = SomethingType.define_connection { ... }\n \n-## 1.5.8 (2 Oct 2017)\n+ DifferentThingType = GraphQL::ObjectType.define do\n+ # And pass it to the connection helper:\n+ connection :somethings, SomethingCustomConnectionType\n+ end\n+ ```\n \n ### New Features\n \n-- Use `authorize(:pundit, namespace: )` to lookup policies in a namespace instead of the global namespace.\n+- Support for custom edge types / classes #50\n+- Support for multiple connection classes #50\n \n-### Bug Fix\n+## 0.10.0 (31 May 2016)\n \n-- Introspection data is allowed through `fallback:` `authorize:` and `access:` filters. (It can be hidden with a `view:` filter.)\n+### New Feature\n \n-## 1.5.7 (20 Sept 2017)\n+- Support `graphql` 0.14.0 #47\n \n ### Bug Fix\n \n-- Properly return `nil` when a list of authorized objects returns `nil`\n-\n-## 1.5.6 (19 Sept 2017)\n+- Use strings as argument names, not symbols #47\n \n-### New Features\n-\n-- Add `authorization(..., operation_store:)` option for authorizing operation store requests\n+## 0.9.5\n \n-## 1.5.5 (18 Sept 2017)\n+### New Feature\n \n-### New Features\n+- Root `id` field may have a description #43\n \n-- Support `ConnectionType.bidrectional_pagination?` in stable RelationConnection\n-\n-## 1.5.4 (18 Sept 2017)\n+## 0.9.4 (29 Apr 2016)\n \n ### Bug Fix\n \n-- Fix load issue when Rails is not present\n+- Fix Node interface to support GraphQL 0.13.0+\n \n-## 1.5.3 (4 Sept 2017)\n+## 0.9.2 (29 Apr 2016)\n \n ### Bug Fix\n \n-- Fix OperationStore views on PostgresQL\n-- Fix stable cursors when joined tables have the same column names\n-\n- __Note:__ This is implemented by adding extra fields to the `SELECT`\n- clause with aliases like `cursor_#{idx}`, so you'll notice this in your\n- SQL logs.\n+- Fix Node interface when type_from_object returns nil\n \n-## 1.5.2 (4 Aug 2017)\n+## 0.9.1 (6 Apr 2016)\n \n ### Bug Fix\n \n-- Bump `graphql` dependency to `1.6`\n+- Respond to connection fields without any pagination arguments\n+- Limit by `max_page_size` even when no arguments are present\n \n-## 1.5.1 (2 Aug 2017)\n+## 0.9.0 (30 Mar 2016)\n \n-### New Features\n+### Breaking change\n \n-- Routing extensions moved to `using GraphQL::Pro::Routes`\n-\n-### Deprecations\n+- Remove the `order` argument from connection fields. This isn't part of the spec and shouldn't have been there in the first place!\n \n-- Deprecate `using GraphQL::Pro`, move extensions to `GraphQL::Pro::Routes`\n+ You can implement this behavior with a custom argument, for example:\n \n-## 1.5.0 (31 Jul 2017)\n-\n-### New Features\n-\n-- Add `GraphQL::Pro::OperationStore` for persisted queries with Rails\n-\n-## 1.4.8 (14 Jul 2017)\n+ ```ruby\n+ field :cities, CityType.connection_type do\n+ argument :order, types.String, default_value: \"name\"\n+ resolve ->(obj, args, ctx) {\n+ obj.order(args[:order])\n+ }\n+ end\n+ ```\n \n ### Bug Fix\n \n-- Update `authorization` to use type-level `resolve_type` hooks\n+- Include the MIT license in the project's source\n \n-## 1.4.7 (13 Jul 2017)\n+## 0.8.1 (22 Mar 2016)\n \n ### Bug Fix\n \n-- Update authorization instrumentation for `graphql >= 1.6.5`\n+- Accept description for Mutations\n \n-## 1.4.6 (6 Jul 2017)\n+## 0.8.0 (20 Mar 2016)\n \n-### Bug Fix\n+### New Feature\n \n-- Fix typo in RelationConnection source\n+- Accept configs for `to_global_id` and `from_global_id`\n+- Support `graphql` 0.12+\n \n-## 1.4.5 (6 Jul 2017)\n+## 0.7.1 (29 Feb 2016)\n \n ### Bug Fix\n \n-- Correctly fall back to offset-based cursors with `before:` argument\n+- Limit the `count(*)` when testing next page with ActiveRecord #28\n \n-## 1.4.4 (15 Jun 2017)\n+## 0.7.0 (20 Feb 2016)\n \n-### New Features\n+### New Feature\n \n-- Add `Schema#unauthorized_object(obj, ctx)` hook for failed runtime checks\n+- `max_page_size` option for connections\n+- Support ActiveSupport 5.0.0.beta2\n \n-### Bug Fix\n-\n-- Prevent usage of `parent_role:` with `view:` or `access:` (since parent role requires a runtime check)\n-- Fix versioned, encrypted cursors with 16-byte legacy cursors\n-\n-## 1.4.3 (13 Jun 2017)\n-\n-### New Features\n-\n-- `OrderedRelationConnection` supports ordering by joined fields\n+## 0.6.2 (11 Feb 2016)\n \n ### Bug Fix\n \n-- Update auth plugin for new Relay instrumenters\n-- `Pro::Encoder` supports `encoder(...)` as documented\n+- Correctly cast values from connection cursors #21\n+- Use class _name_ instead of class _object_ when finding a connection implementation (to support Rails autoloading) #16\n \n-## 1.4.2 (2 May 2017)\n+## 0.6.1 (14 Dec 2015)\n \n ### Bug Fix\n \n-- Fix compatibility of `RelationConnection` and `RangeAdd` helper\n-\n-## 1.4.1 (19 Apr 2017)\n-\n-### New Features\n-\n-- Add `:datadog` monitoring\n-\n-## 1.4.0 (19 Apr 2017)\n-\n-### New Features\n-\n-- `ActiveRecord::Relation`s can be scoped by Pundit `Scope`s, CanCan `accessible_by`, or custom strategy's `#scope(gate, relation)` methods\n-- Default authorization configuration can be provided with `authorization(..., fallback: { ... })`\n-- Authorization's `:current_user` key can be customized with `authorization(..., current_user: ...)`\n-\n-## 1.3.0 (7 Mar 2017)\n+- Stringify `id` when passed into `to_global_id`\n \n-### New Features\n-\n-- Serve static, persisted queries with `GraphQL::Pro::Repository`\n-\n-## 1.2.3 (2 May 2017)\n-\n-### Bug Fix\n-\n-- Fix compatibility of `RelationConnection` and `RangeAdd` helper\n+## 0.6.0 (11 Dec 2015)\n \n-## 1.2.2 (6 Mar 2017)\n+### Breaking Change\n \n-### Bug Fix\n+- `GlobalNodeIdentification#object_from_id(id, ctx)` now accepts context as the second argument #9\n \n-- Raise `GraphQL::Pro::RelationConnection::InvalidRelationError` when a grouped, unordered relation is returned from a field. (This relation can't be stably paginated.)\n+## 0.5.1 (11 Dec 2015)\n \n-## 1.2.1 (3 Mar 2017)\n \n-### New Features\n+### Feature\n \n-- Formally support ActiveRecord `>= 4.1.0`\n+- Allow custom UUID join string #15\n \n ### Bug Fix\n \n-- Support grouped relations in `GraphQL::Pro::RelationConnection`\n-\n-## 1.2.0 (1 Mar 2017)\n-\n-### New Features\n-\n-- Authorize fields based on their parent object, for example:\n-\n- ```ruby\n- AccountType = GraphQL::ObjectType.define do\n- name \"Account\"\n- # This field is visible to all users:\n- field :name, types.String\n- # This is only visible when the current user is an `:owner`\n- # of this account\n- field :account_balance, types.Int, authorize: { parent_role: :owner }\n- end\n- ```\n-\n-## 1.1.1 (22 Feb 2017)\n-\n-### Bug Fixes\n-\n-- Fix monitoring when `Query#selected_operation` is nil\n-\n-## 1.1.0 (9 Feb 2017)\n-\n-### New Features\n-\n-- Add AppSignal monitoring platform\n-- Add type- and field-level opting in and opting out of monitoring\n-- Add `monitor_scalars: false` to skip monitoring on scalars\n-\n-### Bug Fixes\n-\n-- Fix `OrderedRelationConnection` when neither `first` nor `last` are provided (use `max_page_size` or don't limit)\n-\n-## 1.0.4 (23 Jan 2017)\n-\n-### Bug Fixes\n-\n-- `OrderedRelationConnection` exposes more metadata methods: `parent`, `field`, `arguments`, `max_page_size`, `first`, `after`, `last`, `before`\n-\n-## 1.0.3 (23 Jan 2017)\n-\n-### Bug Fixes\n-\n-- When an authorization check fails on a non-null field, propagate the null and add a response to the errors key (as if the field had returned null). It previously leaked the internal symbol `__graphql_pro_access_not_allowed__`.\n-- Apply a custom Pundit policy even when the value isn't `nil`. (It previously fell back to `Pundit.policy`, skipping a `pundit_policy_name` configuration.)\n-\n-## 1.0.2\n-\n-### Bug Fixes\n-\n-- `OrderedRelationConnection` exposes the underlying relation as `#nodes` (like `RelationConnection` does), supporting custom connection fields.\n-\n-## 1.0.1\n-\n-### New Features\n-\n-- CanCan integration now supports a custom `Ability` class with the `ability_class:` option:\n-\n- ```ruby\n- authorize :cancan, ability_class: CustomAbility\n- ```\n-\n-## 1.0.0\n-\n-- `GraphQL::Pro` released\n+- Remove implicit ActiveSupport dependency #14\n"}]}]}]}]}]}