pulumi/sdk/nodejs/tests/sxs_ts_test
Will Jones d64448ec3b
Replace Rome with Biome in the NodeJS SDK ()
As @denbezrukov notes in , Rome (https://github.com/rome/tools,
the JavaScript toolchain we have been using to format and lint code in
the NodeJS SDK) has been deprecated. Biome (https://biomejs.dev/) has
sprung up in its place as a community fork and appears to be the best
bet for migration going forward. This commit introduces Biome, ports the
bits of configuration that need changing and updates formatting
accordingly.

Closes 

Co-authored-by: Denis Bezrukov <6227442+denbezrukov@users.noreply.github.com>
2024-06-24 11:14:56 +00:00
..
.gitignore Fix side-by-side tests () 2024-03-05 13:50:45 +00:00
README.md ci: fix sxs test 2022-03-06 14:45:26 -08:00
index.ts Apply autoformat 2023-04-28 18:27:10 -04:00
package^3.json Fix side-by-side tests () 2024-03-05 13:50:45 +00:00
package^4.json Fix side-by-side tests () 2024-03-05 13:50:45 +00:00
package~3.8.3.json Add missing `typescript` dependency to sxs_ts_test () 2024-04-16 00:05:05 +00:00
tsconfig.json Replace Rome with Biome in the NodeJS SDK () 2024-06-24 11:14:56 +00:00

README.md

This test validates that changes we're making in @pulumi/pulumi will be side-by-side compatible with the 'latest' version of @pulumi/pulumi that has already shipped.

If a change is made that is not compatible, then the process should be:

  1. Ensure that the change is absolutely what we want to make.
  2. Disable running this test.
  3. Commit the change and update the minor version of @pulumi/pulumi (i.e. from 0.17.x to 0.18.0).
  4. Flow this change downstream, rev'ing the minor version of all downstream packages.
  5. Re-enable the test. Because there is now a new 'latest' @pulumi/pulumi, this test should pass.

Step '3' indicates that we've made a breaking change, and that if 0.18 is pulled in from any package, that it must be pulled in from all packages.

Step '4' is necessary so that people can pick a set of packages that all agree on using this new @pulumi/pulumi version. While not necessary to rev the minor version of these packages, we still do so to make it clear that there is a significant change here, and that one should not move to it as readily as they would a patch update.