-
Notifications
You must be signed in to change notification settings - Fork 10
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
chore(deps): update dependency graphql to v1.13.23 #211
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/graphql-1.x-lockfile
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
💻 Website PreviewThe latest changes are available as preview in: https://e727fda3.schema-stitching.pages.dev |
renovate
bot
force-pushed
the
renovate/graphql-1.x-lockfile
branch
from
October 20, 2023 17:01
07d6bc0
to
fc2e245
Compare
renovate
bot
changed the title
chore(deps): update dependency graphql to v1.13.19
chore(deps): update dependency graphql to v1.13.20
Oct 20, 2023
renovate
bot
force-pushed
the
renovate/graphql-1.x-lockfile
branch
from
January 25, 2024 20:57
fc2e245
to
b80709f
Compare
renovate
bot
changed the title
chore(deps): update dependency graphql to v1.13.20
chore(deps): update dependency graphql to v1.13.21
Jan 25, 2024
renovate
bot
changed the title
chore(deps): update dependency graphql to v1.13.21
chore(deps): update dependency graphql to v1.13.22
Feb 28, 2024
renovate
bot
force-pushed
the
renovate/graphql-1.x-lockfile
branch
from
February 28, 2024 20:00
b80709f
to
8967829
Compare
renovate
bot
force-pushed
the
renovate/graphql-1.x-lockfile
branch
2 times, most recently
from
March 26, 2024 22:33
78a2b5f
to
7fbcf88
Compare
renovate
bot
force-pushed
the
renovate/graphql-1.x-lockfile
branch
from
April 7, 2024 02:49
7fbcf88
to
3aff2b3
Compare
renovate
bot
changed the title
chore(deps): update dependency graphql to v1.13.22
chore(deps): update dependency graphql to v1.13.23
Apr 7, 2024
renovate
bot
changed the title
chore(deps): update dependency graphql to v1.13.23
chore(deps): update dependency graphql to v1.13.23 - autoclosed
Jul 14, 2024
renovate
bot
changed the title
chore(deps): update dependency graphql to v1.13.23 - autoclosed
chore(deps): update dependency graphql to v1.13.23
Jul 14, 2024
renovate
bot
force-pushed
the
renovate/graphql-1.x-lockfile
branch
from
July 14, 2024 04:53
3aff2b3
to
58c80b4
Compare
renovate
bot
changed the title
chore(deps): update dependency graphql to v1.13.23
chore(deps): update dependency graphql to v1.13.23 - autoclosed
Aug 6, 2024
renovate
bot
changed the title
chore(deps): update dependency graphql to v1.13.23 - autoclosed
chore(deps): update dependency graphql to v1.13.23
Aug 6, 2024
renovate
bot
force-pushed
the
renovate/graphql-1.x-lockfile
branch
from
August 6, 2024 08:43
58c80b4
to
4259470
Compare
renovate
bot
changed the title
chore(deps): update dependency graphql to v1.13.23
chore(deps): update dependency graphql to v1.13.23 - autoclosed
Sep 2, 2024
renovate
bot
changed the title
chore(deps): update dependency graphql to v1.13.23 - autoclosed
chore(deps): update dependency graphql to v1.13.23
Sep 3, 2024
renovate
bot
force-pushed
the
renovate/graphql-1.x-lockfile
branch
from
September 3, 2024 10:34
4259470
to
3bd4829
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.11.6
->1.13.23
Release Notes
rmosolgo/graphql-ruby (graphql)
v1.13.23
Compare Source
v1.13.22
Compare Source
v1.13.21
Compare Source
v1.13.20
Compare Source
v1.13.19
Compare Source
Bug fixes
scope: false
for introspection types #4315v1.13.18
Compare Source
New Features
hash_key:
: perform[...]
lookups even when the underlying object isn't a Hash #4286v1.13.17
Compare Source
Bug fixes
v1.13.16
Compare Source
New Features
validate_max_errors
#4178v1.13.15
Compare Source
Bug fixes
Query#validate
to skip static validation #3881v1.13.14
Compare Source
New Features
Field#relay_nodes_field
reader #4103v1.13.13
Compare Source
New features
#prepare_span
hook for custom tags #4067OpenTelementry
tracing #4077v1.13.12
Compare Source
context[:dataloader]
to multiplex context #4026.accepts_definitions
#4002v1.13.11
Compare Source
Deprecations
RangeAdd
warns whencontext:
isn't provided (it's required in GraphQL-Ruby 2.0) #3996v1.13.10
Compare Source
Breaking changes
id
fields: #3914 Previously, when a field was created withglobal_id_field
, it would pass a legacy-style type definition (an instance ofGraphQL::ObjectType
) toSchema.id_from_object(...)
. Now, it passes a class-based definition instead. If yourid_from_object(...)
method was using any methods from those legacy definitions, they should be migrated. (Most notably, uses oftype.name
should be migrated totype.graphql_name
.)Deprecations
.bidirectional_pagination = ...
and.default_nodes_field = ...
. These two configurations don't apply to the new pagination implementation, so they can be removed. #3918v1.13.9
Compare Source
Breaking changes
Authorization: #3903 In graphql-ruby v1.12.17-1.13.8, when input objects used
prepare: -> { ... }
, the returned values were not authorized at all. However, this release goes back to the behavior from 1.12.16 and before, where a returnedHash
is validated just like an input object that didn't have aprepare:
hook. To get the previous behavior, you can implementdef self.authorized?
in the input object you want to skip authorization in:Bug fixes
query.validate = ...
after a query is initialized #3881prepare:
returns a Hash (this was default < v1.12.16) #3903v1.13.8
Compare Source
Bug fixes
v1.13.7
Compare Source
New Features
replace_null_with_default: true
replaces incomingnull
s with the configureddefault_value:
#3871dig: [key1, key2, ...]
for nested hash key access #3856Bug Fixes
owner
#3870required: true
onf.argument
calls (with explicit receiver) #3858nil
invisitor.field_definition
#3857v1.13.6
Compare Source
New features
__Schema.description
,__Directive.isRepeatable
,__Type.specifiedByUrl
, and__DirectiveLocation.VARIABLE_DEFINITION
#3854Directive.resolve_each
for list items #3853Bug fixes
OFFSET
when it's already set on the relation #3846Types::ISO8601Date
: Accept default values as Ruby date objects #3563v1.13.5
Compare Source
New features
repeatable
directives #3837context[:fallback_transaction_name]
when operations aren't named #3778Bug fixes
NodeField
#3832ActiveSupport
#3829v1.13.4
Compare Source
Bug fixes
v1.13.3
Compare Source
Deprecations
GraphQL::Relay::NodeField
andGraphQL::Relay::NodesField
are deprecated; useGraphQL::Types::Relay::HasNodesField
orGraphQL::Types::Relay::HasNodeField
instead. (The underlying field instances require a reference to their owner type, butNodeField
andNodesField
can't do that, since they're shared instances) #3791New features
required: :nullable
to make an argument required to be present, even if it'snull
#3784.authorized?
on them at runtime #3786extras(...)
for extension-related extras with automatic cleanup #3787Bug fixes
query { ... }
but has no query root #3815Schema.get_field
can't make sense of the arguments #3815prepare:
hooks #3794v1.13.2
Compare Source
Bug fixes
loads:
#3782Interpreter::Arguments
instance ascontext[:current_arguments]
#3783v1.13.1
Compare Source
Bug fixes
scope: false
for introspection types #4315v1.13.0
Compare Source
Since this version, GraphQL-Ruby is tested on Ruby 2.4+ and Rails 4+ only.
Breaking changes
NO_UPDATE
#3713scope ...
configuration, then ascope:
option is required in.trigger(...)
. Usescope ..., optional: true
to get the old behavior. #3692first
/last
/max_page_size
#3609false
for.visible?(context)
, their default values won't be appliedNew features
.visible?(context)
for each query (and raise an error if multiple objects with the same name are visible). #3651 #3716 #3725nonblocking: true
will make GraphQL::Dataloader useFiber.scheduler
to run fields and load data with sources, supporting non-blocking IO. #3482null: true
andrequired: true
are now default. GraphQL-Ruby includes some RuboCop cops,GraphQL/DefaultNullTrue
andGraphQL/DefaultRequiredTrue
, which identify and remove those needless configurations. #3612implement ...
other interfaces #3613Bug fixes
value(...)
and Input Objectargument(...)
methods return the defined object #3727nil
where there were errors in the list #3656v1.12.24
Compare Source
Bug fixes
v1.12.23
Compare Source
Bug fixes
prepare:
#3795v1.12.22
Compare Source
Bug fixes
v1.12.21
Compare Source
Bug fixes
format:
/allow_blank: true
to correctly accept a blank string #3726Schema.type_error
hook #3722v1.12.20
Compare Source
New Features
Bug fixes
yield
didn't satisfy their pending requests #3707v1.12.19
Compare Source
New Features
allow_null
andallow_blank
work standalone #3671Resolver#unauthorized_object
for handling loaded but unauthorized objects #3689Bug fixes
Schema.validate_max_errors
at runtime #3691v1.12.18
Compare Source
New features
NO_UPDATE
constant for skipping subscription updates #3664Schema.validate_max_errors(integer)
for halting validation when it reaches a certain number #3683self.load_...
methods on Input objects for loading arguments #3682import_methods
in Refinements when available #3674AppsignalTracing
: Addset_action_name
#3659Bug fixes
def load_...
methods #3682context[:current_field]
when argumentprepare:
hooks raise an error #3666type(...)
#3679schema.unauthorized_field
for unauthorized resolversnull
is used as a value for a list argument #3660v1.12.17
Compare Source
New features
extras: [:parent]
#3645NumericalityValidator
#3635Bug fixes
context
#3654v1.12.16
Compare Source
New features
def self.topic_for
in Subscription classes for server-filtered streams #3597Bug fixes
v1.12.15
Compare Source
New Features
v1.12.14
Compare Source
Bug fixes
"_"
as the name forfield :_, ...
fields #3560sanitized_printer(...)
in the schema definition forQuery#sanitized_query_string
GraphQL::Backtrace
: fix multiplex supportv1.12.13
Compare Source
Breaking changes
Schema.to_definition
output string #3541Bug fixes
Hash
es andArray
s from queries instead of customized subclasses #3533owner
fornode
andnodes
fields #3509context.skip
s #3514to_h
methods on InputObject classes #3539GraphQL::ExecutionError
#3542v1.12.12
Compare Source
Bug fixes
.resolve(...)
calls #3499v1.12.11
Compare Source
Bug fixes
v1.12.10
Compare Source
New features
GlobalID::Locator.locate_many
for arrays of global Ids #3481.resolve
) onQUERY
#3474Bug fixes
#load_*
methods when they're inherited #3486rescue_from
on loading arguments #3471v1.12.9
Compare Source
New features
.authorized_new(...)
to call.new(...)
effectively skips object authorization #3446Thread.current[...]
when initializing new Fibers #3461Bug fixes
StandardError => ...
condition to the generated GraphqlController #3460Dataloader::Source
on Ruby 3 with keyword argumentsgraphiql-rails
whengenerate graphql:install
is run twice #3441max_page_size: nil
override in fields #3438v1.12.8
Compare Source
Bug fixes
rescue_from
handlers inherited from parent schema classes #3431v1.12.7
Compare Source
Breaking changes
Execution::Errors
(which implementsrescue_from
) was refactored so that, when an error matches more than one registered handler, it picks the most specific handler instead of the first match in the underlying Hash. This might "break" your code if your application registered a handler for a parent class and a child class, but expects instances of the child class to be handled by the handler for the parent class. (This seems very unlikely -- I consider the change to be a "breaking fix.") #3404New features
node_nullable(...)
connection configuration options #3389has_nodes_field(true|false)
connection configuration option #3388Bug fixes
false
#3386RawValue
s as part of a list #3403has_next_page
for ActiveRecord::Relation connections #3414Query#result
#3408v1.12.6
Compare Source
Breaking changes
New features
edges_nullable(false)
andedge_nullable(false)
for non-null fields #3376.arguments
reader to newPagination::Connection
classes #3360Bug fixes
COUNT
query from some scenarios #3373v1.12.5
Compare Source
New features
max_page_size
config #3338range_add_edge
(if supported) to improve stable connection support #3341Bug fixes
throw
s #3333v1.12.4
Compare Source
Bug fixes
resolve
#3326Execution::Lazy
s #3320handle_error
handlers #3319v1.12.3
Compare Source
Bug fixes
v1.12.2
Compare Source
Bug fixes
v1.12.1
Compare Source
New Features
allow_null
andallow_blank
work standalone #3671Resolver#unauthorized_object
for handling loaded but unauthorized objects #3689Bug fixes
Schema.validate_max_errors
at runtime #3691v1.12.0
Compare Source
Breaking changes
GraphQL::Schema
defaults toGraphQL::Execution::Interpreter
,GraphQL::Analysis::AST
,GraphQL::Pagination::Connections
, andGraphQL::Execution::Errors
. (#3145) To get the previous (deprecated) behaviors:v1.11.10
Compare Source
Bug fixes
Schema.max_validation_errors
at query runtime #3690v1.11.9
Compare Source
New Features
Schema.max_validation_errors(val)
limits the number of errors that can be added during static validation #3675v1.11.8
Compare Source
Bug fixes
Schema.possible_types(t)
for object types #3172v1.11.7
Compare Source
Breaking changes
Incoming integer values are properly bound (as per the spec) #3206 To continue receiving out-of-bound integer values, add this to your schema's
def self.type_error(err, ctx)
hook:...
end
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.