Release new version with ESLint 9 support

[michalsanger]

Hi, in #157 (comment) I can see a version 0.0.0-main-e39d0e7f7bfc174041e83f84d14760ca88a2b158 was shipped to test if the support of ESLint 9 works OK (IMHO it does).

Do you plan to make a standard release of a new version?

[captbaritone]

Good idea. Looks like we haven't done a release in several years. I think the next step is to build up a list of all the commits since the last release and write up a changelog of what's in there. Do you have time to take a stab at that?

[michalsanger]

So I checked v1.8.2...main and created a list of commits that should be mentioned in the changelog (some of them IMHO deserve a better description):

5c313c6 Merge pull request #161 from captbaritone/clean-up
493346f Address feedback
b2251d6 Clean up legacy lint rules
2274f07 Fix compatibility issues with ESLint 9 (#157)
3203497 Make compatible with typescript-eslint 8
31bfd44 Merge pull request #128 from opencreek/generated-typescript-types
f29444d Fix invalid typescipt types
0c91b68 Add test for generated-typescript-types and fixed bugs resulting from that
ead1352 Merge branch 'master' of github.com:llldar/eslint-plugin-relay into generated-typescript-types
8b9beb1 Remove RelayCompat support
3d1ebcd Require passing generated flow type for useMutation
105cf7f add "generated-typescript-types" rule

Here is a list of commits that are just version bumps or formatting, that could be omitted from the changelog:

7183502 Prettier
e39d0e7 Merge pull request #159 from PHILLIPS71/chore/update-ci-workflow-actions
6c1b82c chore: pin package manager to yarn v1.22.22
0f2e8a7 style: resolve formatting issues with prettier across codebase
c88d1e0 chore: update actions/checkout and actions/setup-node to v4
24fd162 Merge pull request #151 from alecmev/tseslint-8
e37dd9f Update Node.js in CI to 18, 20, 22
f74143f Merge pull request #146 from relayjs/captbaritone-patch-2
1317043 Add registry-url to setup-node in CI
5feda32 Merge pull request #145 from relayjs/captbaritone-patch-1
deff0d3 Increase verbosity of npm publish from CI
0fb398b Merge pull request #141 from relayjs/alloy/add-release-scripts
ef93d45 Require stable releases to include the package.json change
b0c5786 [ci] Add release automation scripts
b463da4 Merge pull request #140 from relayjs/dependabot/npm_and_yarn/word-wrap-1.2.5
adce3e2 Merge pull request #139 from relayjs/dependabot/npm_and_yarn/semver-7.5.4
3759b77 Bump semver from 7.3.5 to 7.5.4
72b8d4e Bump word-wrap from 1.2.3 to 1.2.5
85b7a9b Fithe intro page link (#129)
4d61341 Upgrade mocha (#127)
07f89ca Upgrade prettier (#126)
a15ccaa Add yarn based caching to CI (#125)
397b730 Update node versions in CI to 12,14,16 (#123)
f9e57b4 Bump version
74631be Bump glob-parent from 5.1.1 to 5.1.2
c4551ad Bump path-parse from 1.0.6 to 1.0.7
af69fa4 Bump lodash from 4.17.15 to 4.17.21
9a3d977 Merge pull request #114 from relayjs/dependabot/npm_and_yarn/y18n-4.0.1
69280c8 Bump y18n from 4.0.0 to 4.0.1

[captbaritone]

I think the next step is a PR that bumps the version to 2.0 and adds a changelog with a summary of the changes included in that first set of commits. Do you want to take a stab at that?

[michalsanger]

@captbaritone please review #163