Fix: Auto-publish feature on merge to main#24
Merged
Conversation
…ME for v2 Agent-Logs-Url: https://github.com/microsoft/aspire-devcontainer-feature/sessions/ff2b69ae-3aa4-4963-885d-40c0e7b702c5 Co-authored-by: IEvangelist <7679720+IEvangelist@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix unresolvable feature for aspire
Fix: Auto-publish feature on merge to main
Apr 2, 2026
IEvangelist
approved these changes
Apr 7, 2026
maddymontaquila
approved these changes
Apr 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The release workflow was
workflow_dispatch-only, so the feature was never republished after the org migration (dotnet → microsoft) and version bump to2.0.0in PR #22. As a result,ghcr.io/microsoft/aspire-devcontainer-feature/aspirewas never resolvable.Changes
.github/workflows/release.yaml— Addpush: branches: [main]trigger so the feature is published to GHCR automatically on every merge. The existingif: github.ref == 'refs/heads/main'job guard already prevents unintended runs.src/aspire/README.md— Update example reference from:1to:2to match current2.0.0version; add missingmicrosoft-aspire.aspire-vscodeextension omitted from the stale auto-generated docs.After merge, the release workflow will publish
ghcr.io/microsoft/aspire-devcontainer-feature/aspire:2.