Releases: Kinto/kinto
Releases · Kinto/kinto
4.3.3
4.3.2
4.3.1
Bug fixes
4.3.0
Protocol
- Fix error response consistency with safe creations if the
create
permission
is granted (fixes #792). The server now returns a412
instead of a403
if
theIf-None-Match: *
header is provided and thecreate
permission is granted. - The
permissions
attribute is now empty in the response if the user has not the permission
to write on the object (fixes #123) - Filtering records now works the same on the memory and postgresql backends:
if we're comparing to a number, the filter will now filter out records that
don't have this field. If we're comparing to anything else, the record
without such a field is treated as if it had '' as the value for this field.
(fixes #815) - Parent attributes are now readable if children creation is allowed. That means for example
that collection attributes are now readable to users withrecord:create
permission.
Same applies to bucket attributes andcollection:create
andgroup:create
(fixes #803) - Return an empty list on the plural endpoint instead of
403
if thecreate
permission is allowed
Protocol is now at version 1.11. See API changelog
Bug fixes
New features
- The storage backend now allows
parent_id
pattern matching inkinto.core.storage.get_all
. (#821) - The history and quotas plugins execution time is now monitored on StatsD (
kinto.plugins.quotas
andkinto.plugins.history
) (#832) - Add new
kinto.version_json_path
setting (fixes #830)
Internal changes
- Fixed a failing pypy test by changing the way it was mocking
transaction.manager.commit
(fixes #755) - Moved storage/cache/permissions base tests to
kinto.core.*.testing
(fixes #801) - Now fails with an explicit error when StatsD is configured but not installed.
- Remove redundant fields from data column in PostgreSQL records table (fixes #762)
4.2.0
Protocol
- Support for filtering records based on a text search (#791)
Protocol is now at version 1.10. See API changelog.
Bug fixes
3.3.3
4.1.1
4.1.0
New features
- Show warning when
http_scheme
is not set tohttps
(#706, thanks @Prashant-Surya)
Bug fixes
- Fix sorting/filtering history entries by
date
field - On subobject filtering, return a 400 error response only if first level field
is unknown (on resources with strict schema)
4.0.1
Bug fixes
- Return 400 error response when history is filtered with unknown field
- Fix crash on permissions endpoint when history is enabled (#774)
- Fix crash on history when interacting via the bucket plural endpoint (
/buckets
) (fixes #773)
Internal changes
- Fix documentation of errors codes (fixes #766)
kinto.id_generator
was removed from documentation since it does not
behave as expected (fixes #757, thanks @doplumi)
folder and akinto.core.testing
module was introduced for tests helpers
(fixes #605)- In documentation, link the notion of principals to the permissions page instead
of glossary - Add details about
PATCH
behaviour (fixes #566)
4.0.0
Breaking changes
kinto --version
was renamedkinto version
ResourceChanged
andAfterResourceChanged
events now return
old
andnew
records for thedelete
action. (#751)- Redis backends are not part of the core anymore. (#712).
Usekinto_redis.cache
instead ofkinto.core.cache.redis
Usekinto_redis.storage
instead ofkinto.core.storage.redis
Usekinto_redis.permission
instead ofkinto.core.permission.redis
- Redis listener is not part of the core anymore. (#712)
Usekinto.event_listeners.redis.use = kinto_redis.listeners
instead of
kinto.event_listeners.redis.use = kinto.core.listeners.redis
- Notion of unique fields was dropped from
kinto.core
resources.
Protocol
- Added a
/__version__
endpoint with the version that has been deployed. (#747) - Allow sub-object filtering on plural endpoints (e.g
?person.name=Eliot
) (#345) - Allow sub-object sorting on plural endpoints (e.g
?_sort=person.name
) (#345)
Protocol is now at version 1.9. See API changelog
_.
New features
- Added a new built-in plugin
kinto.plugins.history
that keeps track of every action
that occured within a bucket and serves a stream of changes that can be synced.
See API documentation. - Added a new
--dry-run
option to command-line scriptmigrate
that will simulate
migration operation without executing on the backend (thanks @lavish205! #685) - Added ability to plug custom StatsD backend implementations via a new
kinto.statsd_backend
setting. Useful for Datadog™ integration for example (fixes #626). - Added a
delete-collection
action to thekinto
command. (#727) - Added verbosity options to the
kinto
command. (#745) - Added a built-in plugin that allows to define quotas per bucket or collection. (#752)
Bug fixes
- Fix bug where the resource events of a request targetting two groups/collection
from different buckets would be grouped together. - Fix crash when an invalid UTF-8 character is provided in URL
- Fix crash when provided
last_modified
field is not divisible (e.g. string)
Internal changes
- Huge rework of documentation after the merge of Cliquet into kinto.core (#731)
- Improve the documentation about generating docs (fixes #615)
- Switch from cliquet-pusher to kinto-pusher in Dockerfile and tutorial.
- List posssible response status on every endpoint documentation (#736)
- Remove duplicated and confusing docs about generic resources
- Replace the term
protocol
byAPI
in documentation (fixes #664) - Add load tests presets (exhaustive, read, write) in addition to the existing random. Switched integration test
make loadtest-check-simulation
to run the exhaustive one (fixes #258) - Remove former Cliquet load tests (#733)
- Add a flag to to run simulation load tests on
default
bucket. Usesblog
bucket by default (#733) - Add command-line documentation (#727)
- The
--backend
command-line option forkinto init
is not accepted as first
parameter anymore - Improved parts of the FAQ (#744)
- Improve 404 and 403 error handling to make them customizable. (#748)
kinto.core
resources are now schemaless by default (fixes #719)