Skip to content

Coordinate public versions across module and NuGet releases - #676

Merged
PrzemyslawKlys merged 1 commit into
mainfrom
codex/coordinated-public-version-20260803
Aug 3, 2026
Merged

Coordinate public versions across module and NuGet releases#676
PrzemyslawKlys merged 1 commit into
mainfrom
codex/coordinated-public-version-20260803

Conversation

@PrzemyslawKlys

Copy link
Copy Markdown
Member

Summary

  • coordinate the module automatically when a project or package build is the selected release source
  • treat occupied NuGet versions as conflicts on the initial coordinated publish
  • allow duplicate-tolerant NuGet behavior only for a checkpoint-proven retry of the same attempted lane
  • document and regenerate the public PowerShell help for the coordinated release contract

Why

A coordinated release must publish one version across its module and aligned NuGet packages. This prevents a duplicate package from being reported as success while PSGallery and GitHub continue with an older module version.

No package is published by this pull request.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@PrzemyslawKlys
PrzemyslawKlys merged commit 553ade8 into main Aug 3, 2026
7 checks passed
@PrzemyslawKlys
PrzemyslawKlys deleted the codex/coordinated-public-version-20260803 branch August 3, 2026 21:37
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.

1 participant