[Bin Du (northtyphoon)]

PR Summary

Generate the OCI config blob as {} instead of a zero-byte file when publishing to a container registry.

• Upload the generated config file using its SHA-256 digest instead of uploading a separate empty blob.
• Generate a unique config path up front so an existing module nupkg/config.json cannot cause hashing and upload to use different files.
• Set the manifest config size to the UTF-8 byte count of {} (2 bytes), retaining application/vnd.oci.image.config.v1+json.
• Add offline regression tests for config content and digest, manifest descriptors, uploaded bytes, upload failures, and publishing with an existing module config file.

Validation

• .\build.ps1 -Build -BuildConfiguration Debug -BuildFramework net472 - passed.
• Invoke-Pester .\test\PublishPSResourceTests\ContainerRegistryConfig.Tests.ps1 -Output Detailed -PassThru - passed, 5/5 tests on both PowerShell Core and Windows PowerShell 5.1, with the built module imported and Pester 5.7.1.
• git --no-pager diff --check - passed.
• Not run: live Azure Container Registry integration tests or the CI Pester 4.x runner.

PR Context

The config descriptor advertises a JSON media type, but the previous config blob was empty and therefore could not be parsed as JSON. Publishing an empty JSON object makes the content valid JSON while keeping the descriptor's digest and size consistent with the uploaded bytes. The package layer and existing media types are unchanged; no command syntax or documentation changes are required.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Documentation needed
    • Issue filed:
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and enumerated concerns in the summary.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

🟡 Changes recommended

An existing nupkg/config.json can cause hashing and upload to use different files, producing a digest mismatch that makes the registry reject the publish.

1 open issue

• Use the generated config file consistently for hashing and upload · New

What changed in this PR

This PR updates container registry publishing to use {} as the OCI config blob instead of an empty file, keeping the uploaded content and manifest descriptor consistent.

Changes:

• Create and upload the JSON config using its SHA-256 digest.
• Set the manifest config size to 2 bytes while preserving existing media types.
• Add offline regression tests for config content, descriptors, uploads, and upload failures.

File	Description
test/​PublishPSResourceTests/​ContainerRegistryConfig.Tests.ps1	Adds offline tests for config generation and uploading.
src/​code/​ContainerRegistryServerAPICalls.cs	Generates and uploads {} and updates the manifest config size.

_{Review effort: Balanced}