Skip to content

Commit

Permalink
Update CHANGELOG
Browse files Browse the repository at this point in the history
  • Loading branch information
lafrech committed Nov 9, 2018
1 parent c7f8f24 commit 3652561
Showing 1 changed file with 18 additions and 5 deletions.
23 changes: 18 additions & 5 deletions CHANGELOG.rst
Original file line number Diff line number Diff line change
@@ -1,17 +1,30 @@
Changelog
---------

0.11.0 (2018-11-09)
+++++++++++++++++++

Features:

- *Backwards-incompatible*: Rework of the ETag feature. It is now accesible
using dedicated ``Blueprint.etag`` decorator. ``check_etag`` and ``set_etag``
are methods of ``Blueprint`` and ``etag.INCLUDE_HEADERS`` is replaced with
``Blueprint.ETAG_INCLUDE_HEADERS``. It is enabled by default (only on views
decorated with ``Blueprint.etag``) and disabled with ``ETAG_DISABLED``
application configuration parameter. ``is_etag_enabled`` is now private.

0.10.0 (2018-10-24)
+++++++++++++++++++

Features:

- *Backwards-incompatible*: Don't prefix all routes in the spec with
`APPLICATION_ROOT`. If using OpenAPI v2, set `APPLICATION_ROOT` as
`basePath`. If using OpenAPI v3, the user should specify `servers` manually.
- *Backwards-incompatible*: In testing and debug modes, `verify_check_etag` not
only logs a warning but also raises `CheckEtagNotCalledError` if `check_etag`
is not called in a resource that needs it.
``APPLICATION_ROOT``. If using OpenAPI v2, set ``APPLICATION_ROOT`` as
``basePath``. If using OpenAPI v3, the user should specify ``servers``
manually.
- *Backwards-incompatible*: In testing and debug modes, ``verify_check_etag``
not only logs a warning but also raises ``CheckEtagNotCalledError`` if
``check_etag`` is not called in a resource that needs it.

0.9.2 (2018-10-16)
++++++++++++++++++
Expand Down

0 comments on commit 3652561

Please sign in to comment.