'src' attribute set to invalid in amp-mustache script

[Dnguye92]

What's the issue?

By simply including the amp-mustache script tag <script async custom-template="amp-mustache" src="https://cdn.ampproject.org/v0/amp-mustache-0.2.js"></script> I am seeing an error from the AMP extension stating The attribute 'src' in tag 'amp-mustache extension .js script' is set to the invalid value .

How do we reproduce the issue?

Can't replicate this inside of a jsbin but even by simply using amp-mustache in the playground (https://ampbyexample.com/playground/) you can see this error in the chrome extension

1. Go to http://jsbin.com/vobolelage/edit?html,output
2. Copy the code on the left side of the bin and past into https://ampbyexample.com/playground/

What browsers are affected?

As of right now I only see the error on Chrome on Desktops

Which AMP version is affected?

<script async src="https://cdn.ampproject.org/v0.js"></script>

[jpettitt]

Confirmed - search console is telling people to upgrade to 0.2 but 0.2 is failing the JS validator

[dreamofabear]

Looks like there's some skew in the deployment pipeline.

version: 0.2 and deprecated_version: 0.1 were added in the same PR: https://github.com/ampproject/amphtml/pull/16201/files#diff-920b14e1d472072d04dcbfc41ab50294R29

[cramforce]

Versions should not be introduced and deprecated in the same release cycle for many reasons.

[cramforce]

@Gregable for when the skew would be resolved.

[jaygray0919]

it's difficult to over-emphasize @cramforce Malte's maxim. It's central to the immutable systems concept practiced at Netflix and advocated by folks like Rich Hickey (https://en.wikipedia.org/wiki/Clojure). You can't breaking existing systems; folks have to voluntarily subscribe to new services. @choumx William has compelling reason to use a new service, but it's my decision when to roll-it-out.

[cramforce]

@jaygray0919 Note, that AMP itself is deployed as an an "evergreen" system and it isn't possibly to version lock to the patch level.

The version skew issue in the validator was resolved. @choumx We can call this fixed, right?

We'll follow up with a quick postmortem, since was a process problem.

[dreamofabear]

Yes, verified that amp-mustache-0.2.js is now valid on both JS and C++ validators.

[Gregable]

This is now resolved.

Validator rules were updated to simultaneously add support for 0.2 and add a deprecation warning for 0.1. These rules get released at different schedules to different Google products. In this case, Search Console picked up the rules first a few hours ago and began displaying the deprecation warning. The Javascript Validator interfaces, such as the extension you noticed, picked up the change a few minutes ago.

In order to see the changes in your extension faster, you may need to clear your cache / restart your browser. You may also just try to force refresh the code here: https://cdn.ampproject.org/v0/validator.js