-
Notifications
You must be signed in to change notification settings - Fork 115
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
[noissue]: Bump django-storages[boto3] from 1.14.3 to 1.14.4 #5553
Conversation
3b87e40
to
adb0205
Compare
Pull request was closed
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. |
@dependabot rebase |
Bumps [django-storages[boto3]](https://github.com/jschneier/django-storages) from 1.14.3 to 1.14.4. - [Changelog](https://github.com/jschneier/django-storages/blob/master/CHANGELOG.rst) - [Commits](jschneier/django-storages@1.14.3...1.14.4) --- updated-dependencies: - dependency-name: django-storages[boto3] dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
adb0205
to
3f6fc26
Compare
So this updating the boto stuff, and failing the S3 test is sufficient coincidence to me indicating that something broke. Looking at the changelog, is there anything we need from this update, or can we postpone investigating this? |
I didn't see anything in the commit-msgs that was a must-have, and yeah, I am also concerned that "it breaks something". It might just be the tests that need to be fixed, but I really don't know. I'm ok with holding off until we free up some cycles to figure out what's going on. |
This is what's going on: |
Let's not pick up that version. It is obviously broken. |
Bumps django-storages[boto3] from 1.14.3 to 1.14.4.
Changelog
Sourced from django-storages[boto3]'s changelog.
Commits
b37d53e
Release version 1.14.4 (#1428)a79a304
[sftp] Cleanup duplicated properties (#1426)cd42c17
[dropbox] Remove dead prefix removal code (#1425)855e58d
[ftp] Add FTP_ALLOW_OVERWRITE setting (#1424)fe759bf
[ftp] Conform to BaseStorage interface (#1423)a531947
[general] Write overwriting files in terms of .exists() (#1422)0041eb2
[dropbox] Add support for Python3.12 (#1421)4cd12e0
[sftp] Format times to UTC (#1420)ea25226
[sftp] Add implementations of get_(modified|accessed)_time (#1347)6c494a0
[docs/scaleway] Create Scaleway docs (#1419)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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)