Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(main): release 4.1.2 #146

Conversation

github-actions[bot]
Copy link
Contributor

🤖 I have created a release beep boop

4.1.2 (2023-02-28)

Miscellaneous Chores

  • Run a test release using release-please (#145) (6d3e535)

This PR was generated with Release Please. See documentation.

@eslint-github-bot
Copy link

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

The first commit message isn't properly formatted. We ask that you update the message 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 running git commit --amend, editing your commit message, and then running git push -f to update this pull request.

Read more about contributing to ESLint here

@btmills btmills closed this Feb 28, 2023
@btmills btmills deleted the release-please--branches--main--components--generator-eslint branch February 28, 2023 07:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant