[GH-ISSUE #104] SemVer badge/shield. #2785

New Issue

GiteaMirror · 2026-04-25T16:41:36-05:00

GiteaMirror commented

2026-04-25 16:41:36 -05:00

Originally created by @jmalloc on GitHub (Jun 6, 2013).
Original GitHub issue: https://github.com/semver/semver/issues/104

Just a quick thought I had - I think it would be beneficial to have a small, official "SemVer" icon/badge/shield to display on websites, README files, etc, that indicates a project uses semantic versioning. It's often hard to tell from tag names alone, and this would remove any doubt.

Originally created by @jmalloc on GitHub (Jun 6, 2013). Original GitHub issue: https://github.com/semver/semver/issues/104 Just a quick thought I had - I think it would be beneficial to have a small, official "SemVer" icon/badge/shield to display on websites, README files, etc, that indicates a project uses semantic versioning. It's often hard to tell from tag names alone, and this would remove any doubt.

GiteaMirror closed this issue

2026-04-25 16:41:36 -05:00

GiteaMirror commented

2026-04-25 16:41:37 -05:00

@Tieske commented on GitHub (Jun 6, 2013):

I would prefer an optional tag eg.a trailing sv (space sv) which would allow existing systems to automatically determine whether a version could be parsed as SemVer. This would make it a lot easier to transition from a proprietary versioning schedule to a standard semver based schedule.

For human communications though I like the idea of a batch.

@Tieske commented on GitHub (Jun 6, 2013): I would prefer an optional tag eg.a trailing `sv` (space sv) which would allow existing systems to automatically determine whether a version could be parsed as SemVer. This would make it a lot easier to transition from a proprietary versioning schedule to a standard semver based schedule. For human communications though I like the idea of a batch.

GiteaMirror commented

2026-04-25 16:41:37 -05:00

@BitDrifter commented on GitHub (Jun 24, 2013):

+1 for both Ideas.

@BitDrifter commented on GitHub (Jun 24, 2013): +1 for both Ideas.

GiteaMirror commented

2026-04-25 16:41:38 -05:00

@jmalloc commented on GitHub (Jun 24, 2013):

A friend of mine linked me the image below, which is a modified example from the "shields as a service" issue on olivierlacan/shields. I like the idea of it stylistically matching badges used by other projects (Travis CI, etc), at the very least in terms of dimensions.

original url: http://calm-shore-6115.herokuapp.com/?label=semver&value=2.0.0-RC1&color=green

@jmalloc commented on GitHub (Jun 24, 2013): A friend of mine linked me the image below, which is a modified example from the ["shields as a service"](https://github.com/olivierlacan/shields/issues/15) issue on [olivierlacan/shields](https://github.com/olivierlacan/shields). I like the idea of it stylistically matching badges used by other projects (Travis CI, etc), at the very least in terms of dimensions. ![](http://calm-shore-6115.herokuapp.com/?label=semver&value=2.0.0-RC1&color=green) original url: http://calm-shore-6115.herokuapp.com/?label=semver&value=2.0.0-RC1&color=green

GiteaMirror commented

2026-04-25 16:41:39 -05:00

@chadwhitacre commented on GitHub (Aug 10, 2013):

I would prefer an optional tag eg.a trailing sv (space sv) which would allow existing systems to automatically determine whether a version could be parsed as SemVer.

@Tieske There are multiple versions of SemVer though. How would you communicate that?

@chadwhitacre commented on GitHub (Aug 10, 2013): > I would prefer an optional tag eg.a trailing sv (space sv) which would allow existing systems to automatically determine whether a version could be parsed as SemVer. @Tieske There are multiple versions of SemVer though. How would you communicate that?

GiteaMirror commented

2026-04-25 16:41:39 -05:00

@Tieske commented on GitHub (Aug 11, 2013):

using the sv postfix, it could simply be appended; 1.2.3 sv2.0.0 package version 1.2.3 based on SemVer 2.0.0.

@Tieske commented on GitHub (Aug 11, 2013): using the `sv` postfix, it could simply be appended; `1.2.3 sv2.0.0` package version `1.2.3` based on SemVer `2.0.0`.

GiteaMirror commented

2026-04-25 16:41:40 -05:00

@chadwhitacre commented on GitHub (Sep 3, 2013):

@Tieske Noted on https://github.com/gittip/shields.io/issues/36.

@chadwhitacre commented on GitHub (Sep 3, 2013): @Tieske Noted on https://github.com/gittip/shields.io/issues/36.

GiteaMirror commented

2026-04-25 16:41:40 -05:00

@AaronLasseigne commented on GitHub (Nov 22, 2013):

👍 A badge would be great.

@AaronLasseigne commented on GitHub (Nov 22, 2013): :+1: A badge would be great.

GiteaMirror commented

2026-04-25 16:41:41 -05:00

@rlidwka commented on GitHub (Dec 15, 2013):

Will 1.2.3+sv be good enough for this?

Strong "-1" for badges, all of them, because most of them are essentially a web bugs tracking users activity on the internet.

@rlidwka commented on GitHub (Dec 15, 2013): Will `1.2.3+sv` be good enough for this? Strong "-1" for badges, all of them, because most of them are essentially a web bugs tracking users activity on the internet.

GiteaMirror commented

2026-04-25 16:41:42 -05:00

@haacked commented on GitHub (Jul 1, 2014):

I'm not sold on the idea, but if we're going to discuss a badge, it seems a PR is a good place. Closing due to #126

@haacked commented on GitHub (Jul 1, 2014): I'm not sold on the idea, but if we're going to discuss a badge, it seems a PR is a good place. Closing due to #126

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/semver#2785