Skip to content

Main Build Failure Cleanup#1296

Open
Omnideth wants to merge 8 commits intoCommunityToolkit:mainfrom
Omnideth:package-upgrades
Open

Main Build Failure Cleanup#1296
Omnideth wants to merge 8 commits intoCommunityToolkit:mainfrom
Omnideth:package-upgrades

Conversation

@Omnideth
Copy link
Copy Markdown
Contributor

@Omnideth Omnideth commented May 2, 2026

**Closes #1287 **

Technically this doesn't have an issue yet, I intend to make it a WIP PR before asking for review, but I did double dip with the Powershell PR I made, and will close out, so I'll use that issue as the Issue Number.

This PR is an attempt to try and get main clean again.

It required me to break the CPM rule and target various versions - which isn't nice, but also is required since the OpenTelemetry.* packages are at varying numbers.

It's possible there is a more elegant way to achieve this, but I wasn't aware of it.

If you have dotnet 11 and are not in the dev container, the allowPrerelease will prevent you from building.

The only warning is I believe an oustanding issue with .SqlProjects.

PR Checklist

  • Created a feature/dev branch in your fork (vs. submitting directly from a commit on main)
  • Based off latest main branch of toolkit
  • PR doesn't include merge commits (always rebase on top of our main, if needed)
  • New integration
    • Docs are written
    • Added description of major feature to project description for NuGet package (4000 total character limit, so don't push entire description over that)
  • Tests for the changes have been added (for bug fixes / features) (if applicable)
  • Contains NO breaking changes
  • Every new API (including internal ones) has full XML docs
  • Code follows all style conventions

Will make this a working PR, and edit as we go.

Other information

The intent is to try and get main and the ci/cd stable enough to full clear a build.

… clean again.

It required me to break the CPM rule and target various versions - which isn't nice, but also is required since the OpenTelemetry.* packages are at varying numbers.

It's possible there is a more elegant way to achieve this, but I wasn't aware of it.

If you have dotnet 11 and are not in the dev container, the allowPrerelease will prevent you from building.

The only warning is I believe an oustanding issue with .SqlProjects.
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 2, 2026

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/CommunityToolkit/Aspire/main/eng/scripts/dogfood-pr.sh | bash -s -- 1296

Or

  • Run remotely in PowerShell:
iex "& { $(irm https://raw.githubusercontent.com/CommunityToolkit/Aspire/main/eng/scripts/dogfood-pr.ps1) } 1296"

@Omnideth
Copy link
Copy Markdown
Contributor Author

Omnideth commented May 3, 2026

I believe these tests are all struggling prior to the build issues completed. I intend to take a look at some of them later to try and clean them up if I can, but let me know if this type of PR would be allowed WITHOUT fixing all the tests first.

@Omnideth Omnideth marked this pull request as ready for review May 3, 2026 22:57
Copilot AI review requested due to automatic review settings May 3, 2026 22:57
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR aims to restore a clean build on main by updating central package versions (notably OpenTelemetry) and adding explicit package references to address vulnerability/build failures, plus adjusting devcontainer certificate handling guidance.

Changes:

  • Updated OpenTelemetry central versioning and pinned specific instrumentation package versions in central package management.
  • Added explicit package references in specific integrations (PowerShell, KurrentDB) and centrally pinned System.Security.Cryptography.Xml to address restore/audit failures.
  • Updated devcontainer configuration and docs around dev-certs, including adding a devcontainer lock file.

Reviewed changes

Copilot reviewed 8 out of 9 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
src/CommunityToolkit.Aspire.Hosting.PowerShell/CommunityToolkit.Aspire.Hosting.PowerShell.csproj Adds explicit references (OTel + System.Security.Cryptography.Xml) to influence resolved dependency versions.
src/CommunityToolkit.Aspire.Hosting.KurrentDB/CommunityToolkit.Aspire.Hosting.KurrentDB.csproj Adds OpenTelemetry.Api reference to influence resolved dependency versions.
docs/setup.md Adds a devcontainer note about dev-certs tooling.
Directory.Packages.props Pins OTel instrumentation versions and adds System.Security.Cryptography.Xml to central versions.
Directory.Build.props Bumps OpenTelemetryVersion property.
.gitignore Ignores *.lscache.
.devcontainer/post-create.sh Removes dotnet dev-certs auto-trust logic in favor of external tooling.
.devcontainer/devcontainer.json Adds devcontainer-dev-certs feature.
.devcontainer/devcontainer-lock.json Introduces a devcontainer features lock file.

Comment thread .devcontainer/devcontainer-lock.json
Comment thread Directory.Packages.props Outdated
Comment thread docs/setup.md Outdated
@afscrome afscrome mentioned this pull request May 4, 2026
10 tasks
afscrome and others added 6 commits May 4, 2026 21:36
Co-authored-by: Copilot <copilot@github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
…sed by the Copilot review of the initial PR.
@Omnideth
Copy link
Copy Markdown
Contributor Author

Omnideth commented May 5, 2026

Worked with @afscrome to combo his test cleanup with my main build cleanup. I addressed the copilot issues. Requesting formal review.

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.

Powershell Breaks CI - System.Security.Cryptography.Xml

3 participants