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.

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

Merged
merged 1 commit into from
Apr 18, 2020

Conversation

MrArnoldPalmer
Copy link
Contributor

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.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

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.
@mergify mergify bot added contribution/core This is a PR that came from AWS. labels Apr 17, 2020
@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
  • Commit ID: 3e154b5
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@skinny85 skinny85 merged commit c6f9a14 into master Apr 18, 2020
@skinny85 skinny85 deleted the fix/invalid-dotnet-version-ranges branch April 18, 2020 00:03
skinny85 pushed a commit to skinny85/jsii that referenced this pull request Apr 18, 2020
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)
skinny85 added a commit to skinny85/aws-cdk that referenced this pull request Apr 18, 2020
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).
skinny85 added a commit to skinny85/aws-cdk that referenced this pull request Apr 18, 2020
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).
skinny85 added a commit to aws/aws-cdk that referenced this pull request Apr 18, 2020
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).
@eladb
Copy link
Contributor

eladb commented Apr 18, 2020

Curious @MrArnoldPalmer what introduced this issue?

@MrArnoldPalmer
Copy link
Contributor Author

@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. 🤷‍♂️

@eladb
Copy link
Contributor

eladb commented Apr 18, 2020

Cool. Thanks for the details. Worth mentioning the root cause in the PR/commit description next time :-)

@iliapolo iliapolo mentioned this pull request Apr 20, 2020
RomainMuller pushed a commit that referenced this pull request Apr 20, 2020
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.
RomainMuller pushed a commit that referenced this pull request Apr 20, 2020
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution/core This is a PR that came from AWS.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants