The version history of the metadata syntax is given below.
0.15 - 2019-11-05¶
The condition function
is_master(file_path path), which checks if the given file is an installed master plugin.
0.14 - 2018-12-09¶
Groupdata structure now has a
descriptionkey that takes a string value.
The condition function
product_version(file_path path, version given_version, comparison_operator comparator), which checks against the Product Version field of an executable.
dirtymetadata are now allowed in regex plugin entries.
Tagequality comparisons are now case-sensitive.
Regular expressions in condition strings now use a modified Perl grammar instead of a modified ECMAScript grammar.
namefields still use the modified ECMAScript grammar for regex values. To improve portability and avoid mistakes, it’s best to stick to using the subset of regular expression features that are common to both grammars.
The change in regular expression grammar means that the following regular expression features are no longer supported in condition strings:
\c<letter>control code escape sequences, use
\0null escape sequence, - use
[:s:]character classes, use
(?!<subpattern>)positive and negative lookahead
0.13 - 2018-04-02¶
groupslist to the root of the metadata file format.
groupkey to the plugin data structure.
priorityfield from the plugin data structure.
global_priorityfield from the plugin data structure.
0.10 - 2016-11-06¶
cleankey to the plugin data structure.
global_priorityfield to the plugin data structure.
infokey to the cleaning data structure.
strkey in the localised content data structure to
priorityfield of the plugin data structure now stores values between -127 and 127 inclusive.
Regular expressions no longer accept
\as a directory separator:
/must now be used.
file()condition function now also accepts a regular expression.
active()condition function to also accept a regular expression.
Renamed the dirty info data structure to the cleaning data structure.
regex()condition function, as it has been obsoleted by the
file()function’s new regex support.
0.8 - 2015-07-22¶
namekey to the location data structure.
The documentation now defines the equality criteria for all of the metadata syntax’s non-standard data structures.
Detection of regular expression plugin entries. Previously, a plugin entry was treated as having a regular expression filename if the filename ended with
\.esp. Now, a plugin entry is treated as having a regular expression filename if the filename contains one or more of
verkey in the location data structure.
The documentation gave the values of the
dirtykeys as lists, when they have always been sets.
0.7 - 2015-05-20¶
The message string substitution key, i.e.
sub, in the message data structure.
Support for YAML merge keys, i.e.
Messages may now be formatted using most of GitHub Flavored Markdown, minus the GitHub-specific features (like @mentions, issue/repo linking and emoji).
0.6 - 2014-07-05¶
0.5 - 2014-03-31¶