No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

what about listing the affected packages with a tag like pulumi and then using that in an if on the pulumi step?

Ended up just adding a job that checks whether the expected projects are part of the output from `nx affected`  and make the job that deploys pulumi to be dependant on the check.