[bug] semantic-release-monorepo ignores pkgRoot about semantic-release-monorepo

[iknowcss]

@eng-dibo I'm affected by this as well. Today I tried downgrading my @semantic-release/npm version down from 9.0.1 to 8.0.3 and that seemed to fix the problem. Does that fix the issue in your example repo?

[iknowcss]

@eng-dibo I just started using this repo, damn I didn't realize there wasn't much (or any?) activity in the last year. @pmowrer are you still actively developing this or have you set it aside temporarily?

[pmowrer]

@iknowcss This project is essentially in maintenance mode. The aim is to keep pace with changes to semantic-release, which seems to have slowed down significantly in recent years. Haven't had much time to commit to open source lately - kids 🤷

[its-dibo]

anyone here?

[its-dibo]

@eng-dibo I'm affected by this as well. Today I tried downgrading my @semantic-release/npm version down from 9.0.1 to 8.0.3 and that seemed to fix the problem. Does that fix the issue in your example repo?

finally, someone came here!! it seems this repo is not maintained anymore and we need to migrate to another solution

[its-dibo]

confirmed as this issue only occurs in v9, v8 is more stable

[iknowcss]

Yeah fair enough, thanks for your work on it so far anyway. We have a way forward now at least. Take care 🙏

[its-dibo]

The aim is to keep pace with changes to semantic-release

we just need your help to fix this vital issue

[iknowcss]

@eng-dibo is it an issue with this project or with semantic-release? semantic-release did a major upgrade so I would guess they've changed some API. It might not be too difficult to fix. If someone like yourself put up a PR to fix it then maybe Patrick could review and merge in between juggling kids?

[greglbd]

This issue is actually from semantic-release/npm see semantic-release/npm#504

and this PR that fixes it semantic-release/npm#531 - the PR however is only for v10 so that will be an issue but the thread related to the issue does have a way to patch semantic-release/npm