We've tested your project with an updated dependency and got errors while installing the dependencies.
This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.
name
version specification
new version
rails
6.0.6.1
Unfortunately, the build failed while installing dependencies. This means that while the new version is within the specified range, a version conflict between two or more packages will prohibit this version from being installed.
As this breaks fresh installs of your package, we've left this pull request open for you to investigate.
Though this method was likely never meant to take user input, it was
attempting sanitization. That sanitization could be bypassed with
carefully crafted input.
This commit makes the sanitization more robust by replacing any
occurrances of "/" or "/" with "/ " or " /". It also performs a
first pass to remove one surrounding comment to avoid compatibility
issues for users relying on the existing removal.
This also clarifies in the documentation of annotate that it should not
be provided user input.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
depfu[bot]
commented
1 year ago
We've tested your project with an updated dependency and got errors while installing the dependencies.
This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.
Unfortunately, the build failed while installing dependencies. This means that while the new version is within the specified range, a version conflict between two or more packages will prohibit this version from being installed.
As this breaks fresh installs of your package, we've left this pull request open for you to investigate.
What changed?
✳️ rails ( → 6.0.6.1) · Repo
Release Notes
6.0.6.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
Version 6.0.6.1Make sanitize_as_sql_comment more strictDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands