-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in semantic-release-monorepo: "Cannot read properties of undefined (reading 'map')" During Automated Publishing in Monorepo #158
Comments
I'm facing the exact same issue: [10:07:00 AM] [semantic-release] › ✘ An error occurred while running semantic-release: TypeError: Cannot read properties of undefined (reading 'map')
at withFiles (file:///runner/_work/acme-react-libraries/acme-react-libraries/node_modules/semantic-release-monorepo/src/only-package-commits.js:26:13)
at onlyPackageCommits (file:///runner/_work/acme-react-libraries/acme-react-libraries/node_modules/semantic-release-monorepo/src/only-package-commits.js:38:34)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async file:///runner/_work/acme-react-libraries/acme-react-libraries/node_modules/semantic-release-monorepo/src/options-transforms.js:8:58
at async file:///runner/_work/acme-react-libraries/acme-react-libraries/node_modules/semantic-release-monorepo/src/lens-utils.js:7:17
at async file:///runner/_work/acme-react-libraries/acme-react-libraries/node_modules/semantic-release-monorepo/src/only-package-commits.js:86:5 {
pluginName: '[Function: semantic-release-monorepo]'
} Was you able to solve that @wojtekKrol ? |
Unfortunately not yet |
@juliosampaio please ping me once you resolve your problem okey? |
Hey @wojtekKrol , we actually decided to use Changesets instead, which is the opposite approach on all the automation provided by semantic-release, but fits perfectly on our use case. I'm glad we did tbh 😀 |
@juliosampaio and do you have case that includes monorepo with multiple libraries published to npm/github registry? Can you share configs? Thanks |
This seems to happen if another plugin throws an error. I had to comment out |
Oh great! Same here, thanks for pointing it out. |
I am trying to set up a monorepo with automated publishing of packages to both npm and GitHub Packages. My goal is to only publish packages that have been updated (detecting changes in files). I have configured my repository to use
semantic-release
withsemantic-release-monorepo
, but I am encountering errors during the release process.This is the repository: https://github.com/paxcode-it/zodify-forms/tree/dev
Current Setup
Monorepo Structure
Release Configuration (
release.config.cjs
) same for each packageGitHub Actions CI/CD Configuration
Problem Encountered
I am encountering an error during the release process:
Additionally, I received an
ENOGHTOKEN
error indicating no GitHub token is specified.Full logs:https://github.com/paxcode-it/zodify-forms/actions/runs/10028361403/job/27715190158
Question
Is it possible to achieve what I want using
semantic-release-monorepo
? Specifically, I need to:If there are any alternative approaches or additional configurations required to achieve this, I would appreciate any guidance or examples. ( I couldn't find any open source project with those requirements)
Thank you
The text was updated successfully, but these errors were encountered: