chore: add 10.0.300 -> 10.0.127 to workload version map

[JoonghyunCho]

Summary

Tizen Workload 10.0.127 was released for the .NET SDK 10.0.3xx feature band (see v10.0.127), but the version map on main — which users fetch via the documented workload-install.sh / workload-install.ps1 URLs — did not have an entry for the 10.0.300 band.

• Add { "sdkBand": "10.0.300", "workloadVersion": "10.0.127" } to version-map.json
• Regenerate workload-install.sh / workload-install.ps1 via Generate-InstallScripts.ps1

Without this entry, the install scripts still resolve correctly while nuget.org is reachable (NuGet-first lookup), but the offline/fallback path would resolve the stale 10.0.100 -> 10.0.123 mapping for SDK 10.0.3xx users.

Same change landed on net10.0 as fc559a8.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the Tizen workload version map to ensure that users on the .NET SDK 10.0.3xx feature band correctly resolve to the latest Tizen Workload version (10.0.127). By updating the version mapping in the installation scripts, this change prevents the fallback mechanism from incorrectly resolving to older versions when NuGet is unreachable.

Highlights

• Workload Version Mapping: Added the mapping for Tizen Workload 10.0.127 to the 10.0.300 SDK feature band.
• Install Script Updates: Regenerated the PowerShell and shell installation scripts to include the new version mapping for offline/fallback resolution.

New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Ignored Files

• Ignored by pattern: workload/scripts/version-map.json (1)
  • workload/scripts/version-map.json

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the workload installation scripts (workload-install.ps1 and workload-install.sh) to include the mapping for the 10.0.300 SDK band pointing to version 10.0.127 in the auto-generated version maps. No review comments were provided, and there is no additional feedback.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.