chore(main): release all-contributors-cli 7.0.0#476
Conversation
|
Are we ok with bumping to 7, given all of the major dependency updates? It seems reasonable to me. |
|
Ok looks like we will want to add a lint step on the changelog that release please creates. But how... |
|
@lwasser So, I believe there's an issue with the Release Please setup. It's not detecting any previous releases, so I believe this effectively is every change that's ever happened (that fits into feat or fix - and it may be capped at 500). For instance this change in the changelog is from 2019, but the last release was 2023, so it shouldn't be included. The problem is that the Release Please config is setup to use the component name as part of the tag name (default behavior when using manifest releases), and the existing tags aren't using that format. So, it fails to find any previous release tags.
That format is really meant for monorepos with multiple packages being published out of it. When it's disabled, the tag format is the same as what you're already using. So, you just need to add this to your release please config: Before merging that, I'd suggest closing this PR, and deleting the release-please branch, so that when the above change merges it regenerates the branch and pr from scratch. At that point it should detect your previous releases, and only include unreleased changes in the new PR. (for the lint error, we just excluded the changelog from our eslint config, since it's being generated) |
Il look 🫡 Update - So we can do something like this, or we can ignore the changelog from the linter/prettier |
|
@jdalrymple, if you want to have a go at ignoring the linting for the changelog, that would be awesome!! I think that is we fixed it by linting, we would then need to commit the change within the workflow? I am fine with that or just telling eslint to ignore it. @michaelfaith thank you - I'll create a new PR with the config change. I saw it was a large changelog but just figured it was 3 years of commits without validating what was going on. THANK YOU for catching this!! |
|
@all-contributors please add @michaelfaith for bug, review, code |
|
I've put up a pull request to add @michaelfaith! 🎉 |
|
thank you again Michael, and Justin!! I'll close this and delete the head branch. I opened #479 |


🤖 I have created a release beep boop
7.0.0 (2026-03-06)
⚠ BREAKING CHANGES
🚀 New Features
widthandvalignattributes for cleaner <td> (#344) (554667b)wrapperTemplateoption (#348) (2c07af8)promotion(#339) (8fc7c7e)businessandcontent(#156) (48fecd3)altattributes (#138) (87ce8bb)🔥 Bug Fixes
tbody(#311) (531b7e1)commitConventiondefault same asapp(#318) (94b555e)7forcontributorsPerLine(e1fd794)7forcontributorsPerLine(#139) (e1fd794)nextLinkbefore slicing (5df6b47)nextLinkbefore slicing (#309) (5df6b47)🏃 Performance Improvements
📚 Documentation
⚙️ Chores
package-lock.json(#434) (5de78d9)contributors[skip ci] (05bed92)⌨️ Code Refactoring
🧪 Testing
add-contributors-listtests (#396) (84ac3ed)🛠️ Build System
📦 CI Improvements
This PR was generated with Release Please. See documentation.