Skip to content

8.31.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 02 Sep 10:23
· 23 commits to main since this release
v8.31.0
a00f0b2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

@comet/admin@8.31.0

Patch Changes

  • be2d64f: Show the GraphQL error messages in the error dialog again

    createErrorDialogApolloLink only passed the message of network errors to the ErrorDialog.
    For GraphQL errors, the dialog showed "Unknown error" instead of the actual messages (e.g., the message of a BadRequestException thrown by the API).

@comet/cms-admin@8.31.0

Minor Changes

  • f3907cc: Remove the "Permissions" and "Scopes" columns from the user permissions users list

    The users list now shows the name, the email and the row actions. The permissionsCount and contentScopesCount fields of UserPermissionsUser are deprecated and now return 0. They will be removed in the next major version.

Patch Changes

  • 8b5f06f: Stop deduplicating content scopes in the user permissions API

    UserPermissionsService.getAvailableContentScopes(), getContentScopes() and getPermissionsAndContentScopes() no longer deduplicate their content scopes. Deduplication only mattered for how the scopes are displayed, so it now happens in the admin where the lists are rendered. This also removes the lodash.uniqwith dependency.

    Projects that consume UserPermissionsPublicService or the currentUser / availableContentScopes GraphQL fields directly and rely on the scopes being unique should deduplicate them on their side.

@comet/cms-api@8.31.0

Minor Changes

  • 8b5f06f: Stop deduplicating content scopes in the user permissions API

    UserPermissionsService.getAvailableContentScopes(), getContentScopes() and getPermissionsAndContentScopes() no longer deduplicate their content scopes. Deduplication only mattered for how the scopes are displayed, so it now happens in the admin where the lists are rendered. This also removes the lodash.uniqwith dependency.

    Projects that consume UserPermissionsPublicService or the currentUser / availableContentScopes GraphQL fields directly and rely on the scopes being unique should deduplicate them on their side.

  • f3907cc: Remove the "Permissions" and "Scopes" columns from the user permissions users list

    The users list now shows the name, the email and the row actions. The permissionsCount and contentScopesCount fields of UserPermissionsUser are deprecated and now return 0. They will be removed in the next major version.

Assets 2
Loading