Hi pulumi expert, sorry for asking this question, I noticed a change when updating from pulumi 3.181.0 to 3.182.0, when I run

pulumi up

on my existing stack, I got all resource deletion instead of update. The pulumi update plan originally looks like this

@ Previewing update.........
    pulumi:pulumi:Stack lighthouse-dev  [INFO][2025-10-27 14:58:23,201][__init__] cluster_config_dir: /home/syscl/deductive/code/config/iac_export/lighthouse
    pulumi:pulumi:Stack lighthouse-dev running [INFO][2025-10-27 14:58:23,201][__init__] cluster_config_dir: /home/syscl/deductive/code/config/iac_export/lighthouse
@ Previewing update.....
 ~  pulumi:providers:aws deductive-controller update [diff: ~version]
@ Previewing update.....
 ~  pulumi:providers:aws aws update [diff: +profile~version]
@ Previewing update....
 +  aws:s3:Bucket deductiveai-alb-access-logs-lighthouse create
 +  aws:iam:Role DeductiveAIEKSClusterRole-lighthouse create
@ Previewing update....
 +  aws:secretsmanager:Secret deductive-secrets create
 +  aws:iam:Role DeductiveAIEC2Role-lighthouse create
 +  aws:s3:BucketLifecycleConfigurationV2 deductiveai-alb-access-logs-lighthouse-lifecycle create
 +  aws:s3:BucketPolicy deductive-alb-access-logs-policy create
 +  aws:secretsmanager:SecretVersion deductiveai-secret-init-awscurrent-empty-lighthouse create
 ~  aws:route53:Record <http://ssl-cert-validation-dns-record-for-lighthouse.deductive.ai|ssl-cert-validation-dns-record-for-lighthouse.deductive.ai> update [diff: +allowOverwrite]
 ~  aws:ec2:Vpc lighthouse-vpc update [diff: ~enableDnsHostnames]
@ Previewing update....
 ++ aws:ec2:Subnet lighthouse-vpc-public-1 create replacement [diff: ~cidrBlock]

But updating to 3.182.0 and later version it became completely deletion:

Previewing update.....
 -  pulumi:providers:kubernetes eks-provider delete
 -  aws:eks:NodeGroup standard_node_group delete
 -  aws:ec2:SecurityGroup lighthouse-ELB-SecurityGroup delete
 -  aws:eks:Cluster lighthouse delete
 -  aws:ec2:Route lighthouse-vpc-private-2 delete
 -  aws:ec2:Route lighthouse-vpc-private-1 delete
 -  aws:ec2:Route lighthouse-vpc-public-2 delete
 -  aws:ec2:Route lighthouse-vpc-public-1 delete
 -  aws:ec2:RouteTableAssociation lighthouse-vpc-private-1 delete
 -  aws:ec2:RouteTableAssociation lighthouse-vpc-private-2 delete
 -  aws:ec2:NatGateway lighthouse-vpc-2 delete
 -  aws:ec2:RouteTableAssociation lighthouse-vpc-public-2 delete
 -  aws:ec2:NatGateway lighthouse-vpc-1 delete

And I also noticed a lot of warnings like this:

@ Previewing update.....
    pulumi:pulumi:Stack lighthouse-dev  [INFO][2025-10-27 14:59:49,357][__init__] cluster_config_dir: /home/syscl/deductive/code/config/iac_export/lighthouse
    pulumi:pulumi:Stack lighthouse-dev  /home/syscl/.local/share/uv/python/cpython-3.13.3-linux-x86_64-gnu/lib/python3.13/asyncio/base_events.py:744: RuntimeWarning: coroutine 'RPCManager.do_rpc.<locals>.rpc_wrapper' was never awaited
    pulumi:pulumi:Stack lighthouse-dev    self._ready.clear()
    pulumi:pulumi:Stack lighthouse-dev  RuntimeWarning: Enable tracemalloc to get the object allocation traceback
    pulumi:pulumi:Stack lighthouse-dev  /home/syscl/.local/share/uv/python/cpython-3.13.3-linux-x86_64-gnu/lib/python3.13/asyncio/base_events.py:744: RuntimeWarning: coroutine 'Output.__init__.<locals>.is_value_known' was never awaited
    pulumi:pulumi:Stack lighthouse-dev    self._ready.clear()
    pulumi:pulumi:Stack lighthouse-dev  RuntimeWarning: Enable tracemalloc to get the object allocation traceback
    pulumi:pulumi:Stack lighthouse-dev  <sys>:0: RuntimeWarning: coroutine 'Output.__init__.<locals>.is_value_known' was never awaited
    pulumi:pulumi:Stack lighthouse-dev  RuntimeWarning: Enable tracemalloc to get the object allocation traceback

I am using python 3.13.3, any reason why this happens? Thanks!