Closed andreialecu closed 9 months ago
Not exactly sure what to do about the integ:snapshots
, I updated them and the test passes locally. I wonder if it's because of the gh runner differences vs my system.
Slightly offtopic: I also noticed something you may want to look into for the test infrastructure.
The GitHub workflow for testing updates the snapshots, too, while running the tests. This doesn't seem like something you'd want. Screenshot from recent workflow:
Slightly offtopic: I also noticed something you may want to look into for the test infrastructure.
The GitHub workflow for testing updates the snapshots, too, while running the tests. This doesn't seem like something you'd want. Screenshot from recent workflow:
This is the correct behavior, the "mutations" are then committed back, see
https://github.com/projen/projen/blob/main/docs/publishing/build.md#self-mutation
Not exactly sure what to do about the
integ:snapshots
, I updated them and the test passes locally. I wonder if it's because of the gh runner differences vs my system.
Looking into this, usually fixed by running everything in a codespace.
Slightly offtopic: I also noticed something you may want to look into for the test infrastructure. The GitHub workflow for testing updates the snapshots, too, while running the tests. This doesn't seem like something you'd want. Screenshot from recent workflow:
This is the correct behavior, the "mutations" are then committed back, see
Yes, but what's the point of the test if the snapshots are always blindly updated? Seems easy to overlook.
Yes, but what's the point of the test if the snapshots are always blindly updated? Seems easy to overlook.
blindly updated but then reviewed in the PR
Thanks @andreialecu
Fixes #255
BREAKING CHANGE:
cloudstructs
now requiresaws-cdk-lib
>= 2.112.0