The file CHANGELOG.md indicates that it should include any significant changes to the plugin. It appears this gets included in the plugin package and shows up inside VS Code, too, under the "changelog" tab when viewing the plugin.
The last entry, right now, is 1.0.0. There have been three releases since then (1.1.0, 1.1.1, 1.1.2). Looking at the change list between 1.0.0 and 1.1.2 it appears at least one item of note is in there ("Allow the use of remote ruleset files that are hosted on http"). It feels like that should have been listed in the changelog.
It wouldn't be such a big deal except in the releases there is also no changelog or notes to indicate what's new and I don't even see earlier versions of the plugin listed as releases. Thus, there's no real way to see what's actually changing.
It'd be nice to see the CHANGELOG.md maintained, or, alternatively, have GitHub releases for each release that include the high points.
Describe the bug
The file
CHANGELOG.mdindicates that it should include any significant changes to the plugin. It appears this gets included in the plugin package and shows up inside VS Code, too, under the "changelog" tab when viewing the plugin.The last entry, right now, is 1.0.0. There have been three releases since then (1.1.0, 1.1.1, 1.1.2). Looking at the change list between 1.0.0 and 1.1.2 it appears at least one item of note is in there ("Allow the use of remote ruleset files that are hosted on http"). It feels like that should have been listed in the changelog.
It wouldn't be such a big deal except in the releases there is also no changelog or notes to indicate what's new and I don't even see earlier versions of the plugin listed as releases. Thus, there's no real way to see what's actually changing.
It'd be nice to see the
CHANGELOG.mdmaintained, or, alternatively, have GitHub releases for each release that include the high points.