Skip to content

[release/6.0] WasmAppBuilder: publish only once per target framework instead of invoking publish explicitly. - #59136

Merged
marek-safar merged 1 commit into
dotnet:release/6.0from
radical:fix-wasmappbuilder-6.0
Sep 15, 2021
Merged

[release/6.0] WasmAppBuilder: publish only once per target framework instead of invoking publish explicitly.#59136
marek-safar merged 1 commit into
dotnet:release/6.0from
radical:fix-wasmappbuilder-6.0

Conversation

@radical

@radicalradical commented Sep 15, 2021

Copy link
Copy Markdown
Member

Based on @ericstj's suggestion
#58816 (comment) .

Fixes#58816 .

@ghostghost added the area-Build-mono label Sep 15, 2021

@danmoseleydanmoseley left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I don't really have enough context to approve but this is breaking CI and if this it we should get it merged ASAP

@danmoseley

Copy link
Copy Markdown
Contributor

After the validation completes of course. Thanks for fixing..

@radical

Copy link
Copy Markdown
MemberAuthor

I'm hoping that this fixes it!

@radical
radicalforce-pushed the fix-wasmappbuilder-6.0 branch from a01d479 to 4d2eab4CompareSeptember 15, 2021 07:19
@radicalradical changed the title WasmAppBuilder: publish only once per target frameworkWasmAppBuilder: publish only once per target framework instead of invoking publish explicitly.Sep 15, 2021
@radical
radical marked this pull request as ready for review September 15, 2021 08:22
@radicalradical changed the title WasmAppBuilder: publish only once per target framework instead of invoking publish explicitly.[release/6.0] WasmAppBuilder: publish only once per target framework instead of invoking publish explicitly.Sep 15, 2021
@marek-safar
marek-safar merged commit 5d03338 into dotnet:release/6.0Sep 15, 2021
@radical
radical deleted the fix-wasmappbuilder-6.0 branch September 15, 2021 13:32
@danmoseley

Copy link
Copy Markdown
Contributor

Did this break originally get through PR validation just by bad luck?

@radical

Copy link
Copy Markdown
MemberAuthor

Did this break originally get through PR validation just by bad luck?

Yeah, race, and it happened to pass for all the builds that time 😬

radical added a commit to radical/runtime that referenced this pull request Sep 15, 2021
…instead of invoking publish explicitly. (dotnet#59136)
(cherry picked from commit 5d03338)
@ghostghost locked as resolved and limited conversation to collaborators Nov 3, 2021
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@radical@danmoseley@marek-safar