See:

• A CDN for the AMP runtime section in the OpenJS Foundation application.

• The FAQ on the OpenJS Foundation announcement:

  Currently, the AMP runtime is hosted on the same infrastructure as the Google AMP Cache. Doesn’t this present serious issues?

  The end goal is to separate the AMP runtime from the Google AMP Cache. The Project is currently in the incubating stage and Project leaders are still determining the next steps. Ideally, hosting and deployment of the AMP runtime to the CDN would fall under the purview of the OpenJS Foundation, much like the foundation is handling other projects CDNs, such as the jQuery CDN.

  Untangling the runtime from the cache is a complex endeavor requiring significant investments of time and effort which would be planned and implemented in collaboration with the foundation and industry stakeholders during and after incubation.

  The OpenJS Foundation CPC is committed to having a long-term strategy in place to address this issue by the end of AMP’s incubation.

This should notably:

• be done in collaboration with the foundation and the CPC,
• describe the difference between the proprietary AMP caches, such as Google's or Bing's, and the hosting of the AMP runtime,
• include a projected timeframe for dis-entangling the two,
• specify the domain(s) on which the AMP runtime would be hosted,
• clarify that AMP caches would probably host their own copy of the runtime (and that cached AMP pages would be transformed accordingly as part of the pre-caching transform process),
• describe by whom the supporting infrastructure would be provided, how it would be maintained, and how it would be governed,
• describe the deployment process and related security considerations, and
• describe the privacy policy under which the runtime would be hosted.

See ampproject/amphtml#32195 for more details

What was accomplished?

• Transformed AMP validation, all required validation is code complete.

What was accomplished?

• Removed error categories in AMP Validator, and rev’d to Node 12.
• Above caused some incompatibility issues, which have now been resolved.
• Added SameSite=none to AMP CID cookie.

What was accomplished?

• Signed Exchanges:
  • AMP Packager can now be deployed on Google Cloud. Instructions
  • AMP Packager now supports docker multi-stage builds reducing the image sizes by 99%. #402
  • Various bugfixes to NGINX Signed Exchange Module.
• Google AMP Cache relevant updates:
  • New origin mapping (0-example-com-0) live. #26205
  • Limited the maximum generated image srcset to 820px in the Cache to improve LCP.
  • Experiment running to have the AMP cache prefetch a heuristically determined hero image, similar to what the AMP packager does for AMP SXG documents.
  • DOM Purify investigation, mentioned at last update, resulted in no planned cache changes.
• Major revamp of the AMP CSS validation engine. This was designed to support a request to have a increasingly divergent CSS specification for the AMP Email specification. Some of the addressed issues on Github include #27507, #27239, and #12651. We now support independednt per-format css properties, vendor-prefixes, byte lengths, and URL validation.
• Progress towards open sourcing the C++ AMPHTML Validator, but work remains ongoing.
• Design agreed on with OpenJS Foundation for disentangling the AMP Runtime from Google's Cache domains. #13

What's next?

• Bring the Web Packager towards feature parity with the AMP Packager to further support building non-AMP Signed Exchanges. For example, adding support for ACME cert renewal.
• Complete the C++ Validator Open-Sourcing.
• Add a prometheus endpoint to the AMP Packer for the next release. #357
• Investigating Google Cloud Click-to-deploy marketplace inclusion for the AMP Packager.
• Wrap up the Google AMP Cache hero image experiment mentioned above.

What was accomplished?

• More cert validation.
• Serve-side infrastructure in place to fetch SXG + cert and validate both.
• SXG I2S has all 3 LGTMs
• Validator has a rule type that allows for ignoring URL length in CSS length.
• Validator enables and disable rules based on type identifiers.
• Validator validates transformed AMP.

What is next?

• Relax CSP requirements for AMP Packager
• Validate server-side rendering transforms.
• Validate URL rewrites transform.

What was accomplished?

• CSP for Signed Exchanges relaxed to support some publisher CSP directives.
• Validator value blacklists for tag using the name and id attributes.
• Cache requires transformed attribute for SXG ingestion.

What was accomplished?

• Convert amppkg from dep to go mod
• Validator verifies that template=”” matches a template id on the page
• Beginning work on ACME cert renewal in amppkg
• Welcome Allan Banaag to https://github.com/ampproject/wg-caching
• <style amp-custom-length-check> special error in AMP Validator

This update includes several previous weeks.

What was accomplished?

• Restore dns-prefetch cache transformers; broken recently.
• Major changes to Email Validator to better match Gmail filtering rules.
• Javascript fix to implement the 1000 byte inline CSS limit.
• Fixed inner != outer issue in amppackager.
• WIP improving/defining amppkg release process

What was accomplished?

• Basic image preloading in amppkg

What was accomplished

• AMP actions validator rules now available.
• Correct handling of document fragments in the cache. #19688
• Transformed AMP SXG now include
  • version of transformers used
  • original CSS string fragments
  • protect against data:...</style> in CSS
  • css escaping logic
• Validation of transformer cdn and version

What's next

• Transformed AMP SXG to
  • strip comments from script tags
• Validator to enable/disable tagspec based on type identifiers.

What was accomplished?

• Prep for SXG Contributor Summit Talk next week

What was accomplished?

• Web Packager: Added option to limit byte size / signing duration
• nginx-sxg-module: Serve cert-chain with fresh OCSP; automated .deb release with GH Actions
• libsxg: Add documentation & man file

What's next?

• amppackager: Add Prometheus monitoring endpoint
• Initial release of C++ HTML Parser leading to C++ AMP Validator.

What was accomplished?

• AMP Validation limit for CSS transitioned from 50,000 to 75,000 bytes.
• Open-Sourced C++ HTML Parser.
• Validator Chrome extension updated to include support for Chrome v80.
• AMP Packager v3 released, includes:
  • Experimental ACME support
  • SSR no longer re-adds boilerplate
  • No longer strip <script type={text,mustache}>
  • Allow self-signed certs in dev
  • health check endpoint
• Released SXG nginx module.
• Significant progress in producing a Docker image for running AMP Packager.

What's next?

• C++ AMPHTML Validator
• AMP Packager docker image and instructions for integrating into web sites.
• Investigate and begin work to remove need for DOM Purify on some AMP pages as served by the AMP Cache.

What was accomplished?

• Released amppkg v2.
• Fixed etag issue with AMP Packager’s certificates.
• Meta tag fix to transformers in AMP Cache, cease moving them all to head.