Skip to content
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

Bump djangorestframework from 3.7.4 to 3.9.2 #1694

Closed

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps djangorestframework from 3.7.4 to 3.9.2.

Release notes

Sourced from djangorestframework's releases.

Version 3.9.2

See Release Notes for details.

Version 3.9.1

Change Notes:
https://www.django-rest-framework.org/community/release-notes/#39x-series

Verision 3.9.0

Release announcement:
https://www.django-rest-framework.org/community/3.9-announcement/

Change Notes:
https://www.django-rest-framework.org/community/release-notes/#39x-series

Version 3.8.2

Point release for 3.8.x series

  • Fix read_only + default unique_together validation. #5922
  • authtoken.views import coreapi from rest_framework.compat, not directly. #5921
  • Docs: Add missing argument 'detail' to Route #5920

Version 3.8.1

  • Use old url_name behavior in route decorators #5915

    For list_route and detail_route maintain the old behavior of url_name,
    basing it on the url_path instead of the function name.

Version 3.8

  • Release Announcement

  • 3.8.0 Milestone

  • Breaking Change: Alter read_only plus default behaviour. #5886

    read_only fields will now always be excluded from writable fields.

    Previously read_only fields with a default value would use the default for create and update operations.

    In order to maintain the old behaviour you may need to pass the value of read_only fields when calling save() in
    the view:

      def perform_create(self, serializer):
          serializer.save(owner=self.request.user)
    

    Alternatively you may override save() or create() or update() on the serialiser as appropriate.

  • Correct allow_null behaviour when required=False #5888

    Without an explicit default, allow_null implies a default of null for outgoing serialisation. Previously such
    fields were being skipped when read-only or otherwise not required.

... (truncated)
Commits
  • 0ab527a Updated release notes for v3.9.2
  • ac4c789 Update version for v3.9.2 release.
  • 7eac866 Remove executable bit from static assets (#6484)
  • 94593b3 Introduce RemovedInDRF…Warning classes to simplify deprecations. (#6480)
  • a216d02 Merge multiple isinstance() calls to one (#6481)
  • 31bf597 Updated note on BooleanField required kwarg generation.
  • 1dc81ac Fixed a typo in pagination docs. (#6475)
  • 317174b Avoided calling distinct on annotated fields in SearchFilter. (#6240)
  • 2daf6f1 Add negation ~ operator to permissions composition (#6361)
  • 739b0a2 Fix DeprecationWarning in tests when accessing collections.abc classes via co...
  • Additional commits viewable in compare view

Dependabot compatibility score

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 ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

Bumps [djangorestframework](https://github.com/encode/django-rest-framework) from 3.7.4 to 3.9.2.
- [Release notes](https://github.com/encode/django-rest-framework/releases)
- [Commits](encode/django-rest-framework@3.7.4...3.9.2)

Signed-off-by: dependabot[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Mar 4, 2019
@dependabot-preview dependabot-preview bot changed the base branch from v0.14.0 to v0.15.0 April 19, 2019 05:12
@dependabot-preview
Copy link
Contributor Author

Superseded by #1714.

@dependabot-preview dependabot-preview bot deleted the dependabot/pip/djangorestframework-3.9.2 branch April 30, 2019 05:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant