b2c1b2c670
BREAKING CHANGE: this feature change the way semantic-release keep track of the channels on which a version has been released. It now use a JSON object stored in a [Git note](https://git-scm.com/docs/git-notes) instead of Git tags formatted as v{version}@{channel}. The tags formatted as v{version}@{channel} will now be ignored. If you have made releases with v16.0.0 on branches other than the default one you will have to update your repository. The changes to make consist in: - Finding all the versions that have been released on a branch other than the default one by searching for all tags formatted v{version}@{channel} - For each of those version: - Create a tag without the {@channel} if none doesn't already exists - Add a Git note to the tag without the {@channel} containing the channels on which the version was released formatted as `{"channels":["channel1","channel2"]}` and using `null` for the default channel (for example.`{"channels":[null,"channel1","channel2"]}`) - Push the tags and notes - Update the GitHub releases that refer to a tag formatted as v{version}@{channel} to use the tag without it - Delete the tags formatted as v{version}@{channel}
30 lines
557 B
JavaScript
30 lines
557 B
JavaScript
const RELEASE_TYPE = ['patch', 'minor', 'major'];
|
|
|
|
const FIRST_RELEASE = '1.0.0';
|
|
|
|
const FIRSTPRERELEASE = '1';
|
|
|
|
const COMMIT_NAME = 'semantic-release-bot';
|
|
|
|
const COMMIT_EMAIL = 'semantic-release-bot@martynus.net';
|
|
|
|
const RELEASE_NOTES_SEPARATOR = '\n\n';
|
|
|
|
const SECRET_REPLACEMENT = '[secure]';
|
|
|
|
const SECRET_MIN_SIZE = 5;
|
|
|
|
const GIT_NOTE_REF = 'semantic-release';
|
|
|
|
module.exports = {
|
|
RELEASE_TYPE,
|
|
FIRST_RELEASE,
|
|
FIRSTPRERELEASE,
|
|
COMMIT_NAME,
|
|
COMMIT_EMAIL,
|
|
RELEASE_NOTES_SEPARATOR,
|
|
SECRET_REPLACEMENT,
|
|
SECRET_MIN_SIZE,
|
|
GIT_NOTE_REF,
|
|
};
|