> :loudspeaker: Update Lately we’ve made some m...
# general
f
📢 Update
Lately we’ve made some major changes to SST with the Console and the move to CDK v2. A couple of bugs have popped up as a result of that. Most of them should be fixed by now. Consider updating to v0.60.8. If this error seems familiar to you:
Copy code
X  dev-stackA failed: Export dev-stackA:ExportsOutputXXXXXXXXXX cannot be deleted as it is in use by dev-stackB
SST can now detect this prior to deploying, and prevent it by temporarily adding the exports that are still in-use. This means you can now remove a cross stack reference directly. Read more about how it works.
k
This is AWESOME I had many issues with this 😂
d
omg, game changer
@Drew 😄
d
OMG! This is it!! Everything is going to be alright
g
Great news, was a real pain, will this also work when StackA needs to be recreated ?
f
@Gabriel Bleu do you mean removing StackA while StackB still imports an export from StackA?
g
Yes, like when renaming StackA
f
I see. In that case, It is recommended that you create a new stack with the new name, and then remove the old stack.
But yeah, to answer ur question, this change doesn’t really help w/ that.
s
What!?!?! ♥️♥️♥️