1 <h1 id=
"version">Manifest - Version
</h1>
4 One to four dot-separated integers
5 identifying the version of this extension.
6 A couple of rules apply to the integers:
7 they must be between
0 and
65535, inclusive,
8 and non-zero integers can't start with
0.
9 For example,
99999 and
032 are both invalid.
13 Here are some examples of valid versions:
17 <li> <code>"version":
"1"</code> </li>
18 <li> <code>"version":
"1.0"</code> </li>
19 <li> <code>"version":
"2.10.2"</code> </li>
20 <li> <code>"version":
"3.1.2.4567"</code> </li>
24 The autoupdate system compares versions
25 to determine whether an installed extension
27 If the published extension has a newer version string
28 than the installed extension,
29 then the extension is automatically updated.
33 The comparison starts with the leftmost integers.
34 If those integers are equal,
35 the integers to the right are compared,
37 For example,
1.2.0 is a newer version than
1.1.9.9999.
41 A missing integer is equal to zero.
42 For example,
1.1.9.9999 is newer than
1.1.
46 For more information, see
47 <a href=
"http://developer.chrome.com/extensions/autoupdate">Autoupdating
</a>.
50 <h2 id=
"version_name">Version Name
</h2>
53 In addition to the version field, which is used for update purposes,
54 version_name can be set to a descriptive version string and will be used for
55 display purposes if present.
59 Here are some examples of version names:
63 <li> <code>"version_name":
"1.0 beta"</code> </li>
64 <li> <code>"version_name":
"build rc2"</code> </li>
65 <li> <code>"version_name":
"3.1.2.4567"</code> </li>
69 If no version_name is present, the version field will be used for
70 display purposes as well.