Skip to content

Tag released versions #497

@WarningImHack3r

Description

@WarningImHack3r

Hi maintainers, I'm the creator of Svelte Changelog, a site that tracks all the releases by the Svelte organization.

To list releases, I leverage the GitHub API in 2 ways:

  • list GitHub releases if available
  • reconstruct releases from the list of tags, with the release body constructed from the root CHANGELOG.md file

As a result, releases not listed in the releases nor in the list of tags are not caught by the site.

This repo is the only one I can tell from the sveltejs org that has a few divergences from the other ones: the latest CHANGELOG.md file is in the special version-3 branch instead of master, but most importantly, the last two releases are not tagged at all, making them invisible from my site's perspective.

I could adjust my research algorithm to take the most recent source between the list of tags and the CHANGELOG.md file, but it's a far less reliable method and adds up quite a bit of code to specifically handle the case of this repo.

As a result, can you please make sure new releases for this repo are tagged accordingly? This would help Paolo during TWIS, but also all the other users of Svelte Changelog ^^ Thanks!!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions