feat: release metadata #457
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
achingbrain
approved these changes
Feb 14, 2020
SemVer spec allows to the version contain a metadata about the build using format <semver>+<metadata. This patch extends the release task with ability to specify metadata to be appended to the version.
AuHau
force-pushed
the
auhau/feat/release_metadata
branch
from
aabb432 to
83d7831
Compare
Member
|
Closing as semantic-release is now used for releases so we'd need to find another way to do this, if it's still desirable. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
SemVer spec allows to the version contain a metadata about the build
using format
<semver>+<metadata>. This patch extends the release taskwith ability to specify metadata to be appended to the version.
This will be used for example in
js-ipfs-repo-migrationsto give information about what latest migration does the release contain as discussed ipfs/js-ipfs-repo-migrations#1 (comment)