Updates: (deps): Update drupal/graphql requirement from 4.6.0 to 4.9.0 #4073
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
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
prio: medium
status: needs review
|
@dependabot rebase |
Updates the requirements on drupal/graphql to permit the latest version. --- updated-dependencies: - dependency-name: drupal/graphql dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/composer/drupal/graphql-4.9.0
branch
from
548cb4c to
ccdc08a
Compare
denis-getopensocial
force-pushed
the
dependabot/composer/drupal/graphql-4.9.0
branch
from
1c2504e to
86022ca
Compare
The compass components are not yet importing and the output for an empty `labels` is not an array but `null`. So we change this over to be the same in all our compass files in the hope that they import.
The import of components from monorepos isn't working properly yet. The Atlassian support team suggested making them manually and then adding the generated files instead in small (~10 files) batches. This commit contains the first ten files for which components were manually created in compass.
The import of components from monorepos isn't working properly yet. The Atlassian support team suggested making them manually and then adding the generated files instead in small (~10 files) batches.
The import of components from monorepos isn't working properly yet. The Atlassian support team suggested making them manually and then adding the generated files instead in small (~10 files) batches.
The import of components from monorepos isn't working properly yet. The Atlassian support team suggested making them manually and then adding the generated files instead in small (~10 files) batches.
… the user does not start with __DELETED_USER
…that feature is active/disabled
In the database we have table "group_relationship_field_data" which is the data table for group content entities. In this table, we can see the columns type, group_type and plugin_id. The pattern for the group membership type is usually <group_type>-<plugin>. The type (column) is limited to 32 characters, and for example closed_challenge-group_membership (33 characters) is just too long. Group includes a way to generate names that fit the limits imposed by Drupal core, and it does this consistently in its own code. However, this means that where a <bundle>-<plugin> concatenation would exceed the limit, it instead converts it to 'group_content_type_' . md5($preferred_id) and truncates it. This is done in GroupRelationshipTypeStorage::getRelationshipTypeId. The problem is that our code is naively looking at the concatenation and doesn't handle the "too long" case, which is handled by the group module. To solve the problem, we replaced the type condition in the count database query withthe plugin_id condition, because we do not need the relationship type, which is unique per plugin_id and group_type. Since group_type is always the same per group entity (and we count per entity), filtering by plugin_id instead of type gives the expected result.
In the database we have table "group_relationship_field_data" which is the data table for group content entities. In this table, we can see the columns type, group_type and plugin_id. The pattern for the group membership type is usually <group_type>-<plugin>. The type (column) is limited to 32 characters, and for example closed_challenge-group_membership (33 characters) is just too long. Group includes a way to generate names that fit the limits imposed by Drupal core, and it does this consistently in its own code. However, this means that where a <bundle>-<plugin> concatenation would exceed the limit, it instead converts it to 'group_content_type_' . md5($preferred_id) and truncates it. This is done in GroupRelationshipTypeStorage::getRelationshipTypeId. The problem is that our code is naively looking at the concatenation and doesn't handle the "too long" case, which is handled by the group module. To solve the problem, we replaced the "type" condition in the database query with the "plugin_id" condition, because we do not need the relationship "type", which is unique per plugin_id and group_type. Since group_type is always the same per group entity (and we filter per entity), filtering by "plugin_id" instead of "type" gives the expected result.
Bumps [rollup](https://github.com/rollup/rollup) from 4.14.1 to 4.22.4. - [Release notes](https://github.com/rollup/rollup/releases) - [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md) - [Commits](rollup/rollup@v4.14.1...v4.22.4) --- updated-dependencies: - dependency-name: rollup dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [braces](https://github.com/micromatch/braces) from 3.0.2 to 3.0.3. - [Changelog](https://github.com/micromatch/braces/blob/master/CHANGELOG.md) - [Commits](micromatch/braces@3.0.2...3.0.3) --- updated-dependencies: - dependency-name: braces dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 5.2.8 to 5.2.14. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v5.2.14/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v5.2.14/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>
Updates the requirements on drupal/admin_toolbar to permit the latest version. --- updated-dependencies: - dependency-name: drupal/admin_toolbar dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
denis-getopensocial
force-pushed
the
dependabot/composer/drupal/graphql-4.9.0
branch
from
d0c3278 to
36ab9f1
Compare
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
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.
Updates the requirements on drupal/graphql to permit the latest version.
You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)