Skip to content

Bump puma from 6.3.1 to 6.4.2 (#1487) #3573

Bump puma from 6.3.1 to 6.4.2 (#1487)

Bump puma from 6.3.1 to 6.4.2 (#1487) #3573

GitHub Actions / GraphQL Inspector succeeded Apr 19, 2024 in 3s

Everything looks good

Found 10 changes

Breaking: 0
Dangerous: 2
Safe: 8

Dangerous changes

  • Argument number: [Int!] added to field Anime.episodes
  • Argument number: [Int!] added to field Episodic.episodes

Safe changes

  • Description The mutation requires an authenticated logged-in user session, and none was provided or the session has expired. The recommended action varies depending on your application and whether you provided the bearer token in the Authorization header or not. If you did, you should probably attempt to refresh the token, and if that fails, prompt the user to log in again. If you did not provide a bearer token, you should just prompt the user to log in. on type NotAuthenticatedError has changed to The mutation requires an authenticated logged-in user session, and none was
    provided or the session has expired. The recommended action varies depending on
    your application and whether you provided the bearer token in the
    Authorization header or not. If you did, you should probably attempt to
    refresh the token, and if that fails, prompt the user to log in again. If you
    did not provide a bearer token, you should just prompt the user to log in.
  • Description The mutation requires higher permissions than the current user or token has. This is a bit vague, but it generally means youre attempting to modify an object you dont own, or perform an administrator action without being an administrator. It could also mean your token does not have the required scopes to perform the action. The recommended action is to display a message to the user informing them that their action failed and that retrying will generally not help. on type NotAuthorizedError has changed to The mutation requires higher permissions than the current user or token has.
    This is a bit vague, but it generally means you
    re attempting to modify an
    object you dont own, or perform an administrator action without being an
    administrator. It could also mean your token does not have the required scopes
    to perform the action. The recommended action is to display a message to the
    user informing them that their action failed and that retrying will generally not help.
  • Description An object required for your mutation was unable to be located. Usually this means the object youre attempting to modify or delete does not exist. The recommended action is to display a message to the user informing them that their action failed and that retrying will generally not help.** on type NotFoundError has changed to An object required for your mutation was unable to be located. Usually this
    means the object you
    re attempting to modify or delete does not exist. The
    recommended action is to display a message to the user informing them that their
    action failed and that retrying will generally not help.**
  • Field Profile.waifuOrHusbando description changed from The properly-gendered term for the users waifu. This should normally only be Waifu or Husbando but some people are jerks, including the person who wrote this...** to The properly-gendered term for the users waifu. This should normally only be
    Waifu or Husbando but some people are jerks, including the person who wrote this...**
  • Field Query.searchMediaByTitle description changed from Search for any media (Anime, Manga) by title using Algolia. If no media_type is supplied, it will search for both. The most relevant results will be at the top. to Search for any media (Anime, Manga) by title using Algolia. If no media_type
    is supplied, it will search for both. The most relevant results will be at the top.
  • Description The mutation failed validation. This is usually because the input provided was invalid in some way, such as a missing required field or an invalid value for a field. There may be multiple of this error, one for each failed validation, and the path will generally refer to a location in the input parameters, that you can map back to the input fields in your form. The recommended action is to display validation errors to the user, and allow them to correct the input and resubmit. on type ValidationError has changed to The mutation failed validation. This is usually because the input provided was
    invalid in some way, such as a missing required field or an invalid value for a
    field. There may be multiple of this error, one for each failed validation, and
    the path will generally refer to a location in the input parameters, that you
    can map back to the input fields in your form. The recommended action is to
    display validation errors to the user, and allow them to correct the input and resubmit.
  • Field WikiSubmission.data description changed from The full object that holds all the details for any modifications/additions/deletions made to the entity you are editing. This will be validated using JSON Schema. to The full object that holds all the details for any
    modifications/additions/deletions made to the entity you are editing. This
    will be validated using JSON Schema.
  • Description A Wiki Submission is used to either create or edit existing data in our database. This will allow a simple and convient way for users to submit issues/corrections without all the work being left to the mods. on type WikiSubmission has changed to A Wiki Submission is used to either create or edit existing data in our
    database. This will allow a simple and convient way for users to submit
    issues/corrections without all the work being left to the mods.

Looking for more advanced tool? Try GraphQL Hive!

Annotations

Check warning on line 389 in schema.graphql

See this annotation in the file changed.

@github-actions github-actions / GraphQL Inspector

Argument 'number: [Int!]' added to field 'Anime.episodes'

Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.

Check warning on line 1755 in schema.graphql

See this annotation in the file changed.

@github-actions github-actions / GraphQL Inspector

Argument 'number: [Int!]' added to field 'Episodic.episodes'

Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.

Check notice on line 4509 in schema.graphql

See this annotation in the file changed.

@github-actions github-actions / GraphQL Inspector

Description 'The mutation requires an authenticated logged-in user session, and none was provided or the session has expired. The recommended action varies depending on your application and whether you provided the bearer token in the `Authorization` header or not. If you did, you should probably attempt to refresh the token, and if that fails, prompt the user to log in again. If you did not provide a bearer token, you should just prompt the user to log in.' on type 'NotAuthenticatedError' has changed to 'The mutation requires an authenticated logged-in user session, and none was provided or the session has expired. The recommended action varies depending on your application and whether you provided the bearer token in the `Authorization` header or not. If you did, you should probably attempt to refresh the token, and if that fails, prompt the user to log in again. If you did not provide a bearer token, you should just prompt the user to log in.'

Description 'The mutation requires an authenticated logged-in user session, and none was provided or the session has expired. The recommended action varies depending on your application and whether you provided the bearer token in the `Authorization` header or not. If you did, you should probably attempt to refresh the token, and if that fails, prompt the user to log in again. If you did not provide a bearer token, you should just prompt the user to log in.' on type 'NotAuthenticatedError' has changed to 'The mutation requires an authenticated logged-in user session, and none was
provided or the session has expired. The recommended action varies depending on
your application and whether you provided the bearer token in the
`Authorization` header or not. If you did, you should probably attempt to
refresh the token, and if that fails, prompt the user to log in again. If you
did not provide a bearer token, you should just prompt the user to log in.'

Check notice on line 4534 in schema.graphql

See this annotation in the file changed.

@github-actions github-actions / GraphQL Inspector

Description 'The mutation requires higher permissions than the current user or token has. This is a bit vague, but it generally means you're attempting to modify an object you don't own, or perform an administrator action without being an administrator. It could also mean your token does not have the required scopes to perform the action. The recommended action is to display a message to the user informing them that their action failed and that retrying will generally *not* help.' on type 'NotAuthorizedError' has changed to 'The mutation requires higher permissions than the current user or token has. This is a bit vague, but it generally means you're attempting to modify an object you don't own, or perform an administrator action without being an administrator. It could also mean your token does not have the required scopes to perform the action. The recommended action is to display a message to the user informing them that their action failed and that retrying will generally *not* help.'

Description 'The mutation requires higher permissions than the current user or token has. This is a bit vague, but it generally means you're attempting to modify an object you don't own, or perform an administrator action without being an administrator. It could also mean your token does not have the required scopes to perform the action. The recommended action is to display a message to the user informing them that their action failed and that retrying will generally *not* help.' on type 'NotAuthorizedError' has changed to 'The mutation requires higher permissions than the current user or token has.
This is a bit vague, but it generally means you're attempting to modify an
object you don't own, or perform an administrator action without being an
administrator. It could also mean your token does not have the required scopes
to perform the action. The recommended action is to display a message to the
user informing them that their action failed and that retrying will generally *not* help.'

Check notice on line 4559 in schema.graphql

See this annotation in the file changed.

@github-actions github-actions / GraphQL Inspector

Description 'An object required for your mutation was unable to be located. Usually this means the object you're attempting to modify or delete does not exist. The recommended action is to display a message to the user informing them that their action failed and that retrying will generally *not* help.' on type 'NotFoundError' has changed to 'An object required for your mutation was unable to be located. Usually this means the object you're attempting to modify or delete does not exist. The recommended action is to display a message to the user informing them that their action failed and that retrying will generally *not* help.'

Description 'An object required for your mutation was unable to be located. Usually this means the object you're attempting to modify or delete does not exist. The recommended action is to display a message to the user informing them that their action failed and that retrying will generally *not* help.' on type 'NotFoundError' has changed to 'An object required for your mutation was unable to be located. Usually this
means the object you're attempting to modify or delete does not exist. The
recommended action is to display a message to the user informing them that their
action failed and that retrying will generally *not* help.'

Check notice on line 5387 in schema.graphql

See this annotation in the file changed.

@github-actions github-actions / GraphQL Inspector

Field 'Profile.waifuOrHusbando' description changed from 'The properly-gendered term for the user's waifu. This should normally only be 'Waifu' or 'Husbando' but some people are jerks, including the person who wrote this...' to 'The properly-gendered term for the user's waifu. This should normally only be 'Waifu' or 'Husbando' but some people are jerks, including the person who wrote this...'

Field 'Profile.waifuOrHusbando' description changed from 'The properly-gendered term for the user's waifu. This should normally only be 'Waifu' or 'Husbando' but some people are jerks, including the person who wrote this...' to 'The properly-gendered term for the user's waifu. This should normally only be
'Waifu' or 'Husbando' but some people are jerks, including the person who wrote this...'

Check notice on line 6213 in schema.graphql

See this annotation in the file changed.

@github-actions github-actions / GraphQL Inspector

Field 'Query.searchMediaByTitle' description changed from 'Search for any media (Anime, Manga) by title using Algolia. If no media_type is supplied, it will search for both. The most relevant results will be at the top.' to 'Search for any media (Anime, Manga) by title using Algolia. If no media_type is supplied, it will search for both. The most relevant results will be at the top.'

Field 'Query.searchMediaByTitle' description changed from 'Search for any media (Anime, Manga) by title using Algolia. If no media_type is supplied, it will search for both. The most relevant results will be at the top.' to 'Search for any media (Anime, Manga) by title using Algolia. If no media_type
is supplied, it will search for both. The most relevant results will be at the top.'

Check notice on line 7197 in schema.graphql

See this annotation in the file changed.

@github-actions github-actions / GraphQL Inspector

Description 'The mutation failed validation. This is usually because the input provided was invalid in some way, such as a missing required field or an invalid value for a field. There may be multiple of this error, one for each failed validation, and the `path` will generally refer to a location in the input parameters, that you can map back to the input fields in your form. The recommended action is to display validation errors to the user, and allow them to correct the input and resubmit.' on type 'ValidationError' has changed to 'The mutation failed validation. This is usually because the input provided was invalid in some way, such as a missing required field or an invalid value for a field. There may be multiple of this error, one for each failed validation, and the `path` will generally refer to a location in the input parameters, that you can map back to the input fields in your form. The recommended action is to display validation errors to the user, and allow them to correct the input and resubmit.'

Description 'The mutation failed validation. This is usually because the input provided was invalid in some way, such as a missing required field or an invalid value for a field. There may be multiple of this error, one for each failed validation, and the `path` will generally refer to a location in the input parameters, that you can map back to the input fields in your form. The recommended action is to display validation errors to the user, and allow them to correct the input and resubmit.' on type 'ValidationError' has changed to 'The mutation failed validation. This is usually because the input provided was
invalid in some way, such as a missing required field or an invalid value for a
field. There may be multiple of this error, one for each failed validation, and
the `path` will generally refer to a location in the input parameters, that you
can map back to the input fields in your form. The recommended action is to
display validation errors to the user, and allow them to correct the input and resubmit.'

Check notice on line 7439 in schema.graphql

See this annotation in the file changed.

@github-actions github-actions / GraphQL Inspector

Field 'WikiSubmission.data' description changed from 'The full object that holds all the details for any modifications/additions/deletions made to the entity you are editing. This will be validated using JSON Schema.' to 'The full object that holds all the details for any modifications/additions/deletions made to the entity you are editing. This will be validated using JSON Schema.'

Field 'WikiSubmission.data' description changed from 'The full object that holds all the details for any modifications/additions/deletions made to the entity you are editing. This will be validated using JSON Schema.' to 'The full object that holds all the details for any
modifications/additions/deletions made to the entity you are editing. This
will be validated using JSON Schema.'

Check notice on line 7427 in schema.graphql

See this annotation in the file changed.

@github-actions github-actions / GraphQL Inspector

Description 'A Wiki Submission is used to either create or edit existing data in our database. This will allow a simple and convient way for users to submit issues/corrections without all the work being left to the mods.' on type 'WikiSubmission' has changed to 'A Wiki Submission is used to either create or edit existing data in our database. This will allow a simple and convient way for users to submit issues/corrections without all the work being left to the mods.'

Description 'A Wiki Submission is used to either create or edit existing data in our database. This will allow a simple and convient way for users to submit issues/corrections without all the work being left to the mods.' on type 'WikiSubmission' has changed to 'A Wiki Submission is used to either create or edit existing data in our
database. This will allow a simple and convient way for users to submit
issues/corrections without all the work being left to the mods.'