diff options
| author | Michael Kubacki <michael.kubacki@microsoft.com> | 2022-09-16 15:44:27 -0400 |
|---|---|---|
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2022-09-22 19:12:25 +0000 |
| commit | dd1e20b3c281940c5b5783151b24cf6ceeb31ca3 (patch) | |
| tree | 3d91d4793f0a566182ec1a4f60fe65a2b4ab08ba /BaseTools | |
| parent | 62f00dad22bc657290780dc65c6f1b8ac6e88f9b (diff) | |
| download | edk2-dd1e20b3c281940c5b5783151b24cf6ceeb31ca3.tar.gz edk2-dd1e20b3c281940c5b5783151b24cf6ceeb31ca3.tar.bz2 edk2-dd1e20b3c281940c5b5783151b24cf6ceeb31ca3.zip | |
nasm_ext_dep.yaml: Remove leading zero in patch version
The patch version is currently: "2.15.05"
When a formal semantic version validator is run against this version
it is recognized as being invalid due to the leading zero in the
patch which is not allowed per the Semantic Versioning Specification:
https://semver.org/#spec-item-2
The NuGet Gallery already reports the version without the leading
zero: https://www.nuget.org/packages/mu_nasm/2.15.5
This change simply removes the leading zero to prevent code such as
https://pypi.org/project/semantic-version/ from reporting a version
error.
Cc: Bob Feng <bob.c.feng@intel.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Cc: Yuwei Chen <yuwei.chen@intel.com>
Cc: Sean Brogan <sean.brogan@microsoft.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Signed-off-by: Michael Kubacki <mikuback@linux.microsoft.com>
Reviewed-by: Michael D Kinney <michael.d.kinney@intel.com>
Diffstat (limited to 'BaseTools')
| -rw-r--r-- | BaseTools/Bin/nasm_ext_dep.yaml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/BaseTools/Bin/nasm_ext_dep.yaml b/BaseTools/Bin/nasm_ext_dep.yaml index 7a56dd2b8b..56703d4c18 100644 --- a/BaseTools/Bin/nasm_ext_dep.yaml +++ b/BaseTools/Bin/nasm_ext_dep.yaml @@ -13,6 +13,6 @@ "type": "nuget",
"name": "mu_nasm",
"source": "https://api.nuget.org/v3/index.json",
- "version": "2.15.05",
+ "version": "2.15.5",
"flags": ["set_path", "host_specific"]
}
|