chore: release 0.1.0 🚀

github-actions[bot] commented 3 months ago

:robot: 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[bot] commented 3 months ago

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[bot] commented 3 months ago

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[bot] commented 3 months ago

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[bot] commented 3 months ago

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[bot] commented 3 months ago

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 commented 3 months ago

Looks like Release-As: 0.1.0 in https://github.com/eslint/json/commit/d8afca4fe72ae025c0acec523c0d6d9d9aaa5a49 didn't work.

nzakas commented 3 months ago

Looks like a known bug: https://github.com/googleapis/release-please-action/issues/952

I think this will work: https://github.com/eslint/json/pull/5

eslint-github-bot[bot] commented 3 months ago

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[bot] commented 3 months ago

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 commented 3 months ago

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

mdjermanovic commented 3 months ago

Maybe https://github.com/eslint/json/pull/6 could help.

mdjermanovic commented 3 months ago

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

eslint-github-bot[bot] commented 3 months ago

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[bot] commented 3 months ago

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 commented 3 months ago

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

nzakas commented 3 months ago

Maybe this will work: https://github.com/eslint/json/pull/7

mdjermanovic commented 3 months ago

Maybe this will work: #7

It fixed the problem 🎉

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

nzakas commented 2 months ago

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[bot] commented 2 months ago

:robot: Created releases:

json-v0.1.0 :sunflower:

eslint / json