fix(core): fix the value check for publishConfig.provenance

[smorimoto]

What's the problem this PR addresses?

This PR resolves an issue where the publishConfig.provenance field in package.json wasn't being read correctly.

Specifically:

• When publishConfig.provenance: true was set in package.json, Yarn's npm publish command wouldn't generate provenance statements
• Whilst the PublishConfig interface had provenance?: boolean defined, the load method in Manifest.ts was missing the processing logic for the provenance field when handling publishConfig
• Other fields (access, main, module, browser, registry, bin, executableFiles) were being processed correctly, but provenance was the only one being omitted

How did you fix it?

I added the following code to the publishConfig processing section within the load method in packages/yarnpkg-core/sources/Manifest.ts:

if (typeof data.publishConfig.provenance === `boolean`)
  this.publishConfig.provenance = data.publishConfig.provenance;

This fix ensures:

1. The publishConfig.provenance field in package.json is read correctly when it's a boolean value
2. It becomes available as workspace.manifest.publishConfig.provenance
3. The existing logic in npm publish command (publish.ts lines 109-120) functions properly

Additionally, to ensure the accuracy of the fix, I added test cases to packages/yarnpkg-core/tests/Manifest.test.ts:

• Test for when provenance: true is set
• Test for when provenance: false is set
• Test to verify that non-boolean values are ignored

With this fix, when publishConfig.provenance is configured in package.json, provenance statements will be generated as expected.

Checklist

• I have read the Contributing Guide.
• I have set the packages that need to be released for my changes to be effective.
• I will check that all automated PR checks pass before the PR gets reviewed.

[smorimoto]

The failure of CI has nothing to do with this PR, and #6776 needs to be merged first.

[clemyan]

It is not possible for workspace.manifest.publishConfig to have a provenance key but set to undefined, because workspace.manifest is parsed from JSON. So using in here is correct. In fact, this change causes { "publishConfig": { "provenance": false } } to be ignored.

The fact that publishConfig.provenance in manifests do not take effect is not a bug with the publish code, but rather a bug with the manifest parser in Manifest.ts in the core.

[smorimoto]

@clemyan Correct! I just updated the PR!

[smorimoto]

When do you expect this PR to be merged and released?