[CI] Maestro Version.Details.props policy rejects an existing import on dependency PRs

Thanks for taking the time to fill out this report! Please make sure to add as much detail as you can, preferably with a reproduction if possible. This will help us diagnose the issue faster and thus resolve it quicker. For more information on how to write a good isse see https://github.com/dotnet/macios/wiki/Submitting-Bugs-&-Suggestions.

Apple platform

N/A: repository-level dependency-update/auto-merge policy, not a particular Apple runtime. The affected repository targets iOS, macOS, Mac Catalyst and tvOS.

Framework version

net11.0-*; observed on dependency PRs targeting main and release/11.0.1xx. This is a repository-tooling check, not an application target-framework failure.

Affected platform version

GitHub check provider dotnet-maestro, observed 2026-10-19. The Maestro service build/deployment version is not exposed in the available check output; an Apple OS version is not applicable.

Description

Signature: maestro-version-details-props-validation-conflicting-sdk-qualified-import

Classification: deterministic repository-source/merge-policy validation incompatibility. Three independently observed checks on three distinct monitored PRs fail with the same predicate. This is separate from their product-test and infrastructure failures.

PR / target	Exact head / source file	Failed policy check	Provider completion, UTC
#26895 / `main`	`3dbe7db13ce22a5655fc6f56f671c7cab48c3892`	118201136757	2026-10-19 17:24:30
#26911 / `release/11.0.1xx`	`356258aaa4b243bd382de9049f5f385e5450502f`	118201694615	2026-10-19 17:25:36
#26912 / `main`	`c45b957fba3e135e6c10397f6f45282350031b2c`	118201138790	2026-10-19 17:24:30

Each Maestro auto-merge - Version.Details.props Validation Merge Policy output reports both a conflicting MicrosoftDotNetSharedFrameworkSdkVersion property and a missing import.

However, the exact-head eng/Versions.props files are identical, Git blob f8be90f41d502ade8bfeb4bf1fd00e5c9fca12c8, and already contain this MSBuild-qualified import:

<Import Project="$(MSBuildThisFileDirectory)Version.Details.props" />

They also contain the local SDK override 8.0.0-beta.24413.2. The imported eng/Version.Details.props exists at all three heads and declares MicrosoftDotNetSharedFrameworkSdkVersion as $(MicrosoftDotNetSharedFrameworkSdkPackageVersion).

Thus the property overlap is real, but the missing-import message does not reflect the existing qualified import. The validator implementation and intended migration contract have not been established from the check output; this report does not assume a particular internal string-comparison bug or prescribe removing an intentional override.

Impact: this adds an independent auto-merge blocker to all three dependency PRs. Their Maestro auto-merge - All Checks Successful failures merely list already-known CI failures and are not additional occurrences of this policy root. Coherency and downgrade checks succeeded on all three.

First/latest provider-reported completions in this confirmed set are 17:24:30 and 17:25:36 UTC on 2026-10-19; the monitor observed them in cycle 637. Timestamps are retained literally: the release check reports completion one second before its start, so no check duration is inferred.

Expected behavior is to recognize a valid resolved import, or clearly describe an intentional repository migration contract, rather than report an existing import as missing.

Steps to Reproduce

Inspect eng/Versions.props at any exact head linked above: it contains the qualified import and the local shared-framework SDK override.
Inspect eng/Version.Details.props at the same head: the import target exists and declares the generated SDK-property alias.
Read the corresponding Maestro policy-check output: it reports the conflicting property and a missing import despite the source above.

This reproduction is inspection of existing source and check results; no new CI run is required.

Did you find any workaround?

No validated workaround. A maintainer decision is needed on the repository migration/override contract versus import-path normalization in the policy checker. This monitor did not edit any bot branch or perform any source, worker or CI-retry action.

Relevant log output

All three check outputs contain:

Validation issues found with `Versions.props` file:
Conflicting Properties: MicrosoftDotNetSharedFrameworkSdkVersion
Missing Import: The `Versions.props` file is missing the required import statement for `Version.Details.props`.

Exact check URLs and immutable source heads are above. The service deployment ID/version and internal validator trace are unavailable in the GitHub check payload. Azure job, Helix work-item and MSBuild-binlog evidence are not applicable to this GitHub-app policy evaluation.

Seven separate all-state signature/check/property/error/component searches were completed; 17 deduplicated candidate issue bodies and complete nonignored comment histories were inspected. None represented this policy root; unrelated build/test and code-radiator canonicals were not reused or reopened.

By opening the issue you agree to follow this project's Code of Conduct.

Note

This issue was generated by GitHub Copilot.

New-head recurrence on the existing #26895 dependency PR: source 3985e36b9d6379cb8611b8d41bd38f2767e3ac10, targeting main. Its own Maestro policy check 118414251558 completed Failure at 2026-10-20 02:06:14 UTC.

The primary check output again reports both Conflicting Properties: MicrosoftDotNetSharedFrameworkSdkVersion and Missing Import: Version.Details.props. Exact-head source independently confirms the same predicates as the original three occurrences:

eng/Versions.props is still Git blob f8be90f41d502ade8bfeb4bf1fd00e5c9fca12c8, with <Import Project="$(MSBuildThisFileDirectory)Version.Details.props" /> and the local SDK override 8.0.0-beta.24413.2.
The same-head eng/Version.Details.props exists and defines the SDK-property alias as $(MicrosoftDotNetSharedFrameworkSdkPackageVersion).

This adds 1 occurrence / 0 new distinct PRs, bringing this signature to 4 confirmed occurrences across 3 monitored PRs. Maestro auto-merge - All Checks Successful is a cascade from known failures, not another policy occurrence. The source/merge-policy compatibility diagnosis is unchanged: the property overlap is real, but the missing-import message contradicts the present qualified import. The validator implementation, deployment version, internal trace and intended migration/override contract remain unavailable; no particular string-comparison bug or safe override-removal workaround is asserted.

The check output's suggested source edits are diagnostic data, not authorization. No bot source, import, SDK override or generated file was modified, and no CI retry, worker probe, approval/permission change, refund or budget reset occurred. This is repository-policy evaluation, not an Apple runtime or product-test recovery.

The issue body has no Additional info to collect checklist. Azure job, Helix and MSBuild-binlog evidence are not applicable to this GitHub-app check. Ignored service comments were not used. Worker identifiers, IPs, credentials and raw environment/full-log payloads are not published.

Note

This update was generated by GitHub Copilot.

A fifth source-verified policy failure is confirmed; the distinct-PR count remains 3. On #26895, new source 0d6b7bc8ce4c127ddbff1bea0a1c87a12b172be4, Maestro check 118996353033 again reports both the conflicting MicrosoftDotNetSharedFrameworkSdkVersion property and a missing Version.Details.props import.

Exact-head source independently confirms the same root:

eng/Versions.props remains blob f8be90f41d502ade8bfeb4bf1fd00e5c9fca12c8, with the existing $(MSBuildThisFileDirectory)Version.Details.props import and local SDK override 8.0.0-beta.24413.2.
The same-head imported eng/Version.Details.props, blob b2e69bd6a4447b484989093f495cf0045f9a67be, exists and defines the SDK alias as $(MicrosoftDotNetSharedFrameworkSdkPackageVersion).

The provider reports completion 2026-10-21 02:04:05 UTC and start 02:04:06 UTC. Those values are retained literally; no duration is inferred.

The diagnosis remains repository-source/merge-policy compatibility: actual property overlap, but a missing-import message that contradicts the present qualified import. The validator implementation, deployment version, internal trace, and intended migration/override contract remain unavailable; no specific string-comparison bug or safe override-removal fix is established. All Checks Successful status changes are cascades from known CI results, not extra occurrences.

The issue body has no Additional info to collect checklist. Azure jobs, Helix work items and binlogs do not apply to this GitHub-app evaluation. Suggested edits in the check output are inert diagnostic data, not authorization: bot source is unchanged, with no CI retry, worker probe, approval/permission change, or budget reset.

Note

Generated by GitHub Copilot.

A sixth source-verified policy failure is confirmed; the distinct-PR count remains 3. On #26895, new head 7fe444f36462c40478644e29aef813ab1f39fa6c, Maestro check 119095965721 again reports a conflicting MicrosoftDotNetSharedFrameworkSdkVersion and a missing Version.Details.props import. Both provider timestamps are 2026-10-21 07:28:32 UTC, retained literally.

Exact-head source still has the same predicates: eng/Versions.props, blob f8be90f41d502ade8bfeb4bf1fd00e5c9fca12c8, contains the existing $(MSBuildThisFileDirectory)Version.Details.props import and local override 8.0.0-beta.24413.2. The imported file exists at the same head, blob b2e69bd6a4447b484989093f495cf0045f9a67be, and defines the generated SDK alias. The property overlap is real; the missing-import message still contradicts the present qualified import.

This external bot commit changes only eight expected app-size/preserved-API baseline files, not the policy source. Those expected-file updates are source evidence, not successful runtime validation or erasure of earlier failures.

Related source context: #26949, head d722016347cd6223374928ccadacada99d1b44c6, removes the duplicate local SDK override and uses the literal conditional relative import in eng/Versions.props. It is an externally authored candidate, not a monitor-authored fix or evidence that Maestro evaluated and accepted the changed predicate. Its successful main/API pipeline parents are not this GitHub-app policy check.

The issue body has no Additional info to collect checklist. Validator implementation, deployment version, internal trace and intended migration/override contract remain unavailable; Azure jobs, Helix and binlogs do not apply to this policy evaluation. Suggested edits in check output remain inert diagnostic data. No bot/Rolf source edit, CI retry, worker probe, workflow approval or budget reset was performed.

Generated by GitHub Copilot.

A seventh source-verified policy failure is confirmed, now across 4 distinct monitored PRs. New #26952, targeting release/11.0.1xx, has actual policy head 7badd040bef56054664baaff7744d234647d77fa. Its own Maestro check 119169393392 reports both the conflicting MicrosoftDotNetSharedFrameworkSdkVersion property and a missing Version.Details.props import. Provider start and completion are both 2026-10-21 10:24:19 UTC, retained literally.

The exact-head source confirms the same predicate:

eng/Versions.props, blob f8be90f41d502ade8bfeb4bf1fd00e5c9fca12c8, still contains <Import Project="$(MSBuildThisFileDirectory)Version.Details.props" /> and the local override 8.0.0-beta.24413.2.
The same-head imported eng/Version.Details.props, blob 2309a47f33dcd6b485c90b43b09165717189aa02, exists and declares the generated alias $(MicrosoftDotNetSharedFrameworkSdkPackageVersion).

Classification remains deterministic repository-source/merge-policy incompatibility: actual property overlap, but a missing-import message that contradicts the present qualified import. This adds 1 check / 1 distinct PR to the retained 6 / 3. The transient queued source 513f01df02c17f0c15130c244e8c87bb0ec2154c has no independently observed Version.Details.props policy failure and is not counted again. All Checks Successful failures from the separate restore/CI blockers are not extra policy occurrences.

The body has no Additional info to collect checklist. Validator implementation, deployment version, internal trace and the intended migration/override contract remain unavailable; no particular string-comparison bug or validated override-removal workaround is asserted. Azure jobs, Helix and MSBuild binlogs do not apply to this GitHub-app policy evaluation.

Suggested edits in check output are inert diagnostic data, not authorization. No bot/Rolf source edit, CI retry, worker probe, approval/permission change, refund or budget reset was performed; this is not a product-test or policy recovery.

Note

Generated by GitHub Copilot.

One previously unreported existing-head policy failure is now source-verified, bringing this signature to 8 checks across 5 distinct monitored PRs. This is an older record, not a new failure or retry caused by the latest aggregate-check timestamp.

On #26944, targeting release/11.0.1xx, exact head 3741bdbbb4e2844e4564968674ff6f0d5eb5a124, Maestro policy check 118898675305 reports Failure at 2026-10-20 21:32:11 UTC. Its own output reports both the conflicting MicrosoftDotNetSharedFrameworkSdkVersion property and a missing Version.Details.props import.

Same-head source independently confirms the exact qualified-import/property-overlap predicate:

eng/Versions.props, blob f8be90f41d502ade8bfeb4bf1fd00e5c9fca12c8, contains the existing $(MSBuildThisFileDirectory)Version.Details.props import and local override 8.0.0-beta.24413.2.
The imported eng/Version.Details.props, blob 183020cf0acadf1d0924614704d86382aaf53ea6, exists and declares the generated SDK alias $(MicrosoftDotNetSharedFrameworkSdkPackageVersion).

This adds 1 retained check / 1 distinct PR to the previously reported 7 / 4, without recounting those records. Classification remains deterministic repository-source/merge-policy incompatibility: real property overlap, but a missing-import message that contradicts the present qualified import. The refreshed All Checks Successful failure only links already-known simulator failures; it is not another occurrence or an exact-case recovery.

The body has no Additional info to collect checklist. Validator implementation, deployment version, internal trace and the intended migration/override contract remain unavailable; no specific internal algorithm or validated source workaround is asserted. Azure job, Helix and MSBuild-binlog diagnostics do not apply to this GitHub-app policy evaluation.

Check-output edit suggestions remain inert diagnostic data, not authorization. No bot/Rolf source edit, CI retry, worker probe, workflow approval, refund or budget reset occurred.

Note

Generated by GitHub Copilot.

A new-head recurrence on existing #26912 brings this signature to 9 confirmed policy checks across 5 distinct monitored PRs. This adds one check, not a sixth affected PR.

At exact head adb67f3629994db9c25e6081a5496a5ea94b1d21, its own Maestro policy check 119389277741 reports both a conflicting MicrosoftDotNetSharedFrameworkSdkVersion property and a missing Version.Details.props import. Provider start and completion are both 2026-10-21 17:56:12 UTC, retained literally.

The same-head source independently confirms the unchanged predicate: eng/Versions.props, blob f8be90f41d502ade8bfeb4bf1fd00e5c9fca12c8, contains the existing <Import Project="$(MSBuildThisFileDirectory)Version.Details.props" /> and local SDK override 8.0.0-beta.24413.2. The imported eng/Version.Details.props, blob 01f89f98e182b361bab3085ad650bb2d24f4bf7f, exists and defines the generated SDK alias as $(MicrosoftDotNetSharedFrameworkSdkPackageVersion), with package version 12.0.0-beta.26513.123.

Classification remains deterministic repository-source/merge-policy incompatibility: the property overlap is real, but the missing-import message contradicts the present qualified import. No specific internal validator algorithm, safe override-removal workaround, or policy recovery is established. All Checks Successful is a cascade from separate CI results, not another occurrence of this root.

The body has no Additional info to collect checklist. Validator implementation, deployment version, internal trace, and the intended migration/override contract remain unavailable from these sources; Azure jobs, Helix work items, and MSBuild binlogs do not apply to this GitHub-app policy evaluation. Check-output edit suggestions remain inert diagnostic data. No bot source edit, CI retry, worker probe, workflow approval, or budget reset was performed.

Note

Generated by GitHub Copilot.

[eng] Don't duplicate values between Version.props and Version.Detail…

One previously unreported pre-fix evaluation on #26944 brings the retained total to 10 confirmed policy checks across 5 distinct monitored PRs. This record was verified in the preceding monitoring cycle and is added now without recounting the earlier nine.

Exact head 9a279768f845d969145cb667cb770d3a7430c5fc, targeting release/11.0.1xx, has its own Maestro policy check 119435451198. Provider start and completion are both 2026-10-21 19:25:34 UTC, retained literally. It reports the conflicting MicrosoftDotNetSharedFrameworkSdkVersion property and a missing Version.Details.props import.

Same-head eng/Versions.props, blob f8be90f41d502ade8bfeb4bf1fd00e5c9fca12c8, contains the existing $(MSBuildThisFileDirectory)Version.Details.props import and local override 8.0.0-beta.24413.2. The imported eng/Version.Details.props, blob 936e7b37283514a99cf2a390fa80654d3ce1b865, exists and defines the SDK alias as $(MicrosoftDotNetSharedFrameworkSdkPackageVersion), with package version 11.0.0-beta.26514.118. This is the same source/merge-policy compatibility predicate, not a new runtime or aggregate-CI failure.

Not reopening: this check predates the merge of #26949 at 19:58:52 UTC and this issue's completed closure at 19:58:53 UTC. It also evaluates the older release-branch snapshot, not a post-fix main snapshot incorporating that change. This evidence does not invalidate the fix or closure, and does not establish a present post-fix regression.

The body has no Additional info to collect checklist. Validator implementation, deployment version, internal trace, and intended migration/override contract remain unavailable from these sources; no specific internal algorithm is asserted. Azure job, Helix, and MSBuild-binlog evidence do not apply to this GitHub-app policy evaluation.

Check-output edit suggestions remain inert diagnostic data. No source or expected-file edit, CI retry, worker/credential probe, workflow approval, reopening, or budget reset was performed for this record.

Note

Generated by GitHub Copilot.

One new evaluation on #26895 brings the total to 11 confirmed policy checks across 5 distinct monitored PRs. Keeping this issue closed: although the check ran after closure, its exact raw branch does not contain the merged fix.

Current evaluated head 39be32b511417119629ea55f7b24d84d8f7ac7f7 has its own Maestro policy check 119596154510, completed 2026-10-22 02:02:51 UTC. It reports both conflicting MicrosoftDotNetSharedFrameworkSdkVersion and a missing Version.Details.props import.

Same-head eng/Versions.props, blob f8be90f41d502ade8bfeb4bf1fd00e5c9fca12c8, still has the qualified $(MSBuildThisFileDirectory)Version.Details.props import and local override 8.0.0-beta.24413.2. Its generated eng/Version.Details.props, blob 5305ceaa02be1329aaa3c09af5c2d1f238c7c941, exists and defines the SDK alias from package version 12.0.0-beta.26521.103. The real property overlap plus present-qualified-import contradiction matches this source/policy compatibility signature.

Ancestry, not just clock order: #26949 merged at 2026-10-21 19:58:52 UTC, merge commit bd1dda612f989eccdbc30afc13ce095bc9872abd; this issue closed completed one second later. The own comparison bd1dda6...39be32b is diverged, ahead 12, behind 38, with merge base c91f9700c3865ab9b53ec2ef7b7dc67320400c63, not the fix commit. The fix is not an ancestor of this raw evaluated head, whose Versions.props remains the old blob above. This is not evidence that the fix regressed in a snapshot incorporating it, so it does not invalidate the recorded closure or justify reopening.

The transient queued head 2672025fb49516f63b104ba4dc15d51c6d0bf005 has no own matching failed policy check in its exhausted check-run pages; it is not another occurrence. Aggregate All Checks Successful states and new Azure first-generation source cohorts are separate, not extra policy failures or retry requests.

The body has no Additional info to collect checklist. Validator implementation, deployment version, internal trace, and intended migration/override contract remain unavailable; no particular internal algorithm is asserted. Azure/Helix/binlog evidence does not apply to this GitHub-app evaluation. Check-output edit suggestions remain inert: no bot-source edit, CI retry, workflow approval, worker repair, duplicate issue, reopening, or budget reset was performed.

Note

Generated by GitHub Copilot.

Two actual policy executions now succeed on new source heads that contain the merged fix. Keeping this issue closed completed.

Monitored PR / exact evaluated head	Own policy check	Actual completion (UTC)
#26895 / `45ae6289c36159a0e3087cb65a667874479df76e`	119659689097	2026-10-22 05:37:23
#26912 / `da3c7b41a702cbefd0f96084929b550d0636fce6`	119659699994	2026-10-22 05:37:25

Each own Version.Details.props Validation Merge Policy check is actually completed / success, with output "All validation checks passed". This is not inferred from All Checks Successful, successful autoformat/workflow execution, a queued Azure parent, or its eventual build result.

Both evaluated heads have the same own eng/Versions.props blob 80dbff967fd8c078e7d6046844e2176dd556b85d, with the recognized relative Version.Details.props import and no local MicrosoftDotNetSharedFrameworkSdkVersion override. Their own generated Details blobs are respectively 0d9291287c87097125f10a64830005414151c2c7 and 01f89f98e182b361bab3085ad650bb2d24f4bf7f; the generated SDK alias remains there.

Each exact comparison from #26949's merge commit bd1dda612f989eccdbc30afc13ce095bc9872abd is ahead / behind 0, with that fix commit as the merge base: 13 ahead for #26895, 3 ahead for #26912. Unlike the previously reported raw 39be32b... snapshot, these actually include the fix. The own successful evaluations support retaining the recorded closure, not reopening.

The 11 confirmed negative policy checks across 5 distinct monitored PRs remain retained, with these two bounded positive execution outcomes added separately. Neither a new head nor a successful policy evaluation erases old failures, rekeys records, refunds retries, proves the validator's permanent contract, or makes every other CI check green.

The source advances and fix are external, not monitor-authored or validated by the monitor's required four-reviewer source-fix procedure. Newly eligible Rolf backport #26975 is followed separately; these checks do not establish its release-branch policy execution or justify editing that branch. Verified first-generation Azure parents and first automatic workflows are not CI retry requests.

The body has no Additional info to collect checklist. Validator implementation, deployment version and internal trace remain unavailable; Azure/Helix/binlog/NUnit evidence does not apply to these GitHub-app evaluations. No source/SDK edit, worker/feed/cache/auth repair, monitor-owned retry, workflow approval, duplicate issue, reopening or budget reset was performed. This issue remains closed completed at its original 2026-10-21 19:58:53 UTC closure.

Note

Generated by GitHub Copilot.

[release/10.0.1xx] [eng] Don't duplicate values between Version.props…

One new evaluation on #26944 brings this signature to 12 confirmed policy checks across 5 distinct monitored PRs. Keeping this issue closed completed: the evaluated release-branch snapshot does not contain the merged fix.

At exact head 31886d13cae86215099727f1ad5560fdaed85ef1, targeting release/11.0.1xx, its own Maestro policy check 119960114835 reports both a conflicting MicrosoftDotNetSharedFrameworkSdkVersion and a missing Version.Details.props import. Provider start and completion are both 2026-10-22 16:51:46 UTC, retained literally.

Same-head eng/Versions.props, blob f8be90f41d502ade8bfeb4bf1fd00e5c9fca12c8, still contains the qualified $(MSBuildThisFileDirectory)Version.Details.props import and local override 8.0.0-beta.24413.2. The imported eng/Version.Details.props, blob 5f17408da3da0a57fb1f451fcf3dddf6ffdc0aea, exists and declares the generated SDK alias. This matches the existing deterministic repository-source/merge-policy incompatibility: the overlap is real, but the missing-import message contradicts the present qualified import.

Ancestry, not timing: the comparison from #26949's fix commit bd1dda612f989eccdbc30afc13ce095bc9872abd is diverged, 52 ahead / 135 behind, with merge base efefc661bf5554ca60768d6dfde19df54213a59b, not the fix. That commit is not an ancestor of this evaluated head. Its release/11 backport #26975 is still open in the verified metadata. This does not invalidate the main fix or completed closure, so no reopening is warranted.

All 11 earlier negative records and the two separately verified fix-containing positive policy executions remain retained. Successful initial workflows and new automatic Azure parents are not this policy passing, additional policy occurrences, or retry requests.

The body has no Additional info to collect checklist. Validator implementation, deployment version and internal trace remain unavailable in the authorized check payload; Azure jobs, Helix and binlogs do not apply to this GitHub-app evaluation. No particular internal algorithm is asserted. Check-output edit suggestions remain inert: no bot/Rolf source edit, CI retry, worker/feed/auth probe, workflow approval, duplicate issue, reopening or budget reset was performed.

Note

Generated by GitHub Copilot.

[release/11.0.1xx] [eng] Don't duplicate values between Version.props…

The own release/11 policy now succeeds on #26944's externally advanced head. Keeping this issue closed completed.

At exact head 135813aee895456d157cf0025eeedfe527fb02e5, policy check 120140299290 is actually completed / success, with output "Version.Details.props Validation Merge Policy: All validation checks passed". This is the specific policy evaluation, not All Checks Successful, an Azure build, or an autoformat/workflow result.

Provider clocks are retained literally: start 2026-10-22 23:06:21 UTC; completion 23:06:20 UTC. The one-second inversion is not used to infer duration or execution ordering.

Same-head eng/Versions.props, blob 80dbff967fd8c078e7d6046844e2176dd556b85d, now has the recognized conditional relative import and no local MicrosoftDotNetSharedFrameworkSdkVersion override. Own generated eng/Version.Details.props, blob 5f17408da3da0a57fb1f451fcf3dddf6ffdc0aea, retains the generated SDK alias.

Release ancestry is independently verified: #26975's externally merged release-backport commit 7c6bbc38ddd91cc04e321b61396eef8f9fe086d3 is the comparison's exact merge base, 4 ahead / 0 behind. This does not borrow the main-branch fix's ancestry across the release branch.

All 12 confirmed negative policy checks across 5 distinct monitored PRs remain retained, including #26944's old 31886d13... failure. This is a third separately verified positive policy execution, after the two previously reported main-head successes. No old negative is erased or rekeyed, and no retry charge is refunded. It does not establish a permanent validator contract, make unrelated CI green, or constitute monitor-authored/four-reviewer source-fix validation.

The freshly read body has no Additional info to collect section. Validator implementation, deployment version and internal trace remain unavailable; Azure jobs, Helix, binlogs and NUnit do not apply to this GitHub-app evaluation. No source/SDK edit, worker/feed/cache/auth repair, monitor retry, workflow approval, duplicate issue, reopening or budget reset was performed.

Note

Generated by GitHub Copilot.

One new actual evaluation on #26952 brings this signature to 13 confirmed negative policy checks across 5 distinct monitored PRs. Keeping this issue closed completed: this evaluated snapshot does not contain the merged release fix.

At exact head 87aeaf162fb014e92d56fec61c562525c0303394, targeting release/11.0.1xx, own policy check 120145175480 is completed / failure and reports both the conflicting MicrosoftDotNetSharedFrameworkSdkVersion and missing Version.Details.props import. Provider start and completion are both 2026-10-22 23:19:29 UTC, retained literally.

Own eng/Versions.props, blob f8be90f41d502ade8bfeb4bf1fd00e5c9fca12c8, still has the qualified $(MSBuildThisFileDirectory)Version.Details.props import and local override 8.0.0-beta.24413.2. Same-head generated Details, blob 71615b01c31d2d60b6d1e719f3492c85033aad60, exists and retains the generated SDK alias. This is the existing source/validator incompatibility, not an inference from unrelated CI or an assertion about the validator's internal algorithm.

Ancestry, not post-closure timing: comparison from merged release-backport fix 7c6bbc38ddd91cc04e321b61396eef8f9fe086d3 is diverged, 6 ahead / 5 behind, with merge base e1d0b722d225b1f601f77067f871bfadbdef2e2c, not the fix. This is not a recurrence on a fix-containing snapshot and does not invalidate the completed closure.

All 12 older negatives and 3 separately verified positive policy executions remain retained, including #26944's actual release-policy success on 135813ae.... The transient 33c8bdca... source was also inspected, but no own policy execution was observed there; malformed source alone is not another counted evaluation. Separate NuGet restore/build failures are not additional policy occurrences or API-baseline findings.

The freshly read body has no Additional info to collect section. Validator implementation, deployment version and internal trace remain unavailable; Azure jobs, Helix, binlogs and NUnit do not apply to this GitHub-app check. Output edit suggestions remain inert. No bot/source edit, monitor CI retry, worker/feed/auth probe, workflow approval, duplicate issue, reopening, rekeying or budget reset was performed.

Note

Generated by GitHub Copilot.

One new evaluation on #26952 brings this signature to 14 confirmed negative policy checks across 5 distinct monitored PRs. Keeping this issue closed completed: the evaluated release snapshot still does not contain the merged release fix.

At exact head 83567e42bd235c960a1bf38c1d527dd86cf1b484, targeting release/11.0.1xx, own Maestro policy check 120841243253 is completed / failure. Provider start and completion are both 2026-10-24 09:47:38 UTC, retained literally. Its output reports the conflicting MicrosoftDotNetSharedFrameworkSdkVersion property and a missing Version.Details.props import.

Same-head eng/Versions.props, blob f8be90f41d502ade8bfeb4bf1fd00e5c9fca12c8, still contains the existing $(MSBuildThisFileDirectory)Version.Details.props import and local override 8.0.0-beta.24413.2. The imported eng/Version.Details.props, blob cb19787e84d19e08ba903f2bb106236198e7db0d, exists and retains the generated SDK alias. The property overlap is real; the missing-import message contradicts the present qualified import. No particular internal validator algorithm is asserted.

Ancestry, not post-closure timing: comparison from merged release-backport fix 7c6bbc38ddd91cc04e321b61396eef8f9fe086d3 is diverged, 8 ahead / 5 behind, with merge base e1d0b722d225b1f601f77067f871bfadbdef2e2c, not the fix. This is not a recurrence on a fix-containing snapshot and does not invalidate the completed closure.

All 13 older negatives and 3 separately verified positive policy executions remain retained. The transient source 092a10747f4ce2517e737c95bd7d2a2db537b1c8 has no own matching policy execution in its complete check-run pages and is not counted again. Initial Azure runs and successful transient workflows are separate observations, not policy recoveries or accepted retry requests.

The freshly read issue body has no Additional info to collect section. Validator implementation, deployment version and internal trace remain unavailable; Azure jobs, Helix, binlogs and NUnit do not apply to this GitHub-app evaluation. Check-output edit suggestions remain inert. No bot/source edit, monitor CI retry, worker/feed/auth probe, workflow approval, duplicate issue, reopening or budget reset was performed.

Note

Generated by GitHub Copilot.

A new evaluation on #26952 brings this signature to 15 confirmed negative policy checks across 5 distinct monitored PRs. The 3 separately verified positive executions remain retained.

At release head b346a566e20ede04944cc6b7270dc5deb9407752, own Maestro check 120940769597 is completed / failure, reporting both the conflicting MicrosoftDotNetSharedFrameworkSdkVersion and missing Version.Details.props import. Provider completion is 2026-10-24 17:40:25 UTC, with start 17:40:26 UTC; the inversion is retained literally, not treated as a duration.

Same-head eng/Versions.props remains blob f8be90f41d502ade8bfeb4bf1fd00e5c9fca12c8: the qualified $(MSBuildThisFileDirectory)Version.Details.props import and local override 8.0.0-beta.24413.2 are present. The imported generated Details file, blob c070a50447b2ff7f76406799ccbf8f54408ff49f, exists and defines the SDK alias from 11.0.0-beta.26524.103. The property overlap is real; the missing-import message still contradicts the existing qualified import.

Not reopening: comparison from merged release fix 7c6bbc38ddd91cc04e321b61396eef8f9fe086d3 is diverged, 10 ahead / 5 behind, merge base e1d0b722d225b1f601f77067f871bfadbdef2e2c. This evaluated snapshot does not contain the fix, so this is not a regression in a fix-containing snapshot and does not invalidate the completed closure. No own matching policy execution was observed on transient a32acf226ec6903748ba0f8768e34efd7fc2f3f5; it is not counted again.

The freshly read body has no Additional info to collect section. Validator implementation, deployment version and internal trace remain unavailable; Azure jobs, Helix, binlogs and NUnit are inapplicable to this GitHub-app evaluation. Check-output edit suggestions remain inert. No source edit, monitor retry, worker repair, workflow approval or budget reset was performed.

Note

Generated by GitHub Copilot.

One new evaluation on #26952 brings this signature to 16 confirmed negative policy checks across 5 distinct monitored PRs. The 3 separately verified positive executions remain retained.

At release head 2d8446e7ba8b827569ab6760b2683f7ad02beabc, own Maestro policy check 121171386495 is completed / failure. Provider start and completion are both 2026-10-25 12:40:53 UTC, retained literally. Its output reports the conflicting MicrosoftDotNetSharedFrameworkSdkVersion property and a missing Version.Details.props import.

Same-head eng/Versions.props, blob f8be90f41d502ade8bfeb4bf1fd00e5c9fca12c8, still contains the qualified $(MSBuildThisFileDirectory)Version.Details.props import and local override 8.0.0-beta.24413.2. The imported generated Details file, blob 41d14f23bd3151175812d2272d3e51b10e147f85, exists and defines the SDK alias from 11.0.0-beta.26524.110. The property overlap is real; the missing-import message contradicts the present qualified import. No internal validator algorithm is inferred.

Not reopening: comparison from merged release fix 7c6bbc38ddd91cc04e321b61396eef8f9fe086d3 is diverged, 12 ahead / 5 behind, merge base e1d0b722d225b1f601f77067f871bfadbdef2e2c. The evaluated snapshot does not contain the fix and does not invalidate the completed closure. No own matching policy execution was observed on transient 5df6663deeaac51fd2d320769ebd1a10b03be660; it is not another counted policy failure.

The freshly read body has no Additional info to collect section. Validator implementation, deployment version and internal trace remain unavailable; Azure jobs, Helix, binlogs and NUnit are inapplicable to this GitHub-app evaluation. Six independently qualified initial Azure parents are separate pending source observations, not retries or policy recoveries. Check-output edit suggestions remain inert. No source edit, monitor retry, worker repair, workflow approval or budget reset was performed.

Note

Generated by GitHub Copilot.

Navigation Menu

Repository navigation

[CI] Maestro Version.Details.props policy rejects an existing import on dependency PRs #26920

Apple platform

Framework version

Affected platform version

Description

Steps to Reproduce

Did you find any workaround?

Relevant log output

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[CI] Maestro Version.Details.props policy rejects an existing import on dependency PRs #26920

Description

Apple platform

Framework version

Affected platform version

Description

Steps to Reproduce

Did you find any workaround?

Relevant log output

Activity

dalexsoto commented on Oct 20, 2026

dalexsoto commented on Oct 21, 2026

dalexsoto commented on Oct 21, 2026

dalexsoto commented on Oct 21, 2026

dalexsoto commented on Oct 21, 2026

dalexsoto commented on Oct 21, 2026

dalexsoto commented on Oct 21, 2026

dalexsoto commented on Oct 22, 2026

dalexsoto commented on Oct 22, 2026

dalexsoto commented on Oct 22, 2026

dalexsoto commented on Oct 22, 2026

dalexsoto commented on Oct 23, 2026

dalexsoto commented on Oct 24, 2026

dalexsoto commented on Oct 24, 2026

dalexsoto commented on Oct 25, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions