I don't know how much this suggestion could apply to you, but in general this is called "reduce blast radius".
Try to split these 140 resources in two (or 3), along dependency and frequency of change lines.
Then, put each group in its own Pulumi project.
To link information from one project to the other, use
https://www.pulumi.com/docs/using-pulumi/stack-outputs-and-references/
For an introduction to the concept of multiple, dependent projects, see
https://www.pulumi.com/docs/using-pulumi/organizing-projects-stacks/
This approach, reduce blast radius, is not specific to Pulumi. I do the same with Terraform.
Last point: the moment there is more than one project with dependencies among them, one cannot use anymore
pulumi up
. Instead, one has to script the invocation of the projects in the correct order.
Is it worth it? I think it is mandatory best practice for any prod that reaches a certain size...