chore(main): release 5.1.0

[release-please]

🤖 I have created a release beep boop

5.1.0 (2023-09-29)

Features

• no-floating-promises (#756) (c93e733)

Bug Fixes

• deps: update dependency eslint to v8.49.0 (#784) (5e2a05c)
• deps: update dependency eslint to v8.50.0 (#802) (794abf3)
• deps: update dependency eslint-config-prettier to v8.10.0 (#785) (5391d89)
• deps: update dependency eslint-config-prettier to v9 (#777) (470977a)
• deps: update dependency prettier to v3.0.3 (#782) (5a04e76)
• run eslint from PATH (#654) (5dc2a76)

---

This PR was generated with Release Please. See documentation.

[release-please]

🤖 Release is at https://github.com/google/gts/releases/tag/v5.1.0 🌻

[naseemkullah]

thanks @danielbankhead - when will it be available on npm tho? https://www.npmjs.com/package/gts

[danielbankhead]

@naseemkullah it’s available on npm now.

[danielbankhead]

@naseemkullah, we had to roll back the non-floating-promises part of this release due to it breaking a number of repos:

• Revert "feat: no-floating-promises (#756)" #808

Feel free to pin your version of gts to this release until the next major, or follow/subscribe to this issue:

• feat!: Set no-floating-promises to error #793

[naseemkullah]

thanks for the heads up @danielbankhead - curious how did it break repos if it was just warn ?

[danielbankhead]

@naseemkullah the project property of the PR causes eslint to error when eslint attempts to lint a file not specified in tsconfig.json (which shouldn't be an error imo, but eslint doesn't expose a way to turn it off).

Here's a sample of that error:

• https://github.com/googleapis/nodejs-googleapis-common/actions/runs/6398556579/job/17368932343#step:5:67

[naseemkullah]

oh I see, thanks

0:0 error Parsing error: ESLint was configured to run on <tsconfigRootDir>/system-test/fixtures/kitchen/src/index.ts using parserOptions.project: /tsconfig.json