feat(release): support groupPreVersionCommand for release groups

[jogelin]

Current Behavior

In Nx release configuration, the property preVersionCommand can be set only at the root level in the nx.json:

"release": {
    "version": {
        "preVersionCommand": "nx run-many -t build"
    }
},    

It is not possible to specify it per group meaning that if we want to release only one group, we have to build all releasable projects.

Expected Behavior

We should be able to specify preVersionCommand per group:

"release": {
    "groups": {
        "toolkits": {
            "projects": ["*-toolkit"],
            "version": {
                "groupPreVersionCommand": "nx run-many -t build -p \"*-toolkit\""
             }
        }
    }
},

In that way, we can align the list of projects related to the group and the list of projects to build

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	Sep 16, 2024 0:13am

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit ffb0d79. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 4 targets

• nx affected --targets=lint,test,build,e2e,e2e-ci --base=e768de6296f32d8c4c85eb7a70af0aed718bac35 --head=ffb0d794bbf9235e3081198aaf2a40ea6bed3e56 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=e768de6296f32d8c4c85eb7a70af0aed718bac35 --head=ffb0d794bbf9235e3081198aaf2a40ea6bed3e56
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

[JamesHenry]

Given some feedback on X

[JamesHenry]

Still pending the discussed updates

[JamesHenry]

Updated the PR title to match what will be coming to the PR

[JamesHenry]

Suggested change

	The `groupPreVersionCommand` will run in addition of the global `preVersionCommand`.
	The `groupPreVersionCommand` will run in addition to the global `preVersionCommand`.

[JamesHenry]

You left this underneath the comment saying it is not something which is supported at the group level, which doesn't make sense, but more broadly why are you creating a relationship between preVersionCommand and groupPreVersionCommand?

They are separate things, right now the way you have things it looks like if you set a preVersionCommand it will be run twice, once as a preVersionCommand and once as a groupPreVersionCommand?

Please remove this relationship

[JamesHenry]

This confirms what I said in my previous comment - this should not be set in this example, we do not want the command to be duplicated from global pre to group pre

[JamesHenry]

Thank you @jogelin!

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.