Verbose error:

Cannot update Project header at packages/header. It doesn't exist or uses package.json configuration.
at validateProjectConfigurationOperationsWithoutWorkspaceJson (/Users/xxxx/Documents/Lerna_Nx/projectA/node_modules/@jscutlery/semver/node_modules/@nrwl/devkit/src/generators/project-configuration.js:355:15)

I'm getting the same error with a fresh install with nx:

@herrlegno could you provide the output of nx report please?

@herrlegno can you provide the output of nx report please?

@edbzn is there a way to migrate from package.json to project.json that seems to be the way to be able to use this versioning plugin?

@edbzn I found a workaround to make it work. Just add a project.json file with:

{
  "name": <project name>,
  "targets":{}
}

before running

ng g @jscutlery/semver:install

It will add the nx runners to it, and if you run:

nx affected --target version [...options]

after the commits it will run as expected.

For reference after doing what I described in one of my packages I this project.json:

{
  "name": "eslint-config",
  "$schema": "../../node_modules/nx/schemas/project-schema.json",
  "targets": {
    "version": {
      "executor": "@jscutlery/semver:version",
      "options": {
        "preset": "conventional"
      }
    }
  }
}

@edbzn Today I wanted to update a package but it's not working again:

It doesn't detect the changes

@herrlegno does it work when using run-many command?

nx run-many --target version 

Kinda works but It creates also versions for packages that are not modified. Also git is executed in parallel and it doesn't like to do that:

Yeah, you have to explicitly give --parallel=1 for the concurrent Git access, anyway run-many is not what you need. I checked and it seems that actually, our executor is not compatible with package.json based projects. This is something we need to consider in #655, but for now, you need to use a project.json file to be able to configure executors.

@edbzn Today I wanted to update a package but it's not working again:

It doesn't detect the changes

@edbzn sorry for bothering you again. I found out the problem that i mentioned was because i was running affected version with main as base branch and the commits were on main so there was no change. After changing the base branch to origin/main it runs perfectly.

Running this (in my example) works as expected:

nx affected --target version --base=origin/main --parallel=1

Sorry for all the trouble, first time using Nx Automatic versioning.

No problem! Happy it works for you.