Skip to content

Replace <PackageLicenseFile> with <PackageLicenseExpression>#32

Merged
jnm2 merged 2 commits intobuvinghausen:masterfrom
michael-wolfenden:feature/package-license-expression
Aug 12, 2025
Merged

Replace <PackageLicenseFile> with <PackageLicenseExpression>#32
jnm2 merged 2 commits intobuvinghausen:masterfrom
michael-wolfenden:feature/package-license-expression

Conversation

@michael-wolfenden
Copy link
Contributor

Because an embedded license file is used instead of an SPDX tag, automated tools like nuget-license and packageguard are unable to detect this package's license. Also the license does not show up in the package's metadata in nuget.

Packing a license expression or a license file
recommends that MIT-licensed packages should have <PackageLicenseExpression>MIT</PackageLicenseExpression> instead of referring to a file.

The License.md file can still remain in the package, just the metadata would change.

Because an embedded license file is used instead of an SPDX tag, automated tools like [nuget-license](https://github.com/tomchavakis/nuget-license) and [packageguard](https://github.com/dennisdoomen/packageguard) are unable to detect this package's license. Also the license does not show up in the package's metadata in nuget.

[Packing a license expression or a license file
](https://learn.microsoft.com/en-us/nuget/reference/msbuild-targets#packing-a-license-expression-or-a-license-file) recommends that MIT-licensed packages should have `<PackageLicenseExpression>MIT</PackageLicenseExpression>` instead of referring to a file.

The `License.md` file can still remain in the package, just the metadata would change.
@jnm2
Copy link
Collaborator

jnm2 commented Aug 10, 2025

Closing and reopening the PR to see if the required build check resets.

@jnm2 jnm2 closed this Aug 10, 2025
@jnm2 jnm2 reopened this Aug 10, 2025
@jnm2
Copy link
Collaborator

jnm2 commented Aug 10, 2025

@buvinghausen Can you go to this repo's branch protection settings and fix the issue? A check named build was at one time required to succeed, but it no longer exists under https://github.com/buvinghausen/TaskTupleAwaiter/tree/master/.github/workflows.

@jnm2 jnm2 requested a review from buvinghausen August 10, 2025 01:34
@jnm2
Copy link
Collaborator

jnm2 commented Aug 10, 2025

Hey, something must have resolved. I just now had a button to approve this PR to build, and a workflow has started.

@jnm2
Copy link
Collaborator

jnm2 commented Aug 10, 2025

Looks like the main branch is not building. I'll try to get that fixed.

@jnm2
Copy link
Collaborator

jnm2 commented Aug 10, 2025

I fixed CI at #33. We're just waiting for @buvinghausen now because I took some liberties in that PR to reduce the doc burden, but I'll wait for him to confirm before it merges. Then this PR will be unblocked.

@jnm2 jnm2 merged commit bca7214 into buvinghausen:master Aug 12, 2025
1 check passed
@jnm2
Copy link
Collaborator

jnm2 commented Aug 12, 2025

Thanks @michael-wolfenden!

@michael-wolfenden
Copy link
Contributor Author

@jnm2 Will there be a new package released?

@jnm2
Copy link
Collaborator

jnm2 commented Aug 14, 2025

That's up to @buvinghausen I think!

@buvinghausen
Copy link
Owner

@jnm2 I thought I made you a collaborator both here and on nuget but let me kick the tires and do a release

@buvinghausen
Copy link
Owner

Also sorry for the delays but unfortunately my current job has me on Azure DevOps so I don't sign into GitHub nearly as often

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants