moving release.config.js to .config folder not reading configuration correctly. version 23.0.0 #3158
Replies: 6 comments 12 replies
-
could you switch to using a |
Beta Was this translation helpful? Give feedback.
-
Hi, I'm facing the same issue since upgrade to v23. My setup is a GitlabCI pipeline (in a monorepo) which is launching the semantic-release cli using some args (specific for each subrepo - defined by the CI pipeline) and a dynamic JS config for semantic-release (which contains common parameters such as plugins etc...) Historically, the config was named Everything is working fine with v22, so I'm sticking with this version for the moment. |
Beta Was this translation helpful? Give feedback.
-
it probably should be a proper issue/bug instead of community discussion |
Beta Was this translation helpful? Give feedback.
-
Can confirm that It doesnt recognize any of my configuration files, no matter the extension or the location of the file. |
Beta Was this translation helpful? Give feedback.
-
Have y'all tried
|
Beta Was this translation helpful? Give feedback.
-
My issue was that my |
Beta Was this translation helpful? Give feedback.
-
Current behavior
When running a release, the config is not being picked up even though the breaking changes section says explicitly that i should move the
release.config.js
file into the.config
folder.with a file
.config/release.config.js
containing a branch configuration:When running
semantic-release
, it has an error saying it must have 1-3 release branches configured:To Reproduce:
Have a basic node library with a minimum
release.config.js
file in the .config folder and branches configured to ['main']run the
semantic-release --dry-run
(with local repo and branches if necessary)This works fine if the
release.config.js
file is in the project's root directory, which is also unexpected behaviourExpected behavior
Expect for the release to pick up the correct
.config/release.config.js
file as described in the breaking-changes of version 23.0.0semantic-release
version23.0.0
CI environment
buildkite
Plugins used
commit-analyzer, release-notes-generator, npm, github, git
semantic-release
configurationCI logs
ERELEASEBRANCHES The release branches are invalid in the
branches
configuration.| [2024-01-23T06:04:30Z] [ci:release] A minimum of 1 and a maximum of 3 release branches are required in the branches configuration (https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#branches).
| [2024-01-23T06:04:30Z] [ci:release]
| [2024-01-23T06:04:30Z] [ci:release] This may occur if your repository does not have a release branch, such as master.
| [2024-01-23T06:04:30Z] [ci:release]
| [2024-01-23T06:04:30Z] [ci:release] Your configuration for the problematic branches is [].
| [2024-01-23T06:04:30Z] [ci:release]
| [2024-01-23T06:04:30Z] [ci:release] AggregateError:
| [2024-01-23T06:04:30Z] [ci:release] SemanticReleaseError: The release branches are invalid in the
branches
configuration.| [2024-01-23T06:04:30Z] [ci:release] at default (file:///opt/app/node_modules/semantic-release/lib/get-error.js:6:10)
| [2024-01-23T06:04:30Z] [ci:release] at file:///opt/app/node_modules/semantic-release/lib/branches/index.js:45:19
| [2024-01-23T06:04:30Z] [ci:release] at Array.reduce ()
Beta Was this translation helpful? Give feedback.
All reactions