Publishers can opt into LTS by prepending script tag sources with /lts, ex. https://cdn.ampproject.org/lts/v0.js. There are two ways this could be incorporated into AMP Optimizer, and either or both could be useful.

Augment RuntimeVersion to support providing the LTS RTV

The section on Versioned AMP Runtime shows publishers how to use the RuntimeVersion class to pull the latest Stable or Beta (names outdated, see ampproject/amphtml#25560) RTV and provide that version to the transformer. The https://cdn.ampproject.org/rtv/metadata endpoint now includes a ltsRuntimeVersion property which could be used to support an { lts: true } option provided to RuntimeVercsion (note that this would have to be mutually exclusive with { canary: true }.

On a side note, the term "canary" was overloaded and has since been dropped in favor of Beta in most official documentation and communications. It may be worth updating the AMP Optimizer to reflect these changes.

This would allow publishers who use the AMP Optimizer frequently to provide LTS as an option and continuously have their AMP URLs rewritting to RTV-locked versions, each time using the current LTS RTV. This has the typical cache benefits of RTV-locked URLs

Augment RewriteAmpUrls to support the unversioned LTS runtime

Publishers may wish to use the LTS runtime and extensions without re-running the AMP Optimizer for new LTS releases or cherry-picks. The RewriteAmpUrls transformer could be modified to allow rewriting from unversioned standard AMP URLs to unversioned LTS URLs (ex. https://cdn.ampproject.org/v0.js --> https://cdn.ampproject.org/lts/v0.js). LTS unversioned URLs have better cache behavior, as their lifetime is expected to be one months instead of one week (but not as long as RTV URLs, which are expected never to change).

Feature request: Support LTS as runtime version in AMP Optimizer #629

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions