### Documentation search

# Release Notes

> Release Early, Release Often

> — Eric S. Raymond, The Cathedral and the Bazaar.

## Versioning

Minor version numbers (0.0.x) are used for changes that are API compatible. You should be able to upgrade between minor point releases without any other code changes.

Medium version numbers (0.x.0) may include API changes, in line with the deprecation policy. You should read the release notes carefully before upgrading between medium point releases.

Major version numbers (x.0.0) are reserved for substantial project milestones. No major point releases are currently planned.

## Deprecation policy

REST framework releases follow a formal deprecation policy, which is in line with Django's deprecation policy.

The timeline for deprecation of a feature present in version 1.0 would work as follows:

- Version 1.1 would remain fully backwards compatible with 1.0, but would raise `PendingDeprecationWarning` warnings if you use the feature that are due to be deprecated. These warnings are silent by default, but can be explicitly enabled when you're ready to start migrating any required changes. For example if you start running your tests using `python -Wd manage.py test`, you'll be warned of any API changes you need to make.

- Version 1.2 would escalate these warnings to `DeprecationWarning`, which is loud by default.

- Version 1.3 would remove the deprecated bits of API entirely.

Note that in line with Django's policy, any parts of the framework not mentioned in the documentation should generally be considered private API, and may be subject to change.

## Upgrading

To upgrade Django REST framework to the latest version, use pip:

    pip install -U djangorestframework

You can determine your currently installed version using `pip freeze`:

    pip freeze | grep djangorestframework

## 2.3.x series

### 2.3.14

Date: 12th June 2014

- Security fix: Escape request path when it is include as part of the login and logout links in the browsable API.
- `help_text` and `verbose_name` automatically set for related fields on `ModelSerializer`.
- Fix nested serializers linked through a backward foreign key relation.
- Fix bad links for the `BrowsableAPIRenderer` with `YAMLRenderer`.
- Add `UnicodeYAMLRenderer` that extends `YAMLRenderer` with unicode.
- Fix `parse_header` argument convertion.
- Fix mediatype detection under Python 3.
- Web browseable API now offers blank option on dropdown when the field is not required.
- `APIException` representation improved for logging purposes.
- Allow source="*" within nested serializers.
- Better support for custom oauth2 provider backends.
- Fix field validation if it's optional and has no value.
- Add `SEARCH_PARAM` and `ORDERING_PARAM`.
- Fix `APIRequestFactory` to support arguments within the url string for GET.
- Allow three transport modes for access tokens when accessing a protected resource.
- Fix `QueryDict` encoding on request objects.
- Ensure throttle keys do not contain spaces, as those are invalid if using `memcached`.
- Support `blank_display_value` on `ChoiceField`.

### 2.3.13

Date: 6th March 2014

- Django 1.7 Support.
- Fix `default` argument when used with serializer relation fields.
- Display the media type of the content that is being displayed in the browsable API, rather than 'text/html'.
- Bugfix for `urlize` template failure when URL regex is matched, but value does not `urlparse`.
- Use `urandom` for token generation.
- Only use `Vary: Accept` when more than one renderer exists.

### 2.3.12

Date: 15th January 2014

- Security fix: `OrderingField` now only allows ordering on readable serializer fields, or on fields explicitly specified using `ordering_fields`. This prevents users being able to order by fields that are not visible in the API, and exploiting the ordering of sensitive data such as password hashes.
- Bugfix: `write_only = True` fields now display in the browsable API.

### 2.3.11

Date: 14th January 2014

- Added `write_only` serializer field argument.
- Added `write_only_fields` option to `ModelSerializer` classes.
- JSON renderer now deals with objects that implement a dict-like interface.
- Fix compatiblity with newer versions of `django-oauth-plus`.
- Bugfix: Refine behavior that calls model manager `all()` across nested serializer relationships, preventing erronous behavior with some non-ORM objects, and preventing unneccessary queryset re-evaluations.
- Bugfix: Allow defaults on BooleanFields to be properly honored when values are not supplied.
- Bugfix: Prevent double-escaping of non-latin1 URL query params when appending `format=json` params.

### 2.3.10

Date: 6th December 2013

- Add in choices information for ChoiceFields in response to `OPTIONS` requests.
- Added `pre_delete()` and `post_delete()` method hooks.
- Added status code category helper functions.
- Bugfix: Partial updates which erronously set a related field to `None` now correctly fail validation instead of raising an exception.
- Bugfix: Responses without any content no longer include an HTTP `'Content-Type'` header.
- Bugfix: Correctly handle validation errors in PUT-as-create case, responding with 400.

### 2.3.9

Date: 15th November 2013

- Fix Django 1.6 exception API compatibility issue caused by `ValidationError`.
- Include errors in HTML forms in browsable API.
- Added JSON renderer support for numpy scalars.
- Added `transform_<fieldname>` hooks on serializers for easily modifying field output.
- Added `get_context` hook in `BrowsableAPIRenderer`.
- Allow serializers to be passed `files` but no `data`.
- `HTMLFormRenderer` now renders serializers directly to HTML without needing to create an intermediate form object.
- Added `get_filter_backends` hook.
- Added queryset aggregates to allowed fields in `OrderingFilter`.
- Bugfix: Fix decimal suppoprt with `YAMLRenderer`.
- Bugfix: Fix submission of unicode in browsable API through raw data form.

### 2.3.8

Date: 11th September 2013

- Added `DjangoObjectPermissions`, and `DjangoObjectPermissionsFilter`.
- Support customizable exception handling, using the `EXCEPTION_HANDLER` setting.
- Support customizable view name and description functions, using the `VIEW_NAME_FUNCTION` and `VIEW_DESCRIPTION_FUNCTION` settings.
- Added `MAX_PAGINATE_BY` setting and `max_paginate_by` generic view attribute.
- Added `cache` attribute to throttles to allow overriding of default cache.
- 'Raw data' tab in browsable API now contains pre-populated data.
- 'Raw data' and 'HTML form' tab preference in browseable API now saved between page views.
- Bugfix: `required=True` argument fixed for boolean serializer fields.
- Bugfix: `client.force_authenticate(None)` should also clear session info if it exists.
- Bugfix: Client sending empty string instead of file now clears `FileField`.
- Bugfix: Empty values on ChoiceFields with `required=False` now consistently return `None`.
- Bugfix: Clients setting `page_size=0` now simply returns the default page size, instead of disabling pagination. [*]

[*] Note that the change in `page_size=0` behaviour fixes what is considered to be a bug in how clients can effect the pagination size. However if you were relying on this behavior you will need to add the following mixin to your list views in order to preserve the existing behavior.

    class DisablePaginationMixin(object):
        def get_paginate_by(self, queryset=None):
            if self.request.QUERY_PARAMS[self.paginate_by_param] == '0':
                return None
            return super(DisablePaginationMixin, self).get_paginate_by(queryset)

### 2.3.7

Date: 16th August 2013

- Added `APITestClient`, `APIRequestFactory` and `APITestCase` etc...
- Refactor `SessionAuthentication` to allow esier override for CSRF exemption.
- Remove 'Hold down "Control" message from help_text' widget messaging when not appropriate.
- Added admin configuration for auth tokens.
- Bugfix: `AnonRateThrottle` fixed to not throttle authenticated users.
- Bugfix: Don't set `X-Throttle-Wait-Seconds` when throttle does not have `wait` value.
- Bugfix: Fixed `PATCH` button title in browsable API.
- Bugfix: Fix issue with OAuth2 provider naive datetimes.

### 2.3.6

Date: 27th June 2013

- Added `trailing_slash` option to routers.
- Include support for `HttpStreamingResponse`.
- Support wider range of default serializer validation when used with custom model fields.
- UTF-8 Support for browsable API descriptions.
- OAuth2 provider uses timezone aware datetimes when supported.
- Bugfix: Return error correctly when OAuth non-existent consumer occurs.
- Bugfix: Allow `FileUploadParser` to correctly filename if provided as URL kwarg.
- Bugfix: Fix `ScopedRateThrottle`.

### 2.3.5

Date: 3rd June 2013

- Added `get_url` hook to `HyperlinkedIdentityField`.
- Serializer field `default` argument may be a callable.
- `@action` decorator now accepts a `methods` argument.
- Bugfix: `request.user` should be still be accessible in renderer context if authentication fails.
- Bugfix: The `lookup_field` option on `HyperlinkedIdentityField` should apply by default to the url field on the serializer.
- Bugfix: `HyperlinkedIdentityField` should continue to support `pk_url_kwarg`, `slug_url_kwarg`, `slug_field`, in a pending deprecation state.
- Bugfix: Ensure we always return 404 instead of 500 if a lookup field cannot be converted to the correct lookup type. (Eg non-numeric `AutoInteger` pk lookup)

### 2.3.4

Date: 24th May 2013

- Serializer fields now support `label` and `help_text`.
- Added `UnicodeJSONRenderer`.
- `OPTIONS` requests now return metadata about fields for `POST` and `PUT` requests.
- Bugfix: `charset` now properly included in `Content-Type` of responses.
- Bugfix: Blank choice now added in browsable API on nullable relationships.
- Bugfix: Many to many relationships with `through` tables are now read-only.
- Bugfix: Serializer fields now respect model field args such as `max_length`.
- Bugfix: SlugField now performs slug validation.
- Bugfix: Lazy-translatable strings now properly serialized.
- Bugfix: Browsable API now supports bootswatch styles properly.
- Bugfix: HyperlinkedIdentityField now uses `lookup_field` kwarg.

Note: Responses now correctly include an appropriate charset on the `Content-Type` header. For example: `application/json; charset=utf-8`. If you have tests that check the content type of responses, you may need to update these accordingly.

### 2.3.3

Date: 16th May 2013

- Added SearchFilter
- Added OrderingFilter
- Added GenericViewSet
- Bugfix: Multiple `@action` and `@link` methods now allowed on viewsets.
- Bugfix: Fix API Root view issue with DjangoModelPermissions

### 2.3.2

Date: 8th May 2013

- Bugfix: Fix `TIME_FORMAT`, `DATETIME_FORMAT` and `DATE_FORMAT` settings.
- Bugfix: Fix `DjangoFilterBackend` issue, failing when used on view with queryset attribute.

### 2.3.1

Date: 7th May 2013

- Bugfix: Fix breadcrumb rendering issue.

### 2.3.0

Date: 7th May 2013

- ViewSets and Routers.
- ModelSerializers support reverse relations in 'fields' option.
- HyperLinkedModelSerializers support 'id' field in 'fields' option.
- Cleaner generic views.
- Support for multiple filter classes.
- FileUploadParser support for raw file uploads.
- DecimalField support.
- Made Login template easier to restyle.
- Bugfix: Fix issue with depth>1 on ModelSerializer.

Note: See the 2.3 announcement for full details.

## 2.2.x series

### 2.2.7

Date: 17th April 2013

- Loud failure when view does not return a `Response` or `HttpResponse`.
- Bugfix: Fix for Django 1.3 compatibility.
- Bugfix: Allow overridden `get_object()` to work correctly.

### 2.2.6

Date: 4th April 2013

- OAuth2 authentication no longer requires unnecessary URL parameters in addition to the token.
- URL hyperlinking in browsable API now handles more cases correctly.
- Long HTTP headers in browsable API are broken in multiple lines when possible.
- Bugfix: Fix regression with DjangoFilterBackend not worthing correctly with single object views.
- Bugfix: OAuth should fail hard when invalid token used.
- Bugfix: Fix serializer potentially returning `None` object for models that define `__bool__` or `__len__`.

### 2.2.5

Date: 26th March 2013

- Serializer support for bulk create and bulk update operations.
- Regression fix: Date and time fields return date/time objects by default. Fixes regressions caused by 2.2.2. See #743 for more details.
- Bugfix: Fix 500 error is OAuth not attempted with OAuthAuthentication class installed.
- `Serializer.save()` now supports arbitrary keyword args which are passed through to the object `.save()` method. Mixins use `force_insert` and `force_update` where appropriate, resulting in one less database query.

### 2.2.4

Date: 13th March 2013

- OAuth 2 support.
- OAuth 1.0a support.
- Support X-HTTP-Method-Override header.
- Filtering backends are now applied to the querysets for object lookups as well as lists. (Eg you can use a filtering backend to control which objects should 404)
- Deal with error data nicely when deserializing lists of objects.
- Extra override hook to configure `DjangoModelPermissions` for unauthenticated users.
- Bugfix: Fix regression which caused extra database query on paginated list views.
- Bugfix: Fix pk relationship bug for some types of 1-to-1 relations.
- Bugfix: Workaround for Django bug causing case where `Authtoken` could be registered for cascade delete from `User` even if not installed.

### 2.2.3

Date: 7th March 2013

- Bugfix: Fix None values for for `DateField`, `DateTimeField` and `TimeField`.

### 2.2.2

Date: 6th March 2013

- Support for custom input and output formats for `DateField`, `DateTimeField` and `TimeField`.
- Cleanup: Request authentication is no longer lazily evaluated, instead authentication is always run, which results in more consistent, obvious behavior. Eg. Supplying bad auth credentials will now always return an error response, even if no permissions are set on the view.
- Bugfix for serializer data being uncacheable with pickle protocol 0.
- Bugfixes for model field validation edge-cases.
- Bugfix for authtoken migration while using a custom user model and south.

### 2.2.1

Date: 22nd Feb 2013

- Security fix: Use `defusedxml` package to address XML parsing vulnerabilities.
- Raw data tab added to browsable API. (Eg. Allow for JSON input.)
- Added TimeField.
- Serializer fields can be mapped to any method that takes no args, or only takes kwargs which have defaults.
- Unicode support for view names/descriptions in browsable API.
- Bugfix: request.DATA should return an empty `QueryDict` with no data, not `None`.
- Bugfix: Remove unneeded field validation, which caused extra queries.

Security note: Following the disclosure of security vulnerabilities in Python's XML parsing libraries, use of the `XMLParser` class now requires the `defusedxml` package to be installed.

The security vulnerabilities only affect APIs which use the `XMLParser` class, by enabling it in any views, or by having it set in the `DEFAULT_PARSER_CLASSES` setting. Note that the `XMLParser` class is not enabled by default, so this change should affect a minority of users.

### 2.2.0

Date: 13th Feb 2013

- Python 3 support.
- Added a `post_save()` hook to the generic views.
- Allow serializers to handle dicts as well as objects.
- Deprecate `ManyRelatedField()` syntax in favor of `RelatedField(many=True)`
- Deprecate `null=True` on relations in favor of `required=False`.
- Deprecate `blank=True` on CharFields, just use `required=False`.
- Deprecate optional `obj` argument in permissions checks in favor of `has_object_permission`.
- Deprecate implicit hyperlinked relations behavior.
- Bugfix: Fix broken DjangoModelPermissions.
- Bugfix: Allow serializer output to be cached.
- Bugfix: Fix styling on browsable API login.
- Bugfix: Fix issue with deserializing empty to-many relations.
- Bugfix: Ensure model field validation is still applied for ModelSerializer subclasses with an custom `.restore_object()` method.

Note: See the 2.2 announcement for full details.

## 2.1.x series

### 2.1.17

Date: 26th Jan 2013

- Support proper 401 Unauthorized responses where appropriate, instead of always using 403 Forbidden.
- Support json encoding of timedelta objects.
- `format_suffix_patterns()` now supports `include` style URL patterns.
- Bugfix: Fix issues with custom pagination serializers.
- Bugfix: Nested serializers now accept `source='*'` argument.
- Bugfix: Return proper validation errors when incorrect types supplied for relational fields.
- Bugfix: Support nullable FKs with `SlugRelatedField`.
- Bugfix: Don't call custom validation methods if the field has an error.

Note: If the primary authentication class is `TokenAuthentication` or `BasicAuthentication`, a view will now correctly return 401 responses to unauthenticated access, with an appropriate `WWW-Authenticate` header, instead of 403 responses.

### 2.1.16

Date: 14th Jan 2013

- Deprecate `django.utils.simplejson` in favor of Python 2.6's built-in json module.
- Bugfix: `auto_now`, `auto_now_add` and other `editable=False` fields now default to read-only.
- Bugfix: PK fields now only default to read-only if they are an AutoField or if `editable=False`.
- Bugfix: Validation errors instead of exceptions when serializers receive incorrect types.
- Bugfix: Validation errors instead of exceptions when related fields receive incorrect types.
- Bugfix: Handle ObjectDoesNotExist exception when serializing null reverse one-to-one

Note: Prior to 2.1.16, The Decimals would render in JSON using floating point if `simplejson` was installed, but otherwise render using string notation. Now that use of `simplejson` has been deprecated, Decimals will consistently render using string notation. See #582 for more details.

### 2.1.15

Date: 3rd Jan 2013

- Added `PATCH` support.
- Added `RetrieveUpdateAPIView`.
- Remove unused internal `save_m2m` flag on `ModelSerializer.save()`.
- Tweak behavior of hyperlinked fields with an explicit format suffix.
- Relation changes are now persisted in `.save()` instead of in `.restore_object()`.
- Bugfix: Fix issue with FileField raising exception instead of validation error when files=None.
- Bugfix: Partial updates should not set default values if field is not included.

### 2.1.14

Date: 31st Dec 2012

- Bugfix: ModelSerializers now include reverse FK fields on creation.
- Bugfix: Model fields with `blank=True` are now `required=False` by default.
- Bugfix: Nested serializers now support nullable relationships.

Note: From 2.1.14 onwards, relational fields move out of the `fields.py` module and into the new `relations.py` module, in order to separate them from regular data type fields, such as `CharField` and `IntegerField`.

This change will not affect user code, so long as it's following the recommended import style of `from rest_framework import serializers` and referring to fields using the style `serializers.PrimaryKeyRelatedField`.

### 2.1.13

Date: 28th Dec 2012

- Support configurable `STATICFILES_STORAGE` storage.
- Bugfix: Related fields now respect the required flag, and may be required=False.

### 2.1.12

Date: 21st Dec 2012

- Bugfix: Fix bug that could occur using ChoiceField.
- Bugfix: Fix exception in browsable API on DELETE.
- Bugfix: Fix issue where pk was was being set to a string if set by URL kwarg.

### 2.1.11

Date: 17th Dec 2012

- Bugfix: Fix issue with M2M fields in browsable API.

### 2.1.10

Date: 17th Dec 2012

- Bugfix: Ensure read-only fields don't have model validation applied.
- Bugfix: Fix hyperlinked fields in paginated results.

### 2.1.9

Date: 11th Dec 2012

- Bugfix: Fix broken nested serialization.
- Bugfix: Fix `Meta.fields` only working as tuple not as list.
- Bugfix: Edge case if unnecessarily specifying `required=False` on read only field.

### 2.1.8

Date: 8th Dec 2012

- Fix for creating nullable Foreign Keys with `''` as well as `None`.
- Added `null=<bool>` related field option.

### 2.1.7

Date: 7th Dec 2012

- Serializers now properly support nullable Foreign Keys.
- Serializer validation now includes model field validation, such as uniqueness constraints.
- Support 'true' and 'false' string values for BooleanField.
- Added pickle support for serialized data.
- Support `source='dotted.notation'` style for nested serializers.
- Make `Request.user` settable.
- Bugfix: Fix `RegexField` to work with `BrowsableAPIRenderer`.

### 2.1.6

Date: 23rd Nov 2012

- Bugfix: Unfix DjangoModelPermissions. (I am a doofus.)

### 2.1.5

Date: 23rd Nov 2012

- Bugfix: Fix DjangoModelPermissions.

### 2.1.4

Date: 22nd Nov 2012

- Support for partial updates with serializers.
- Added `RegexField`.
- Added `SerializerMethodField`.
- Serializer performance improvements.
- Added `obtain_token_view` to get tokens when using `TokenAuthentication`.
- Bugfix: Django 1.5 configurable user support for `TokenAuthentication`.

### 2.1.3

Date: 16th Nov 2012

- Added `FileField` and `ImageField`. For use with `MultiPartParser`.
- Added `URLField` and `SlugField`.
- Support for `read_only_fields` on `ModelSerializer` classes.
- Support for clients overriding the pagination page sizes. Use the `PAGINATE_BY_PARAM` setting or set the `paginate_by_param` attribute on a generic view.
- 201 Responses now return a 'Location' header.
- Bugfix: Serializer fields now respect `max_length`.

### 2.1.2

Date: 9th Nov 2012

- Filtering support.
- Bugfix: Support creation of objects with reverse M2M relations.

### 2.1.1

Date: 7th Nov 2012

- Support use of HTML exception templates. Eg. `403.html`
- Hyperlinked fields take optional `slug_field`, `slug_url_kwarg` and `pk_url_kwarg` arguments.
- Bugfix: Deal with optional trailing slashes properly when generating breadcrumbs.
- Bugfix: Make textareas same width as other fields in browsable API.
- Private API change: `.get_serializer` now uses same `instance` and `data` ordering as serializer initialization.

### 2.1.0

Date: 5th Nov 2012

- Serializer `instance` and `data` keyword args have their position swapped.
- `queryset` argument is now optional on writable model fields.
- Hyperlinked related fields optionally take `slug_field` and `slug_url_kwarg` arguments.
- Support Django's cache framework.
- Minor field improvements. (Don't stringify dicts, more robust many-pk fields.)
- Bugfix: Support choice field in Browsable API.
- Bugfix: Related fields with `read_only=True` do not require a `queryset` argument.

API-incompatible changes: Please read this thread regarding the `instance` and `data` keyword args before updating to 2.1.0.

## 2.0.x series

### 2.0.2

Date: 2nd Nov 2012

- Fix issues with pk related fields in the browsable API.

### 2.0.1

Date: 1st Nov 2012

- Add support for relational fields in the browsable API.
- Added SlugRelatedField and ManySlugRelatedField.
- If PUT creates an instance return '201 Created', instead of '200 OK'.

### 2.0.0

Date: 30th Oct 2012

- Fix all of the things. (Well, almost.)
- For more information please see the 2.0 announcement.

## 0.4.x series

### 0.4.0

- Supports Django 1.5.
- Fixes issues with 'HEAD' method.
- Allow views to specify template used by TemplateRenderer
- More consistent error responses
- Some serializer fixes
- Fix internet explorer ajax behavior
- Minor xml and yaml fixes
- Improve setup (e.g. use staticfiles, not the defunct ADMIN_MEDIA_PREFIX)
- Sensible absolute URL generation, not using hacky set_script_prefix

## 0.3.x series

### 0.3.3

- Added DjangoModelPermissions class to support `django.contrib.auth` style permissions.
- Use `staticfiles` for css files.
- Easier to override. Won't conflict with customized admin styles (e.g. grappelli)
- Templates are now nicely namespaced.
- Allows easier overriding.
- Drop implied 'pk' filter if last arg in urlconf is unnamed.
- Too magical. Explicit is better than implicit.
- Saner template variable auto-escaping.
- Tidier setup.py
- Updated for URLObject 2.0
- Bugfixes:
- Bug with PerUserThrottling when user contains unicode chars.

### 0.3.2

- Bugfixes:
- Fix 403 for POST and PUT from the UI with UserLoggedInAuthentication (#115)
- serialize_model method in serializer.py may cause wrong value (#73)
- Fix Error when clicking OPTIONS button (#146)
- And many other fixes
- Remove short status codes
- Zen of Python: "There should be one-- and preferably only one --obvious way to do it."
- get_name, get_description become methods on the view - makes them overridable.
- Improved model mixin API - Hooks for build_query, get_instance_data, get_model, get_queryset, get_ordering

### 0.3.1

- [not documented]

### 0.3.0

- JSONP Support
- Bugfixes, including support for latest markdown release

## 0.2.x series

### 0.2.4

- Fix broken IsAdminUser permission.
- OPTIONS support.
- XMLParser.
- Drop mentions of Blog, BitBucket.

### 0.2.3

- Fix some throttling bugs.
- `X-Throttle` header on throttling.
- Support for nesting resources on related models.

### 0.2.2

- Throttling support complete.

### 0.2.1

- Couple of simple bugfixes over 0.2.0

### 0.2.0

- Big refactoring changes since 0.1.0, ask on the discussion group if anything isn't clear. The public API has been massively cleaned up. Expect it to be fairly stable from here on in.

- `Resource` becomes decoupled into `View` and `Resource`, your views should now inherit from `View`, not `Resource`.

- The handler functions on views `.get() .put() .post()` etc, no longer have the `content` and `auth` args. Use `self.CONTENT` inside a view to access the deserialized, validated content. Use `self.user` inside a view to access the authenticated user.

- `allowed_methods` and `anon_allowed_methods` are now defunct. if a method is defined, it's available. The `permissions` attribute on a `View` is now used to provide generic permissions checking. Use permission classes such as `FullAnonAccess`, `IsAuthenticated` or `IsUserOrIsAnonReadOnly` to set the permissions.

- The `authenticators` class becomes `authentication`. Class names change to `Authentication`.

- The `emitters` class becomes `renderers`. Class names change to `Renderers`.

- `ResponseException` becomes `ErrorResponse`.

- The mixin classes have been nicely refactored, the basic mixins are now `RequestMixin`, `ResponseMixin`, `AuthMixin`, and `ResourceMixin` You can reuse these mixin classes individually without using the `View` class.

## 0.1.x series

### 0.1.1

- Final build before pulling in all the refactoring changes for 0.2, in case anyone needs to hang on to 0.1.

### 0.1.0

- Initial release.