[GH-ISSUE #167] Regular Expression to match versions #1843

Closed
opened 2026-04-20 09:31:01 -05:00 by GiteaMirror · 8 comments
Owner

Originally created by @joshuadgoldstein on GitHub (Nov 13, 2013).
Original GitHub issue: https://github.com/semver/semver/issues/167

It might be nice to include a regular expression which matches your versioning scheme as a sort of "example implementation".

Originally created by @joshuadgoldstein on GitHub (Nov 13, 2013). Original GitHub issue: https://github.com/semver/semver/issues/167 It might be nice to include a regular expression which matches your versioning scheme as a sort of "example implementation".
Author
Owner

@Oxymoron290 commented on GitHub (Nov 16, 2013):

https://github.com/mojombo/semver/issues/149

<!-- gh-comment-id:28638122 --> @Oxymoron290 commented on GitHub (Nov 16, 2013): https://github.com/mojombo/semver/issues/149
Author
Owner

@timfriske commented on GitHub (May 20, 2014):

#199

<!-- gh-comment-id:43609622 --> @timfriske commented on GitHub (May 20, 2014): #199
Author
Owner

@FichteFoll commented on GitHub (May 20, 2014):

@timfriske, you should have linked the issues in opposite direction since this one here is way older.

<!-- gh-comment-id:43653980 --> @FichteFoll commented on GitHub (May 20, 2014): @timfriske, you should have linked the issues in opposite direction since this one here is way older.
Author
Owner

@jeffhandley commented on GitHub (Jul 9, 2014):

Do you think #205 relates to this, where we're discussing showing how version ranges/operators can be expressed?

<!-- gh-comment-id:48500185 --> @jeffhandley commented on GitHub (Jul 9, 2014): Do you think #205 relates to this, where we're discussing showing how version ranges/operators can be expressed?
Author
Owner

@FichteFoll commented on GitHub (Jul 9, 2014):

I do not think these are related at all.

<!-- gh-comment-id:48504731 --> @FichteFoll commented on GitHub (Jul 9, 2014): I do not think these are related at all.
Author
Owner

@jeffhandley commented on GitHub (Jul 9, 2014):

Oh, oh, oh... Now I understand what this issue means! I thought it was saying we should show how regular expressions can be used to match versions. But it actually means showing a regular expression that documents the format of SemVer versions.

<!-- gh-comment-id:48510420 --> @jeffhandley commented on GitHub (Jul 9, 2014): Oh, oh, oh... Now I understand what this issue means! I thought it was saying we should show how regular expressions can be used to match versions. But it actually means showing a regular expression that documents the format of SemVer versions.
Author
Owner

@jwdonahue commented on GitHub (Oct 8, 2018):

@joshuadgoldstein, see PR #460. This issue was addressed in other threads and and PR is pending to resolve the issue. Unless you have questions or intend to issue an additional PR, please close this issue at your earliest possible convenience. Thank you.

<!-- gh-comment-id:427709793 --> @jwdonahue commented on GitHub (Oct 8, 2018): @joshuadgoldstein, see PR #460. This issue was addressed in other threads and and PR is pending to resolve the issue. Unless you have questions or intend to issue an additional PR, please close this issue at your earliest possible convenience. Thank you.
Author
Owner

@steveklabnik commented on GitHub (Feb 11, 2019):

Yes, closing this in favor of the duplicate issue/PR. Thank you!

<!-- gh-comment-id:462472500 --> @steveklabnik commented on GitHub (Feb 11, 2019): Yes, closing this in favor of the duplicate issue/PR. Thank you!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/semver#1843