Refactor - use renderVersionBadge - part 4 [githubrelease githubtag] (#10656)
* 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. * refactor: GithubRelease to use renderVersionBadge * refactor: GithubTag use renderVersionBadge * refactor: change forcePrerelease to isPrerelease
This commit is contained in:
@@ -43,17 +43,6 @@ describe('GithubTag', function () {
|
||||
}).expect('1.2.0-beta')
|
||||
})
|
||||
|
||||
test(GithubTag.render, () => {
|
||||
given({ usingSemver: false, version: '1.2.3' }).expect({
|
||||
message: 'v1.2.3',
|
||||
color: 'blue',
|
||||
})
|
||||
given({ usingSemver: true, version: '2.0.0' }).expect({
|
||||
message: 'v2.0.0',
|
||||
color: 'blue',
|
||||
})
|
||||
})
|
||||
|
||||
test(GithubTag.getLimit, () => {
|
||||
given({ sort: 'date', filter: undefined }).expect(1)
|
||||
given({ sort: 'date', filter: '' }).expect(1)
|
||||
|
||||
Reference in New Issue
Block a user