Skip to content

[release/13.0] Add buildOnly field to manifest schema and infrastructure - #12713

Merged
Jose Perez Rodriguez (joperezr) merged 5 commits into
release/13.0from
backport/pr-12696-to-release/13.0
Nov 6, 2025
Merged

[release/13.0] Add buildOnly field to manifest schema and infrastructure#12713
Jose Perez Rodriguez (joperezr) merged 5 commits into
release/13.0from
backport/pr-12696-to-release/13.0

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 5, 2025

Copy link
Copy Markdown
Contributor

Backport of #12696 to release/13.0

/cc Eric Erhardt (@eerhardt) Copilot

Customer Impact

This manifest information is needed for azd to support PublishWithContainerFiles.

Testing

Victor Vazquez (@vhvb1989) is testing it with azd now.

Risk

Low. We are only writing new information to the manifest.

Regression?

No

The issue was that JavaScript apps using PublishAsDockerFile() were not setting HasEntrypoint=false on the correct annotation. The fix required setting it after WithDockerfileBuilder() since that method creates a new DockerfileBuildAnnotation that replaces the original one.

Co-authored-by: vhvb1989 <24213737+vhvb1989@users.noreply.github.com>
As requested in code review, reverting changes to JavaScriptHostingExtensions.cs.
The manifest publisher should describe current API behavior without modifying the APIs.

Co-authored-by: vhvb1989 <24213737+vhvb1989@users.noreply.github.com>
Added three comprehensive tests for the containerFiles feature:
- Single source with single destination
- Single source with multiple source paths
- Multiple sources with multiple destinations

All tests verify that containerFiles are correctly serialized to the manifest JSON.

Co-authored-by: vhvb1989 <24213737+vhvb1989@users.noreply.github.com>
@github-actions

github-actions Bot commented Nov 5, 2025

Copy link
Copy Markdown
Contributor Author

🚀 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/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 12713

Or

  • Run remotely in PowerShell:
iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 12713"

@eerhardt Eric Erhardt (eerhardt) added the Servicing-consider Issue for next servicing release review label Nov 5, 2025
@joperezr

Copy link
Copy Markdown
Member

Approved. Eric Erhardt (@eerhardt) can you double check with Victor Vazquez (@vhvb1989) before merging to ensure things work as expected?

@joperezr Jose Perez Rodriguez (joperezr) added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Nov 5, 2025
@eerhardt

Copy link
Copy Markdown
Member

can you double check with Victor Vazquez (@vhvb1989) before merging to ensure things work as expected?

Yep, we are working together to ensure the whole thing works end-to-end. We will need 1 more change though - #12716 (which is the main PR). That will need to be ported to 13.

@joperezr
Jose Perez Rodriguez (joperezr) merged commit 7e82de9 into release/13.0 Nov 6, 2025
582 of 585 checks passed
@joperezr
Jose Perez Rodriguez (joperezr) deleted the backport/pr-12696-to-release/13.0 branch November 6, 2025 01:40
@github-actions github-actions Bot locked and limited conversation to collaborators Dec 6, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants