-
Notifications
You must be signed in to change notification settings - Fork 245
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.
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
fix(jsii-pacmak): invalid dotnet version suffixes #1568
Conversation
Removes version suffix from version ranges in `.csproj` files generated by jsii-pacmak. Dotnet doesn't allow version suffixes that start with a number. Version ranges by default don't include prereleases so the resolved version is as intended without the suffix in this case.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Removes version suffix from version ranges in `.csproj` files generated by jsii-pacmak. Dotnet doesn't allow version suffixes that start with a number. Version ranges by default don't include prereleases so the resolved version is as intended without the suffix in this case. (cherry picked from commit c6f9a14)
Version 1.3.0 of jsii-packmak has a bug that makes it impossible to publish .NET packages generated with it to NuGet. It was fixed in aws/jsii#1568, released in version 1.3.1, so change our yarn.lock file to use that latest version (fortunately, we use carets in the dependency declarations on jsii-pacmak).
Version 1.3.0 of jsii-packmak has a bug that makes it impossible to publish .NET packages generated with it to NuGet. It was fixed in aws/jsii#1568, released in version 1.3.1, so change our yarn.lock file to use that latest version (fortunately, we use carets in the dependency declarations on jsii-pacmak).
Version 1.3.0 of jsii-packmak has a bug that makes it impossible to publish .NET packages generated with it to NuGet. It was fixed in aws/jsii#1568, released in version 1.3.1, so change our yarn.lock file to use that latest version (fortunately, we use carets in the dependency declarations on jsii-pacmak).
Curious @MrArnoldPalmer what introduced this issue? |
@eladb An update to node-semver changed how prerelease suffixes are parsed/output. We bumped semver and changed some code to handle the new behavior where needed. It wasn't apparent that the changed output broke dotnet because it doesn't cause issues until publishing. It's my understanding that it's a valid range and can be used in a .csproj for a binary project, it just can't be published to nuget because it breaks legacy versions of the toolchain. 🤷♂️ |
Cool. Thanks for the details. Worth mentioning the root cause in the PR/commit description next time :-) |
Removes version suffix from version ranges in `.csproj` files generated by jsii-pacmak. Dotnet doesn't allow version suffixes that start with a number. Version ranges by default don't include prereleases so the resolved version is as intended without the suffix in this case.
Removes version suffix from version ranges in `.csproj` files generated by jsii-pacmak. Dotnet doesn't allow version suffixes that start with a number. Version ranges by default don't include prereleases so the resolved version is as intended without the suffix in this case.
Removes version suffix from version ranges in
.csproj
files generatedby jsii-pacmak.
Dotnet doesn't allow version suffixes that start with a number. Version
ranges by default don't include prereleases so the resolved version is
as intended without the suffix in this case.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.