feat(api-v2): Accept custom timestamps in update/delete requests #1686
This also fixes a bug: the custom timestamp submitted when creating a value should be
Maybe a few remarks, regarding breaking changes.
We are allowed to make braking changes to features, provided we have a sufficiently long deprecation timeframe. We talked about a timeframe of 12 months so that external projects using the backend API have sufficient time to react before their application will potentially break. The deprecation timer starts running when we make an official release and deploy it into production. This also requires that the release notes mention the deprecation prominently.
If we see that no one is using a deprecated feature anymore, which will require to log usage of deprecated features, then we can remove it sooner, or even immediately.
In the case of the mentioned deprecation in this PR, the deprecation timer will start as soon as we make a non-RC release of