scratchfoundation/scratch-semantic-release-config
1
0
Fork 0
mirror of https://github.com/scratchfoundation/scratch-semantic-release-config.git synced 2024-11-24 00:17:55 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
scratch-semantic-release-co.../release.config.js

32 lines
904 B
JavaScript
Raw Normal View History

refactor: fork from @jedmao/semantic-release-npm-github-config@1.0.9 * Update repository references * Update `package-lock.json` * Rename `.releaserc.json` to `release.config.js` * A few other minor tweaks
2022-05-20 13:14:49 -04:00
module.exports = {
fix(ci): fix release config by moving branches setting Instead of merging the configuration values in `package.json` with those in `relase.config.js`, the `package.json` configuration was treated as the only configuration.
2022-05-20 20:51:28 -04:00
"branches": ["main"],
style: reformat release.config.js
2022-05-20 20:31:59 -04:00
"plugins": [
"@semantic-release/commit-analyzer",
"@semantic-release/release-notes-generator",
[
"@semantic-release/changelog",
{
"changelogTitle": "# Changelog\n\nAll notable changes to this project will be documented in this file. See\n[Conventional Commits](https://conventionalcommits.org) for commit guidelines."
}
],
[
fix(ci): fix release config by moving branches setting Instead of merging the configuration values in `package.json` with those in `relase.config.js`, the `package.json` configuration was treated as the only configuration.
2022-05-20 20:51:28 -04:00
"@semantic-release/git",
style: reformat release.config.js
2022-05-20 20:31:59 -04:00
{
fix(ci): fix release config by moving branches setting Instead of merging the configuration values in `package.json` with those in `relase.config.js`, the `package.json` configuration was treated as the only configuration.
2022-05-20 20:51:28 -04:00
"message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
style: reformat release.config.js
2022-05-20 20:31:59 -04:00
}
],
[
fix(ci): fix release config by moving branches setting Instead of merging the configuration values in `package.json` with those in `relase.config.js`, the `package.json` configuration was treated as the only configuration.
2022-05-20 20:51:28 -04:00
"@semantic-release/npm",
style: reformat release.config.js
2022-05-20 20:31:59 -04:00
{
fix(ci): fix release config by moving branches setting Instead of merging the configuration values in `package.json` with those in `relase.config.js`, the `package.json` configuration was treated as the only configuration.
2022-05-20 20:51:28 -04:00
"tarballDir": "pack"
style: reformat release.config.js
2022-05-20 20:31:59 -04:00
}
],
[
fix(ci): fix release config by moving branches setting Instead of merging the configuration values in `package.json` with those in `relase.config.js`, the `package.json` configuration was treated as the only configuration.
2022-05-20 20:51:28 -04:00
"@semantic-release/github",
style: reformat release.config.js
2022-05-20 20:31:59 -04:00
{
fix(ci): fix release config by moving branches setting Instead of merging the configuration values in `package.json` with those in `relase.config.js`, the `package.json` configuration was treated as the only configuration.
2022-05-20 20:51:28 -04:00
"assets": "pack/*.tgz"
style: reformat release.config.js
2022-05-20 20:31:59 -04:00
}
]
fix(ci): fix release config by moving branches setting Instead of merging the configuration values in `package.json` with those in `relase.config.js`, the `package.json` configuration was treated as the only configuration.
2022-05-20 20:51:28 -04:00
],
refactor: fork from @jedmao/semantic-release-npm-github-config@1.0.9 * Update repository references * Update `package-lock.json` * Rename `.releaserc.json` to `release.config.js` * A few other minor tweaks
2022-05-20 13:14:49 -04:00
};
Reference in a new issue Copy permalink