[PR #584] feat: Add specification for SemVer Ranges #824

New Issue

GiteaMirror · 2026-02-17T12:19:46-06:00

GiteaMirror commented

2026-02-17 12:19:46 -06:00

📋 Pull Request Information

Original PR: https://github.com/semver/semver/pull/584
Author: @isaacs
Created: 6/22/2020
Status: 🔄 Open

Base: master ← Head: isaacs/ranges

📝 Commits (1)

efcff2c feat: Add specification for SemVer Ranges

📊 Changes

1 file changed (+384 additions, -0 deletions)

View changed files

➕ ranges.md (+384 -0)

📄 Description

This is just a first draft, and I'm sure there's still a lot of explanatory prose that could be really helpful. Some open questions:

@steveklabnik Does this reflect what the semver crate is doing with range parsing?
Other implementors: how far is this spec from what you're doing with semver ranges? Would it be onerous or disruptive to implement in this way? Does anything conflict with your system's behavior today, or are there other features you've implemented that should go in this spec, so we can drive to consistency? (I seem to recall that ~ in particular is subtly different between rubygems/bundler and npm?)
Does this belong in semver.org, or should it be its own standalone thing, like semver-ranges.org or something? (I'd definitely like it to be owned by this group, whether it's on this specific domain name or another one.)
What questions does it raise for you that you'd like answered? What questions do you expect from others in your communities?

(Note: originally posted incorrectly at https://github.com/semver/semver.org/pull/280, moved over here where it's more appropriate.)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/semver/semver/pull/584 **Author:** [@isaacs](https://github.com/isaacs) **Created:** 6/22/2020 **Status:** 🔄 Open **Base:** `master` ← **Head:** `isaacs/ranges` --- ### 📝 Commits (1) - [`efcff2c`](https://github.com/semver/semver/commit/efcff2c838c9945f79bfd21c1df0073271bcc29c) feat: Add specification for SemVer Ranges ### 📊 Changes **1 file changed** (+384 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `ranges.md` (+384 -0) </details> ### 📄 Description This is just a first draft, and I'm sure there's still a lot of explanatory prose that could be really helpful. Some open questions: - @steveklabnik Does this reflect what the semver crate is doing with range parsing? - Other implementors: how far is this spec from what you're doing with semver ranges? Would it be onerous or disruptive to implement in this way? Does anything conflict with your system's behavior today, or are there other features you've implemented that should go in this spec, so we can drive to consistency? (I seem to recall that `~` in particular is subtly different between rubygems/bundler and npm?) - Does this belong in `semver.org`, or should it be its own standalone thing, like `semver-ranges.org` or something? (I'd definitely like it to be owned by this group, whether it's on this specific domain name or another one.) - What questions does it raise for you that you'd like answered? What questions do you expect from others in your communities? (Note: originally posted incorrectly at https://github.com/semver/semver.org/pull/280, moved over here where it's more appropriate.) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-02-17 12:19:46 -06:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/semver#824