question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Changelog for 4.0.0 release is missing relevant information

See original GitHub issue

Describe the bug

We use renovate to update our dependencies in multiple projects. For a few of our projects we just received the update request for vite 4.0.0, which is great of course.

Unfortunately, the changelog mixes up some information. The changes for release 4.0.0 should contain at least one breaking change (hence the MAJOR version jump), but instead it just contains this:

4.0.0 (2022-12-09)
chore: add \0 to virtual files id (#11261) ([02cdfa9](https://github.com/vitejs/vite/commit/02cdfa9)), closes https://github.com/vitejs/vite/issues/11261
chore(deps): esbuild 0.16.3 (#11271) ([495c0be](https://github.com/vitejs/vite/commit/495c0be)), closes https://github.com/vitejs/vite/issues/11271

which is suprising. It took me a few minutes to figure out, what is probably happening: The breaking changes were actually included in the 4.0.0-beta.0, and they are correctly noted there in the changelog. But for people following semver, it is unlikely that they are interested in the changes since the last beta, they would rather like to now the latest changes compared to the last stable release.

While I am good to go for this release (I figured out what is going on), I am opening this issue to improve on the situation for the future, or possibly, even fixing the changelog for 4.0.0 in retrospective.

Reproduction

https://github.com/vitejs/vite/blob/v4.0.0/packages/vite/CHANGELOG.md#400-2022-12-09

Steps to reproduce

see above

System Info

non relevant

Used Package Manager

npm

Logs

No response

Validations

Issue Analytics

  • State:closed
  • Created 9 months ago
  • Comments:7 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
ArnaudBarrecommented, Dec 14, 2022
0reactions
patak-devcommented, Dec 21, 2022

Done, but all releases point to the top of the changelog so this only changing one won’t have much effect. We should migrate to a new release scheme soon. See https://github.com/vitejs/vite/releases

Read more comments on GitHub >

github_iconTop Results From Across the Web

java - Maven - missing artifact - Stack Overflow
The container 'Maven Dependencies' references non existing library '/home/user/.m2/repository/org/springframework/spring-context/3.2.2.RELEASE/ ...
Read more >
Update 4.0.3 for Microsoft .NET Framework 4 – Runtime Update
This update includes a set of new features and fixes some bugs, based on top customer requests and the .NET Framework scenarios. Notes....
Read more >
History of Changes - Apache POI
Previous releases​​ The change log for POI 3. x and older releases can be found in the history section.
Read more >
Changelog - Cypress Documentation
Fixed an issue where the incorrect Cypress version could be shown in the ... in 10.3.0 where network logs could be missing certain...
Read more >
Changelog | Analytics | 4.0.1 - Unity - Manual
Change assertions to error logs for missing required parameters. [4.0.0] - 2022-05-12. The UGS Analytics is no longer pre-release!
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found