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: release 5.0.0 #248

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Apr 1, 2024

🤖 I have created a release beep boop

5.0.0 (2024-05-01)

⚠ BREAKING CHANGES

  • map known code block languages to respective file extensions (#246)

Features

  • map known code block languages to respective file extensions (#246) (096cff4)

Bug Fixes

  • check upper bounds of message line numbers for code blocks (#247) (00adccb)

Chores

  • run tests in Node.js 22, with ESLint 9 (#250) (085e6d5)
  • switch to eslint v9, eslint-config-eslint v10 (#251) (a76cdf5)

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot changed the title chore: release 4.0.2 chore: release 5.0.0 Apr 29, 2024
@github-actions github-actions bot force-pushed the release-please--branches--main--components--eslint-plugin-markdown branch 2 times, most recently from 284b4e4 to 819cc87 Compare April 29, 2024 20:25
@github-actions github-actions bot force-pushed the release-please--branches--main--components--eslint-plugin-markdown branch from 819cc87 to 60b957c Compare May 1, 2024 17:19
@mdjermanovic mdjermanovic merged commit bbdaaa8 into main May 2, 2024
3 checks passed
@mdjermanovic mdjermanovic deleted the release-please--branches--main--components--eslint-plugin-markdown branch May 2, 2024 20:59
Copy link
Contributor Author

github-actions bot commented May 2, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant