Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release/7.0] Fix encoding problem when publishing #83577

Merged
merged 5 commits into from
Apr 5, 2023

Conversation

ilonatommy
Copy link
Member

@ilonatommy ilonatommy commented Mar 17, 2023

Backport of #82833 to release/7.0

Fixes #78953.

Customer Impact

Customers had a problem with publishing applications that were located in a path with Unicode chars. It was because Windows’s scripts do not support UTF-8 by default. Now we added that feature + tests.

Testing

The PR introduced changes in WasmBuildTests and they are passing.

Risk

Low, it broadens the accepted range of codes for Windows to UTF-8.

@ilonatommy ilonatommy added arch-wasm WebAssembly architecture area-Build-mono labels Mar 17, 2023
@ilonatommy ilonatommy self-assigned this Mar 17, 2023
@ghost
Copy link

ghost commented Mar 17, 2023

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

Manual backport of #82833 to release/7.0.

Author: ilonatommy
Assignees: ilonatommy
Labels:

arch-wasm, area-Build-mono

Milestone: -

@thaystg
Copy link
Member

thaystg commented Mar 17, 2023

The failures on CI are not connected.

@marek-safar marek-safar added the Servicing-approved Approved for servicing release label Mar 20, 2023
@marek-safar marek-safar added this to the 7.0.x milestone Mar 20, 2023
dotnet-maestro bot and others added 2 commits March 23, 2023 17:34
…23.1 (dotnet#83860)

Microsoft.NET.Workload.Emscripten.net6.Manifest-7.0.100 , Microsoft.NET.Workload.Emscripten.net7.Manifest-7.0.100
 From Version 7.0.4 -> To Version 7.0.5

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
@carlossanlop
Copy link
Member

I'm retargeting this PR to the new release/7.0-staging branch, which is the one that we will use from now on for servicing fixes.

Repo maintainers will now be allowed to merge their own servicing PR as long as it meets the requirements:

  • It is approved by Tactics (signaled by adding the Servicing-approved label).
  • It's signed-off by an area owner.
  • The CI is green, or the failures are investigated as unrelated.
  • And if the PR touches an OOB package, the necessary OOB authoring changes are added.

The new process is described here: runtime/docs/project/library-servicing.md.

The infra team will be actively monitoring servicing PRs to ensure all requirements are met and to help with any issues.

Let me know if you have any questions.

@carlossanlop carlossanlop changed the base branch from release/7.0 to release/7.0-staging March 28, 2023 21:00
@carlossanlop carlossanlop added Servicing-approved Approved for servicing release and removed Servicing-approved Approved for servicing release labels Mar 30, 2023
@carlossanlop
Copy link
Member

Reminder: April 10th is the last day to merge backport PRs to ensure they get included in the May Release. PR owners are now in charge of merging their own PRs.

@ilonatommy
Copy link
Member Author

Timezones failures on ios are not connected. Merging.

@ilonatommy ilonatommy merged commit eacc9be into dotnet:release/7.0-staging Apr 5, 2023
@ghost ghost locked as resolved and limited conversation to collaborators May 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-Build-mono Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants