BREAKING.md

Breaking Changes

This branch is a test to see how specific versions of helix services can be selected in order to give a preview of upcoming breaking changes.

How to publish

DON'T PUBLISH TO THE REAL PAGES Service (yet)

hlx publish --custom-vcl='vcl/extensions.vcl'

Example Request

• https://breaking-september--pages--adobe.99productrules.com/premiere/en/yts-livestream

Selected Services

helix-pipeline

Note: The pipeline version needs to be locked via the package.json

Pipeline that enables the new version-lock feature

• adobe/helix-pipeline#840
• https://github.com/adobe/helix-pipeline.git#helix-lock-support

helix-dispatch

Note: The dispatch version needs to be locked via the extensions.vcl

Dispatch that enables the new version-lock feature

• adobe/helix-dispatch#338
• /helix/helix-services/dispatch@ci1939

helix-contentproxy

Contentproxy that enables the new version-lock feature

• adobe/helix-content-proxy#155
• /helix/helix-services/content-proxy@ci830

helix-gdocs2md

https://github.com/adobe/helix-gdocs2md/pull/346

• Google docs converter that has a slight different table handling.

• Google docs supports author friendly urls

• /helix/helix-services/gdocs2md@ci1542

helix-data-embed

The response body is no longer a JSON array, but an object that contains a limit, offset, total and data property.

• adobe/helix-data-embed#136
• /helix/helix-services/data-embed@ci1003

TODO:

• hacking the x-ow-version-lock and dispatch version to the extensions is not so nice. could also be a property of a strain.
• add simple mechanism to tag some PRs in order to get a stable CI version.
• add a tool to collect/update tagged services