chrome/common/extensions/docs/templates/articles/manifest/manifest_version.html

   1 <h1 id="manifest_version">Manifest Version</h1>
   2
   3 <p>
   4 One integer specifying the version of the manifest file format your package
   5 requires. As of Chrome 18, developers <em>should</em> specify <code>2</code>
   6 (without quotes) to use the format as described by this document:
   7 </p>
   8
   9 <pre data-filename="manifest.json">
  10 "manifest_version": 2
  11 </pre>
  12
  13 <p>
  14 Consider manifest version 1 <em>deprecated</em> as of Chrome 18. Version 2 is
  15 not yet <em>required</em>, but we will, at some point in the not-too-distant
  16 future, stop supporting packages using deprecated manifest versions. Extensions,
  17 applications, and themes that aren't ready to make the jump to the new manifest
  18 version in Chrome 18 can either explicitly specify version <code>1</code>, or
  19 leave the key off entirely.
  20 </p>
  21
  22 <p>
  23 The changes between version 1 and version 2 of the manifest file format are
  24 described in detail in <a href="http://developer.chrome.com/extensions/manifestVersion">the
  25 <code>manifest_version</code> documentation.</a>
  26 </p>
  27
  28 <p class="caution">
  29   Setting <code>manifest_version</code> 2 in Chrome 17 or lower is not
  30   recommended. If your extension needs to work in older versions of Chrome,
  31   stick with version 1 for the moment. We'll give you ample warning before
  32   version 1 stops working.
  33 </p>