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

docs(reference-spec.md): fix SemVer 2 link #278

Merged
merged 1 commit into from
Jan 25, 2022
Merged

docs(reference-spec.md): fix SemVer 2 link #278

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/reference-spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ This section of the Bindle specification defines how naming and referencing work

A bindle has a name. For example, if we were to write a `hello world` bindle, it may have the name `hello_world`.

When a bindle is concretized into an invoice, it MUST have a name and a version. Version MUST be a valid [https://semver.org](SemVer 2 version).
When a bindle is concretized into an invoice, it MUST have a name and a version. Version MUST be a valid [SemVer 2 version](https://semver.org).

A bindle name can be one or more characters from the set of unicode alphabetic and numeric characters, as well as the characters `_` and `/`.

Expand Down