Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
H
helm3
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
go
helm3
Commits
a3af75f9
Unverified
Commit
a3af75f9
authored
Dec 05, 2017
by
Tim H
Committed by
GitHub
Dec 05, 2017
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix example and reference version matching syntax
Address documentation issue raised in #2759
parent
16571305
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
4 deletions
+5
-4
requirements.md
docs/chart_best_practices/requirements.md
+5
-4
No files found.
docs/chart_best_practices/requirements.md
View file @
a3af75f9
...
@@ -7,10 +7,12 @@ This section of the guide covers best practices for `requirements.yaml` files.
...
@@ -7,10 +7,12 @@ This section of the guide covers best practices for `requirements.yaml` files.
Where possible, use version ranges instead of pinning to an exact version. The suggested default is to use a patch-level version match:
Where possible, use version ranges instead of pinning to an exact version. The suggested default is to use a patch-level version match:
```
yaml
```
yaml
version
:
^1.2.0
version
:
~1.2.3
```
```
This will match version 1.2.0 and any patches to that release (1.2.1, 1.2.999, and so on)
This will match version
`1.2.3`
and any patches to that release. In other words,
`~1.2.3`
is equivalent to
`>= 1.2.3, < 1.3.0`
For the complete version matching syntax, please see the
[
semver documentation
](
https://github.com/Masterminds/semver#checking-version-constraints
)
### Repository URLs
### Repository URLs
...
@@ -42,4 +44,4 @@ tags:
...
@@ -42,4 +44,4 @@ tags:
- webaccelerator
- webaccelerator
```
```
This allows a user to turn that feature on and off with one tag.
This allows a user to turn that feature on and off with one tag.
\ No newline at end of file
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment