Closed IdecEddy closed 2 years ago
As an update, I looked though the log and found that the @semantic-release/commit-analyzer found that The commit should not trigger a release
but it still did.
[9:16:47 PM] [semantic-release] › ℹ Found 2 commits since last release
[9:16:47 PM] [semantic-release] › ℹ Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[9:16:47 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: fix(CICD): I want to test to make sure releases happen only on the app that is being updated.
[9:16:47 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ The release type for the commit is patch
[9:16:47 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: chore(release): 1.0.4 [skip ci]
# [app1-express-v1.0.4](link) (2022-07-01)
### Bug Fixes
* **API:** I am taking out some unneeded text. ([ceb7476](link))
[9:16:47 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ The commit should not trigger a release
[9:16:47 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ Analysis of 2 commits complete: patch release
[9:16:47 PM] [semantic-release] › ✔ Completed step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[9:16:47 PM] [semantic-release] › ℹ Start step "analyzeCommits" of plugin "@semantic-release/exec"
[9:16:47 PM] [semantic-release] › ✔ Completed step "analyzeCommits" of plugin "@semantic-release/exec"
[9:16:47 PM] [semantic-release] › ℹ Start step "analyzeCommits" of plugin "@semantic-release/exec"
[9:16:47 PM] [semantic-release] › ✔ Completed step "analyzeCommits" of plugin "@semantic-release/exec"
[9:16:47 PM] [semantic-release] › ℹ The next release version is 1.1.8
[9:16:47 PM] [semantic-release] › ℹ Start step "verifyRelease" of plugin "@semantic-release/exec"
[9:16:47 PM] [semantic-release] › ✔ Completed step "verifyRelease" of plugin "@semantic-release/exec"
[9:16:47 PM] [semantic-release] › ℹ Start step "verifyRelease" of plugin "@semantic-release/exec"
[9:16:47 PM] [semantic-release] › ✔ Completed step "verifyRelease" of plugin "@semantic-release/exec"
[9:16:47 PM] [semantic-release] › ℹ Start step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[9:16:47 PM] [semantic-release] › ✔ Completed step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[9:16:47 PM] [semantic-release] › ℹ Start step "generateNotes" of plugin "@semantic-release/exec"
[9:16:47 PM] [semantic-release] › ✔ Completed step "generateNotes" of plugin "@semantic-release/exec"
[9:16:47 PM] [semantic-release] › ℹ Start step "generateNotes" of plugin "@semantic-release/exec"
[9:16:47 PM] [semantic-release] › ✔ Completed step "generateNotes" of plugin "@semantic-release/exec"
[9:16:47 PM] [semantic-release] › ℹ Start step "prepare" of plugin "@semantic-release/changelog"
[9:16:47 PM] [semantic-release] [@semantic-release/changelog] › ℹ Update /builds/project/sandbox/emundo/app1-nextjs/apps/app1-nextjs/CHANGELOG.md
[9:16:47 PM] [semantic-release] › ✔ Completed step "prepare" of plugin "@semantic-release/changelog"
[9:16:47 PM] [semantic-release] › ℹ Start step "prepare" of plugin "@semantic-release/npm"
[9:16:47 PM] [semantic-release] [@semantic-release/npm] › ℹ Write version 1.1.8 to package.json in /builds/app1/sandbox/emundo/app1-nextjs/apps/app1-nextjs
app1-website
v1.1.8
that and the exec step also runs when I don't think it should.
Im just silly looks like I forgot to add "extends": "semantic-release-monorepo" to one of the app I was using as the ignore test. Remember to look over all your work friends.
Hello,
I am using terborepo to manage my monorepo. I made a change to a file in one of the packages in my monorepo (
app1-express
). When the semantic-release step ran in my GitLab CI/CD it released both apps and raised the version number in both of the apps. I ran yarn semantic-release in both app1-express and app2-nextjs directory.Tree of my project's apps dir
what my releaserc.json
Gitlab CICD config
yarn release looks like this in package.json script:
"release": "yarn semantic-release"
I am not sure if semantic-release-monorepo would affect the
"@semantic-release/npm",
plugin that updates the package version. Can you provide any guidance on this topic?