Skip to content

Create GitHub releases whenever releasing vsce #862

@Marcono1234

Description

@Marcono1234

Hello,
the GitHub releases of this project are outdated; the latest entry is for version 2.15.0, but the latest version is currently 2.19.0.

Is this intentional? Is there some other changelog / release notes document I overlooked?

As mentioned in previous similar issues a changelog makes it easier for users to understand what changed between the versions; checking the commits can be tedious especially if commits might have no user facing effect, or if commits messages are unclear to users.

It looks like previously creation of the GitHub releases was automated (see #541 and #710), but that was dropped by #791.

Metadata

Metadata

Assignees

Labels

feature-requestRequest for new features or functionalityverification-neededVerification of issue is requestedverifiedVerification succeeded

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions