Prevent stale assemblies in ProjectBuild packages#520
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 548fa730d3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fe5e8491e7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Summary
ProjectBuild releases now rebuild package projects before packing and verify primary managed assemblies inside each NuGet package against the exact outputs from that fresh build. A stale
bin/objtree can no longer silently produce an older assembly under a newer package version.What changed
dotnet pack --no-buildfor per-project packingRestore;Rebuild;Packfor the parallel MSBuild strategylib/<tfm>,runtimes/<rid>/lib/<tfm>, andtools/<tfm>/anyagainst exact evaluated target directoriesCleanStaging, package provenance, and immutable-feed recovery in the schema, docs, and repository library-builder skillCompatibility
No consumer configuration changes are required. Release builds intentionally trade incremental compilation for artifact correctness.