Pulumi has introduced project-scoped stacks to its DIY backends, aligning them with the Pulumi Service backend's method of managing stack names within projects. This change allows users to employ common stack names like "test" and "prod" across different projects without conflicts, eliminating the need for previous workarounds where stack names were globally unique across all projects. With the new release, users can upgrade existing DIY backends to the project-scoped format using the `pulumi state upgrade` command, but older versions of the Pulumi CLI will not recognize the new format. This update also enables streamlined referencing of stacks within the Pulumi CLI. While the Pulumi Service backend offers enhanced usability and security, the DIY backend provides users with more control over where state information is stored, supporting local filesystems and various cloud storage options. Pulumi's ongoing commitment to improving the Infrastructure as Code experience includes both the open-source SDK and CLI, along with Pulumi Cloud, which offers options ranging from free individual plans to tools for enterprise-level management.