yes, it seems that previously lerna handled logic of "workspace:" versioning, now after moving to internal implementation of graph #2117 the only workspace handler left is that

      if (currentDepVer.startsWith('workspace:')) {
        depUpdates.push(`\n    * ${depName} bumped to ${newVersionString}`);
      } else if (newVersionString !== origDepVer) {
        depUpdates.push(
          `\n    * ${depName} bumped from ${origDepVer} to ${newVersionString}`
        );
        //handle case when "workspace:" version is used

any idea how to fix it? Rolling back to old version is not a great option since setup needs one of the "new" features

upd. for now latest release-please version not affected by that issue is 16.2.0, my current solution is to use local installation of the package and run it in a pipeline. Not as nice as github action, but works.

Any updates on this issue? We would like to migrate to v4 of release-please-action, which includes a couple fixes from release-please v16 that we've been waiting for, but our project makes use pnpm and workspace:*, so we are stuck in a holding pattern like the original submitter.

Is there any workaround？

Yarn workspaces are also affected. Release please keeps replacing workspace:^ with hardcoded version. Also it seems Linking peer dependencies doesn't work as explained, it updated the peerDependencies field of my package with the updated workspace version.

Could someone explain how node-workspace plugin + yarn/pnpm's workspace:* protocol should work together? I don't quite understand if I need node-workspace plugin at all.

Submitted a PR with a fix.