-
Notifications
You must be signed in to change notification settings - Fork 21
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
Update drupal/workbench_access requirement from 2.0.1 to 2.0.3 #3406
Update drupal/workbench_access requirement from 2.0.1 to 2.0.3 #3406
Conversation
Updates the requirements on drupal/workbench_access to permit the latest version. --- updated-dependencies: - dependency-name: drupal/workbench_access dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
See release notes https://www.drupal.org/project/workbench_access/releases/2.0.2 I've rerolled the patch for version 2.0.2 https://www.drupal.org/project/workbench_access/issues/2982550#comment-15585819 |
Needs testing on Probo and multidevs
|
Tested in Probo and with this multidev of a departmental site: I didn't notice any issues. However, I wasn't sure of how to test for this new Workbench Access issue: WBA per user cache context is too broad - applies to many all operations. Would this be a blocker? |
Additional test: ensure that pages that workbench access is restricting editor access for are still cacheable. This will probably require inspecting response headers for those pages to ensure cache-ability is not restricted. |
Next steps: determine whether to include this in a 2.11.x patch release, wait for another module release, or wait until 2.12. |
A newer version of drupal/workbench_access exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
I don't think this issue https://www.drupal.org/project/workbench_access/issues/3447476 should stop us from merging. |
Updates the requirements on drupal/workbench_access 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 rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will 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 version
will 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 dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)