chore: release 6.0.0 🚀

github-actions[bot] commented 3 months ago

:robot: I have created a release beep boop

6.0.0 (2024-07-16)

⚠ BREAKING CHANGES

map known code block languages to respective file extensions (#246)
drop eslint < 8 & Node.js < 18 (#238)
Switch to flat config (#232)
drop node v8 and v10 (#203)

Features

add meta property (#233) (eedda96)
add name to flat configs (#256) (001d51e)
drop eslint < 8 & Node.js < 18 (#238) (f14f6a5)
drop node v8 and v10 (#203) (071fa66)
map known code block languages to respective file extensions (#246) (096cff4)
Switch to flat config (#232) (7a27eef)

Bug Fixes

message.line could be undefined (#191) (3a40160)
overrides general docs and Atom linter-eslint tips (fixes #109) (#111) (2a8482e)
Add unicode-bom to unsatisfiable rules (refs #75) (#84) (e34acc6)
Allowing eslint-plugin-prettier to work (fixes #101) (#107) (a2f4492)
Apply base indent to multiple line breaks (fixes #127) (#128) (5640ea6)
check upper bounds of message line numbers for code blocks (#247) (00adccb)
Don't require message end locations (fixes #112) (#154) (0311640)
Emit correct endLine numbers (#88) (dff8e9c)
Exclude eol-last from output (fixes #48) (abab043)
Ignore anything after space in code fence's language (fixes #98) (#99) (a5d0cce)
Ignore words in info string after syntax (fixes #166) (#167) (23ac2b9)
Indent multiline fixes (fixes #120) (#124) (fb0b5a3)
More reliable comment attachment (fixes #76) (#177) (79be776)
npm prepare script on Windows (refs #166) (#168) (1dd7089)
overrides pattern for virtual filenames in recommended config (#169) (f6a3fad)
Support autofix at the very start of blocks (fixes #117) (#119) (dc90961)
Support globals (fixes #79) (#81) (7c19f8b)
use blocksCache instead of single blocks instance (fixes #181) (#183) (d23d5f7)

This PR was generated with Release Please. See documentation.

mdjermanovic commented 3 months ago

Looks like it included all commits with releasable tags from the main branch. Seems like we need to specify bootstrap-sha when switching from release-please v3 to v4?

mdjermanovic commented 3 months ago

Or perhaps this is a problem with tags.

❯ looking for tagName: eslint-plugin-markdown-v5.1.0

https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md#subsequent-versions

The current setup will be creating and looking for tags in the format eslint-plugin-markdown-v<release-version> but we were using tags in the format v<release-version>, so the question is should we continue using the old format (and update tags settings in the release please config) or switch to the new format (in which case we'd probably need to specify bootstrap-sha)?

nzakas commented 3 months ago

Yeah, I figured something would break and we'd need to adjust. Just wanted to see what broke first. :) I'll take a look.

mdjermanovic commented 3 months ago

Okay, seems like https://github.com/eslint/eslint-plugin-markdown/commit/618a9f58fdf00d1176c7237b56799ee03cdde96d fixed this.

https://github.com/eslint/eslint-plugin-markdown/actions/runs/9977023767/job/27570640115

...
❯ Found release for path ., v5.1.0
❯ release for path: ., version: 5.1.0, sha: f75e14d9729a6107649d19cf540cc5385588fc4d
...
✔ No user facing commits found since f75e14d9729a6107649d19cf540cc5385588fc4d - skipping

Just looks like it doesn't close existing release PRs, so I'll close this manually.

eslint / markdown