chore: set up release-please

[btmills]

Referencing the checklist from #563, I was still able to complete the first two independently, but one of the TSC members will need to complete the third item:

• Update npm package settings to allow publishing with 2FA or automation or granular access tokens.

In setting this up previously on other repositories, some packages already had this setting enabled, so don't be surprised if that's the case.

Fixes #563

To ease review, this differs from https://github.com/eslint/create-config/blob/9fc2de4eb76dd04218b5a4c72a6006563c74f589/.github/workflows/release-please.yml only by the package name:

diff --git ../create-config/.github/workflows/release-please.yml ./.github/workflows/release-please.yml
index 49defac..371943e 100644
--- ../create-config/.github/workflows/release-please.yml
+++ ./.github/workflows/release-please.yml
@@ -14,7 +14,7 @@ jobs:
         id: release
         with:
           release-type: node
-          package-name: '@eslint/create-config'
+          package-name: 'espree'
           pull-request-title-pattern: 'chore: release${component} ${version}'
       - uses: actions/checkout@v3
         if: ${{ steps.release.outputs.release_created }}
@@ -27,14 +27,14 @@ jobs:
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
         if: ${{ steps.release.outputs.release_created }}
-      - run: 'npx @humanwhocodes/tweet "@eslint/create-config ${{ steps.release.outputs.tag_name }} has been released: ${{ steps.release.outputs.html_url }}"'
+      - run: 'npx @humanwhocodes/tweet "espree ${{ steps.release.outputs.tag_name }} has been released: ${{ steps.release.outputs.html_url }}"'
         if: ${{ steps.release.outputs.release_created }}
         env:
           TWITTER_CONSUMER_KEY: ${{ secrets.TWITTER_CONSUMER_KEY }}
           TWITTER_CONSUMER_SECRET: ${{ secrets.TWITTER_CONSUMER_SECRET }}
           TWITTER_ACCESS_TOKEN_KEY: ${{ secrets.TWITTER_ACCESS_TOKEN_KEY }}
           TWITTER_ACCESS_TOKEN_SECRET: ${{ secrets.TWITTER_ACCESS_TOKEN_SECRET }}
-      - run: 'npx @humanwhocodes/toot "@eslint/create-config ${{ steps.release.outputs.tag_name }} has been released: ${{ steps.release.outputs.html_url }}"'
+      - run: 'npx @humanwhocodes/toot "espree ${{ steps.release.outputs.tag_name }} has been released: ${{ steps.release.outputs.html_url }}"'
         if: ${{ steps.release.outputs.release_created }}
         env:
           MASTODON_ACCESS_TOKEN: ${{ secrets.MASTODON_ACCESS_TOKEN }}

[nzakas]

LGTM. I've updated the espree package's npm settings to allow for CI tokens to publish.

Just waiting for @mdjermanovic as he is determining when to roll out release-please to more packages.

[snitin315]

LGTM

[linux-foundation-easycla]

• ✅ login: btmills / name: Brandon Mills (509313f, 6c8378f)
• ✅ login: mdjermanovic / name: Milos Djermanovic (6c8378f)
• ❌ - login: @web-flow / name: GitHub Web Flow . The commit (6c8378f) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[mdjermanovic]

LGTM, thanks!