Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Refactor - use renderVersionBadge - part 4 [github] #10656

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Refactor - use renderVersionBadge - part 4 [github] #10656

wants to merge 4 commits into from

Commits on Nov 2, 2024

  1. feat: add forcePrerelease option to renderVersionBadge function 

    Sometimes API would indicate if a version is pre-release while the version number does not have to be semantically a prerelease like in github-release service.
We don't use a isPrerelease that can also force a non-preleases as we trust here developer semantic over API tagging.
    @jNullj
    jNullj committed Nov 2, 2024
    Configuration menu
    Copy the full SHA
    bef9e31 View commit details
    Browse the repository at this point in the history

Commits on Nov 4, 2024

  1. refactor: GithubRelease to use renderVersionBadge

    @jNullj
    jNullj committed Nov 4, 2024
    Configuration menu
    Copy the full SHA
    df87b6c View commit details
    Browse the repository at this point in the history

  2. refactor: GithubTag use renderVersionBadge

    @jNullj
    jNullj committed Nov 4, 2024
    Configuration menu
    Copy the full SHA
    5ee0413 View commit details
    Browse the repository at this point in the history

  3. Merge branch 'master' into refactor/convert-to-renderVersionBadge-3

    @jNullj
    jNullj authored Nov 4, 2024
    Configuration menu
    Copy the full SHA
    a206b7d View commit details
    Browse the repository at this point in the history