chore: generate browser versions when doing release #999
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This introduces a handful of new markdown preprocessor commands to
insert browser versions:
GEN:chromium-version-if-release
- inserts current Chromium versionif we're doing release; noop otherwise.
GEN:firefox-version-if-release
- inserts current Firefox versionif we're doing release; noop otherwise.
And to generate badge links:
GEN:chromium-version-badge-if-release
- inserts current Chromium versionbadge if we're doing release; noop otherwise.
GEN:firefox-version-badge-if-release
- inserts current Firefox versionbadge if we're doing release; noop otherwise.
This doesn't touch webkit at all - we're yet to figure what to do with
webkit version.
NOTE: versions will be updated only once we release. This way our
README.md always represents last released version.