Enhance nx release with --exclude option to filter by tag (like nx affected / nx show)

[mklueh]

I was using semver before nx release, running it with nx affected.

This allowed me to enhance my projects with tags, depending on if they are live or in development, influencing if they should be release to production or just the staging environment, or none at all.

But it's hard to achieve that with nx release.

I tried to build a hackaround by using nx show --affected --exclude to first determine the projects that match the tag for the specific branch

#!/usr/bin/env bash

CURRENT_BRANCH=$(.github/scripts/current-branch.sh)

args=()
args+=("yarn nx show projects --affected --json true")

if [[ $CURRENT_BRANCH == 'master' ]]; then
  args+=("--exclude='*,!tag:live'")
else
  args+=("--exclude='*,!tag:staging'")
fi

PROJECTS=$(eval "${args[*]}") 2>/dev/null
if [[ $PROJECTS == '' ]]; then
  echo ''
else
  echo "${PROJECTS//[\"\[\]]/}"
fi

and called this

AFFECTED_TAGGED_PROJECTS=$(.github/scripts/nx-affected-projects-with-tag.sh)

args=()
args+=("yarn nx release version")
args+=("--projects=$AFFECTED_TAGGED_PROJECTS")
args+=("--dry-run")
CMD="${args[*]} $@"
eval "$CMD"

However, it seems the --json flag produces internal errors, corrupting the output and making it unusable

�33mConvert compiler options from json failed, File '.nuxt/tsconfig.json' not found.�39m

Leading to a failure of the script

yarn nx release version prerelease --preid=MY_VERSION-899-alpha --projects=�33mConvert compiler options from json failed, Cannot read file '/home/runner/work/my-project/apps/my-app/.nuxt/tsconfig.json'.�39m
�33mConvert compiler options from json failed, File '.nuxt/tsconfig.json' not found.�39m
 NX   Command failed: git diff --name-only --no-renames --relative master b8a7c983b5c21fc18da8e2b571f2173b684529e9
fatal: ambiguous argument 'master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> <revision>... -- <file>...'
Pass --verbose to see the stacktrace. --dry-run 
Convert compiler options from json failed, Cannot read file '/home/runner/work/my-project/apps/my-app/.nuxt/tsconfig.json'.
Convert compiler options from json failed, File '.nuxt/tsconfig.json' not found.
 NX   Your --projects filter "�33mConvert" did not match any projects in the workspace
./.github/scripts/nx-affected-semantic-versions.sh: line 28: $'\E33mConvert': command not found
./.github/scripts/nx-affected-semantic-versions.sh: line [30](https://github.com/my-project/actions/runs/9075232614/job/149254580276#step:16:31): NX: command not found
./.github/scripts/nx-affected-semantic-versions.sh: line 32: fatal:: command not found
./.github/scripts/nx-affected-semantic-versions.sh: line 33: Use: command not found
./.github/scripts/nx-affected-semantic-versions.sh: line 34: git <command> <revision>... -- <file>...: command not found
./.github/scripts/nx-affected-semantic-versions.sh: line 36: Pass: command not found
Error: Process completed with exit code 127.

So I'd appreciate adding this flag to nx release to have better control over projects in a standardized way, like the other commands´

I'm very well aware, that you can control what is getting released, by using the release config in nx.json, but as the build is also controlled by these tags(by using nx affected --exclude) one would have to maintain two separate configurations.