Hello, I have witnessed some type of regression wi...
# general
n
Hello, I have witnessed some type of regression with
v3.249.0
and
v3.250.0
in pulumi cli, I had to revert to
v3.248.0
to make my existing stacks work correctly - my stacks are python based, I can look into expanding this 'report' but I'm currently after a few hours of debugging where I reverted my stack's branch repeatedly because I thought it was one of my local commits that broke things.. so my top priority is catching up.. Basically, the cli was stuck in previewing \ gathering resource states \ resolving resources, once I reverted to
v3.248.0
2 of my stacks were working again locally. note that pulumi deployments did manage to preview what local pulumi cli couldn't I guess since cloud deployments are slower in adopting the new cli versions
f
hm I haven't seen any other reported issues with
3.250.0
- is this still happening today? would you run a
pulumi about
and paste it here?
n
when ran with
3.248.0
the only difference is the version, nothing else
f
Yeah I would expect 248 to be ok, 249 to stall, 250 to be ok
is it all your stacks with 250?