Steps to reproduce

1.  Create a content app and add content to it and publish content
2.  Create delivery endpoint for that content
3. Hit the endpoint to get some content
4. Change some content in the app and publish it again.
5. Make the exact same request to the delivery endpiont

.. Logs, screenshots, gifs...

Expected results

Endpoint returns newly published content

Justify non-trivial expectations with a link to a doc or a relevant discussion.

Actual results

Endpoint returns cached content

Workaround

Create cache config for that content app

or 

Append "cache busting" querystring to the request to endpoint so that the cache does not recognize it. 

Notes

As a developer I expect that the cache will not deliver stale content after a publish is made that affects that content.
It looks like for newly created content types/apps the publishing process does not trigger cache flush for respective workspace in public instances.
Pages (website workspace) works as expected.

Development notes

Also check that this is fixed for GraphQL endpoint.