Skip to content

Commit

Permalink
fixes in changelog (#132)
Browse files Browse the repository at this point in the history
- date of 0.1.11 was wrong
- markdown formatting instead of RST for inline monospace blocks
  • Loading branch information
Andreas committed Feb 18, 2019
1 parent 12a552c commit 8e619a8
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions CHANGES.rst
Original file line number Diff line number Diff line change
@@ -1,18 +1,18 @@
Changelog
=========

0.1.11 (2018-02-13)
0.1.11 (2019-02-13)
------------
* Make JSON logging consistent when the application is run via Gunicorn.
* Set `acceptable_destination` key in status details instead of extended headers
* Allow passing `engine_parameters` to `SQLDatabaseAPI` for those who want to customize SQLAlchemy engine parameters.
* Require recent version of `lxml` for security reasons.
* Set ``acceptable_destination`` key in status details instead of extended headers
* Allow passing ``engine_parameters`` to ``SQLDatabaseAPI`` for those who want to customize SQLAlchemy engine parameters.
* Require recent version of ``lxml`` for security reasons.
* Various test and Docker infrastructure improvements.

0.1.10 (2018-06-03)
-------------------
* Replace separate service/collection/account creation process with single `opentaxii-sync-data` CLI command.
* Persistence and Auth APIs extended with missing CRUD methods, that are used by `opentaxii-sync-data`.
* Replace separate service/collection/account creation process with single ``opentaxii-sync-data`` CLI command.
* Persistence and Auth APIs extended with missing CRUD methods, that are used by ``opentaxii-sync-data``.
* Read/modify collection level ACL added.
* DB models for default implementation of Persistence API and Auth API were changed. No automatic migration code is provided (sorry!), so upgrading might require manual DB migration.
* Drop python2.7 from testing scope.
Expand All @@ -25,7 +25,7 @@ Changelog

0.1.8 (2017-02-21)
------------------
* Ability to enable/disable "huge trees" support in XML parser. Configuration property `xml_parser_supports_huge_tree` set to `yes` or `true` will disable security restrictions and force XML parser to support very deep trees and very long text content.
* Ability to enable/disable "huge trees" support in XML parser. Configuration property ``xml_parser_supports_huge_tree`` set to ``yes`` or ``true`` will disable security restrictions and force XML parser to support very deep trees and very long text content.
* Adjust SQL Persistence API implemetation so it works smoothly with MySQL backend.
* Use Python 3.5 instead of Python 3.4 for tests.

Expand Down

0 comments on commit 8e619a8

Please sign in to comment.