Comments (5)
travi
commented on August 15, 2024
The preset you've chosen to use is not a dependency of semantic-release, so you need to install it in addition to semantic-release. You can still do this directly in your workflow without a package.json
from release-notes-generator.
JMLX42
commented on August 15, 2024
@travi I have conventional-changelog-conventionalcommits installed and I still have the problem.
[4:05:29 PM] [semantic-release] › ℹ Running semantic-release version 21.0.2
(node:387) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
[4:05:30 PM] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/changelog"
[4:05:30 PM] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/git"
[4:05:30 PM] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/gitlab"
[4:05:30 PM] [semantic-release] › ✔ Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[4:05:30 PM] [semantic-release] › ✔ Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[4:05:30 PM] [semantic-release] › ✔ Loaded plugin "prepare" from "@semantic-release/changelog"
[4:05:30 PM] [semantic-release] › ✔ Loaded plugin "prepare" from "@semantic-release/git"
[4:05:30 PM] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/gitlab"
[4:05:30 PM] [semantic-release] › ✔ Loaded plugin "success" from "@semantic-release/gitlab"
[4:05:30 PM] [semantic-release] › ✔ Loaded plugin "fail" from "@semantic-release/gitlab"
[4:05:31 PM] [semantic-release] › ✔ Run automated release from branch main on repository https://gitlab-ci-token:[secure]@git.aerys.in/aerys/infrastructure/vendor/semantic-release-docker.git
[4:05:32 PM] [semantic-release] › ✔ Allowed to push to the Git repository
[4:05:32 PM] [semantic-release] › ℹ Start step "verifyConditions" of plugin "@semantic-release/changelog"
[4:05:32 PM] [semantic-release] › ✔ Completed step "verifyConditions" of plugin "@semantic-release/changelog"
[4:05:32 PM] [semantic-release] › ℹ Start step "verifyConditions" of plugin "@semantic-release/git"
[4:05:32 PM] [semantic-release] › ✔ Completed step "verifyConditions" of plugin "@semantic-release/git"
[4:05:32 PM] [semantic-release] › ℹ Start step "verifyConditions" of plugin "@semantic-release/gitlab"
[4:05:32 PM] [semantic-release] [@semantic-release/gitlab] › ℹ Verify GitLab authentication (https://git.aerys.in/api/v4)
[4:05:32 PM] [semantic-release] › ✔ Completed step "verifyConditions" of plugin "@semantic-release/gitlab"
[4:05:32 PM] [semantic-release] › ℹ Found git tag v1.3.1 associated with version 1.3.1 on branch main
[4:05:32 PM] [semantic-release] › ℹ Found 3 commits since last release
[4:05:32 PM] [semantic-release] › ℹ Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[4:05:32 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: ci: temporary inhibit the semantic-release before_script install
[4:05:32 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ The commit should not trigger a release
[4:05:32 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: chore(deps): update node.js to v20
[4:05:32 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ The release type for the commit is patch
[4:05:32 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: ci: use the conventionalcommits for the release notes
[4:05:32 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ The commit should not trigger a release
[4:05:32 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ Analysis of 3 commits complete: patch release
[4:05:32 PM] [semantic-release] › ✔ Completed step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[4:05:32 PM] [semantic-release] › ℹ The next release version is 1.3.2
[4:05:32 PM] [semantic-release] › ℹ Start step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[4:05:32 PM] [semantic-release] › ✘ Failed step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[4:05:32 PM] [semantic-release] › ✘ An error occurred while running semantic-release: Error: Cannot find module 'conventional-changelog-conventionalcommits'
Require stack:
- /builds/aerys/infrastructure/vendor/semantic-release-docker/noop.js
at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15)
at Module._load (node:internal/modules/cjs/loader:975:27)
at Module.require (node:internal/modules/cjs/loader:1225:19)
at require (node:internal/modules/helpers:177:18)
at module.exports (/builds/aerys/infrastructure/vendor/semantic-release-docker/.npm/lib/node_modules/semantic-release/node_modules/import-from/index.js:5:100)
at default (file:///builds/aerys/infrastructure/vendor/semantic-release-docker/.npm/lib/node_modules/semantic-release/node_modules/@semantic-release/release-notes-generator/lib/load-changelog-config.js:28:67)
at generateNotes (file:///builds/aerys/infrastructure/vendor/semantic-release-docker/.npm/lib/node_modules/semantic-release/node_modules/@semantic-release/release-notes-generator/index.js:34:44)
at validator (file:///builds/aerys/infrastructure/vendor/semantic-release-docker/.npm/lib/node_modules/semantic-release/lib/plugins/normalize.js:36:30)
at file:///builds/aerys/infrastructure/vendor/semantic-release-docker/.npm/lib/node_modules/semantic-release/lib/plugins/pipeline.js:38:42
at next (file:///builds/aerys/infrastructure/vendor/semantic-release-docker/.npm/lib/node_modules/semantic-release/node_modules/p-reduce/index.js:16:10) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/builds/aerys/infrastructure/vendor/semantic-release-docker/noop.js'
],
pluginName: '@semantic-release/release-notes-generator'
}
Error: Cannot find module 'conventional-changelog-conventionalcommits'
Require stack:
- /builds/aerys/infrastructure/vendor/semantic-release-docker/noop.js
�[90m at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15)�[39m
�[90m at Module._load (node:internal/modules/cjs/loader:975:27)�[39m
�[90m at Module.require (node:internal/modules/cjs/loader:1225:19)�[39m
�[90m at require (node:internal/modules/helpers:177:18)�[39m
at module.exports �[90m(/builds/aerys/infrastructure/vendor/semantic-release-docker/�[39m.npm/lib/node_modules/�[4msemantic-release�[24m/node_modules/�[4mimport-from�[24m/index.js:5:100�[90m)�[39m
at default �[90m(file:///builds/aerys/infrastructure/vendor/semantic-release-docker/�[39m.npm/lib/node_modules/�[4msemantic-release�[24m/node_modules/�[4m@semantic-release�[24m/release-notes-generator/lib/load-changelog-config.js:28:67�[90m)�[39m
at generateNotes �[90m(file:///builds/aerys/infrastructure/vendor/semantic-release-docker/�[39m.npm/lib/node_modules/�[4msemantic-release�[24m/node_modules/�[4m@semantic-release�[24m/release-notes-generator/index.js:34:44�[90m)�[39m
at validator �[90m(file:///builds/aerys/infrastructure/vendor/semantic-release-docker/�[39m.npm/lib/node_modules/�[4msemantic-release�[24m/lib/plugins/normalize.js:36:30�[90m)�[39m
at �[90mfile:///builds/aerys/infrastructure/vendor/semantic-release-docker/�[39m.npm/lib/node_modules/�[4msemantic-release�[24m/lib/plugins/pipeline.js:38:42
at next �[90m(file:///builds/aerys/infrastructure/vendor/semantic-release-docker/�[39m.npm/lib/node_modules/�[4msemantic-release�[24m/node_modules/�[4mp-reduce�[24m/index.js:16:10�[90m)�[39m {
code: �[32m'MODULE_NOT_FOUND'�[39m,
requireStack: [
�[32m'/builds/aerys/infrastructure/vendor/semantic-release-docker/noop.js'�[39m
],
pluginName: �[32m'@semantic-release/release-notes-generator'�[39m
}
I am not even using npx. Just a global install:
FROM registry.aerys.in/aerys/infrastructure/vendor/rust-docker/x86_64-unknown-linux-musl:1.74.0-0 as rust
FROM node:20.11.1
COPY --from=rust /opt/rust /opt/rust
ENV PATH="$PATH:/opt/rust/cargo/bin"
ENV RUSTUP_HOME=/opt/rust/rustup
# To see why we need to execute `semantic-release-cargo` through `@semantic-release/exec`
# see https://git.aerys.in/aerys/smartshape/smartshape-cli/-/issues/569#note_437864.
# To see why we can't execute the Node.js plugin directly and install the binary,
# see https://git.aerys.in/aerys/test/semantic-release-cargo-test/-/issues/2#note_437918.
#
# renovate: datasource=crate depName=semantic-release-cargo
RUN cargo install [email protected]
RUN npm install --global \
# renovate: datasource=npm depName=semantic-release
[email protected] \
# renovate: datasource=npm depName=@semantic-release/gitlab
@semantic-release/[email protected] \
# renovate: datasource=npm depName=@semantic-release/exec
@semantic-release/[email protected] \
# renovate: datasource=npm depName=@semantic-release/commit-analyzer
@semantic-release/[email protected] \
# renovate: datasource=npm depName=@semantic-release/changelog
@semantic-release/[email protected] \
# renovate: datasource=npm depName=@semantic-release/git
@semantic-release/[email protected] \
# renovate: datasource=npm depName=conventional-changelog-conventionalcommits
[email protected]
# Pin the version of `yarn` to avoid mismatching versions in different projects.
RUN corepack prepare [email protected] && \
yarn set version 3.5.0from release-notes-generator.
travi
commented on August 15, 2024
Running semantic-release version 21.0.2
you are using an old version of semantic-release with the latest version of the conventional-changelog-conventionalcommmits preset. there is a known incompatibility with the latest presets that was fixed in v22 of semantic-release. please upgrade to the latest semantic-release to see if that improves your situation.
from release-notes-generator.
JMLX42
commented on August 15, 2024
That is correct. Somehow I got two versions of release-notes-generator installed. And I ran the wrong/old one.
This is indeed fixed when using the latest version of all packages.
from release-notes-generator.
Related Issues (20)
- Refactor & chore commits not getting includes in changelog HOT 3
- Release notes generation with Bitbucket
- question: link to both GH PR numbers and external issues
- Question: conventionalcommits preset with PR owner
- Defining the commitPartial voids other wirter and presetConfig options
- I need to include other commits than `feat` and `fix`. HOT 3
- Sort commit sections HOT 11
- An error occurred while running semantic-release: Error [ERR_REQUIRE_ESM] HOT 7
- wrong Gitlab issue link in release notes HOT 20
- Plugin ends up abruptly without completition or error, making other plugins not to start HOT 12
- Wrong commit link for Bitbucket HOT 3
- `release skip`-ed commits still get into release notes
- Links to PRs and Contributors list HOT 2
- Unexpected behavior for major updates with conventionalcommits preset HOT 2
- self-hosted GitLab - no issue links in release notes
- Question: Merging pre-release branches & generated changelog
- Question: Mirror release rules to release notes generator? HOT 1
- Question: how can i gruop no-scope commits on a section in release notes generator configuration ?
- conventional-changelog-conventionalcommits v8.0.0 breaks semantic release HOT 28
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from release-notes-generator.