- Nothing changed yet.
Bug fixes
- Fix redirection for old
?_since
values on changeset endpoints (fixes #299)
New features
- Send cache control headers on old
?_since
redirects (cache for 1 day by default).
Breaking Changes
- No
ResourceEvent
is sent anymore for changes in this virtual monitor/changes collection.
New features
- Add filtering support in monitor/changes changeset endpoint
Bug fixes
- Fix crash when collection is unknown and backend running in readonly mode
Bug fixes
- Bypass storage when redirecting on old
_since
New features
- Redirect clients whose
?_since
value is too old (21 days by default) - Add support for monitor/changes in changeset endpoints (fixes #173)
Bug fixes
- Fix validation rule for
_since
query parameter
Bug fixes
- Include tombstones in changeset endpoint (fixes #175)
- Sort changes explicitly by last_modified descending
Breaking changes
- Switch changeset timestamp from ETag to integer (#168)
New features
- Add changeset endpoint (#154)
Bug fixes
- Fix crash with
If-None-Match: *
(fixes #158)
Bug fixes
- Use explicit resource timestamp from DB instead of event payload
New feature
- Send
Cache-Control
headers if cache busting query parameters or concurrency control request headers are sent (#66)
Breaking changes
- Requires Kinto >= 12
New feature
- Add ability to configure cache control headers (#47)
Bug fixes
- Don't do anything during a
migrate
command (fixes #43).
New feature
- Events are now generated on the monitor/changes collection (#41).
Internal changes
- Get rid of six
Breaking changes
- Upgrade to Kinto 7
Bug fixes
- Disable reify to always get the most accurate timestamp. (#36)
Bug fixes
- Accessing the monitoring collection when no changes occured don't fail anymore (fixes #23)
- The timestamps shown in the monitoring endpoint are now exactly equal (never superior anymore) to the timestamps of the monitored collections.
Breaking changes
- The change endpoint location is now hard-coded (
/buckets/monitor/collections/changes/records
) and cannot be configured. - The permissions principals cannot be specified anymore. The change endpoint is now always public.
- The
monitor
bucket andchanges
collection are not required anymore and are not created anymore. POST
andDELETE
are not supported on the changes endpoint anymore.- Individual entries (eg.
/buckets/monitor/collections/changes/records/{id}
) cannot be accessed anymore. - The listener was dropped. Configuration must be changed:
Before:
kinto.event_listeners = changes
kinto.event_listeners.changes.use = kinto_changes.listener
kinto.event_listeners.changes.http_host = website.domain.tld
kinto.event_listeners.changes.collections = /buckets/settings
/buckets/blocklists/collections/certificates
Now:
kinto.changes.http_host = website.domain.tld
kinto.changes.resources = /buckets/settings
/buckets/blocklists/collections/certificates
- Do not force the timestamp of monitored entries (#27)
- Add the plugin version in the capability (#20)
- Add collections in the capability (#18)
- Add a specific setting to override global
http_host
value (#24)
- Update to
kinto.core
for compatibility with Kinto 3.0. This release is no longer compatible with Kinto < 3.0, please upgrade!
- Addition of the changes capability
- Initial code.
- Bucket and collection name configuration.
- Changes read permissions configuration.
- Selection of buckets and collections to follow configuration.