chore: release 0.1.0 🚀

[github-actions]

🤖 I have created a release beep boop

0.1.0 (2024-07-06)

Features

• Add JSON plugin (#1) (1976f2c)
• Add JSONLanguage#visitorKeys (#4) (d8afca4)

Bug Fixes

• release-please (again) (#7) (5ef7c6c)
• Set initial release version in release-please-config.json (#5) (64f4db5)

---

This PR was generated with Release Please. See documentation.

[eslint-github-bot]

Hi @github-actions[bot]!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[mdjermanovic]

Looks like it didn't respect "bump-minor-pre-major": true option.

[nzakas]

Yeah, that's weird. I'll make another PR to reset the version.

[mdjermanovic]

This could be because of the release-please action we're using.

In this repo, we're using google-github-actions/release-please-action@v4. In the rewrite repo, we're using GoogleCloudPlatform/release-please-action@v4. In other repos, e.g. espree, we're using google-github-actions/release-please-action@v3.

google-github-actions/release-please-action is deprecated in favor of googleapis/release-please-action@v4.

There seem to be a lot of different versions.

[nzakas]

Huh, had no idea all that was going on. I guess we should standardize on the new version.

[eslint-github-bot]

Hi @github-actions[bot]!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[eslint-github-bot]

Hi @github-actions[bot]!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[eslint-github-bot]

Hi @github-actions[bot]!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[eslint-github-bot]

Hi @github-actions[bot]!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[mdjermanovic]

Looks like Release-As: 0.1.0 in d8afca4 didn't work.

[nzakas]

Looks like a known bug: googleapis/release-please-action#952

I think this will work: #5

[eslint-github-bot]

Hi @github-actions[bot]!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[eslint-github-bot]

Hi @github-actions[bot]!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[mdjermanovic]

Nope again, it seems determined to release v1.0.0.

[mdjermanovic]

Maybe #6 could help.

[mdjermanovic]

Note that it didn't update jsr.json, so it's questionable whether our release-please-config.json is correct.

[eslint-github-bot]

Hi @github-actions[bot]!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[eslint-github-bot]

Hi @github-actions[bot]!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[nzakas]

This is bizarre. I have a similar setup in a person repo without any problems. Going to investigate now.

[nzakas]

Maybe this will work: #7

[mdjermanovic]

Maybe this will work: #7

It fixed the problem 🎉

Just it looks like the pattern should be updated a bit.

[mdjermanovic]

This looks good now. Just not sure if we should wait for eslint v9.7.0 (with eslint/eslint@6320732) before releasing this.

[nzakas]

Because we aren't using any selectors, I think it's okay to release. I'm not going to make a formal announcement until next week anyway, but I'd like to ensure the release process works and get this integrated into eslint/eslint.

[github-actions]

🤖 Created releases:

• json-v0.1.0
  🌻