How is @nx/docker intended to interact with nx release version when I don’t want Docker builds?

[patriklarssson]

I’m using Nx 22.0.1 in a monorepo with the @nx/docker plugin installed. My project setup roughly looks like this:

• @nx/docker is installed and configured in nx.json.
• I’m using nx release to manage versioning and tagging in GitHub Actions.

I want a step that only creates a release tag (nx release version) without building or publishing Docker images. However, even when I:

• Remove the docker block from release.groups in nx.json.
• Remove or disable the @nx/docker plugin in nx.json.

the nx release version command still triggers a Docker release.

So my questions are:

1. Is this the intended behavior for @nx/docker?
2. If so, what is the recommended way to use nx release version for tagging only, without triggering Docker builds?
3. Is there a supported way to temporarily skip Docker hooks during a release step?

I want to understand the expected workflow, so I don’t end up fighting Nx’s release system in CI.

Thanks in advance for any guidance!