Missing CHANGELOG / Release information for version 10.0.0 in Dependabot

[nbkhope]

P.S. I realized there's a file at https://github.com/html-to-text/node-html-to-text/blob/master/packages/html-to-text/CHANGELOG.md. However, it doesn't seem to be picked up by Dependabot. Is there some configuration that has to be done to make Dependabot detect that specific folder?

---

There was a major version change from version 9 to version 10, but there doesn't seem to be any information anywhere about what the possible breaking changes are.

Having no CHANGELOG.md or entry in Releases makes it hard for tools such as Dependabot to determine the changes from one major version to another:

[KillyMXI]

https://github.com/html-to-text/node-html-to-text/blob/master/packages/html-to-text/CHANGELOG.md

[nbkhope]

@KillyMXI thanks, I got that. I edited my description:

P.S. I realized there's a file at https://github.com/html-to-text/node-html-to-text/blob/master/packages/html-to-text/CHANGELOG.md. However, it doesn't seem to be picked up by Dependabot. Is there some configuration that has to be done to make Dependabot detect that specific folder?

I will move on from this, but was curious how to make Dependabot work properly with a CHANGELOG.md in another folder.

[KillyMXI]

I'm not sure to what extent Dependabot might support the changelog file. Maybe it doesn't understand the combination of changelog file and monorepo. (I'd be happy if someone can provide more details.)

In general, tools might prefer GitHub release descriptions, but I don't have a workflow for that, because that's not how the package is consumed. (I might add it eventually, but so far it was low priority.)

Thanks for reaching out either way.

[KillyMXI]

Related:

I see something stupid on the NPM side:

• Add a "changelog" url to the package.json documentation npm/npm#18463 - request to add "changelog" to package.json spec, so tools can find it;
• Changelog npm/rfcs#7 - original request transformed into an RFC;
• feat: npm changelog npm/rfcs#8 - transformed into an RFC for npm changelog as a CLI command;
• https://github.com/npm/rfcs/blob/main/withdrawn/0002-changelog.md - the CLI command proposal was withdrawn.

Seems like they lost the plot in the process.

I would rather have the ability to show the Changelog URL at npmjs.com in addition to (pointlessly duplicated) Repository and Homepage links, and allow vscode plugins to show the link in a popup.

[KillyMXI]

Existing practice in vscode extensions:

• https://github.com/pgsandstrom/package-json-upgrade/blob/master/src/changelog.ts
  • extension last updated - recently
  • hardcoded /blob/master/CHANGELOG.md (might break even in case of main branch)
• https://github.com/bashbers/changelog-on-hover/blob/master/src/extension.ts
  • extension last updated - in 2024
  • determines the repo path then looks for predefined file names relative to the root

Not sufficient, not adequate.

[KillyMXI]

From my side, as a workaround, I can create CHANGELOG.md in the root folder with links to per-package changelogs.

In general, this might require a community effort:

• define a community extension to package.json spec
  • the proposal for the changelog field was good but was lost in the RFC process
  • it becomes more important with NPM workspaces
• formulate the request to relevant IDE extensions and other community tools to support certain ways of finding the changelog location in the modern context, including NPM workspaces.