Update LICENSE.md to include MIT License

.github/workflows/ci.yml

@@ -6,6 +6,8 @@ name: CI
 on:
   pull_request:
     branches: [ main ]
+  push:
+    branches: [ main ]
 
   # Allows you to run this workflow manually from the Actions tab
   workflow_dispatch:
@@ -17,14 +19,14 @@ jobs:
       matrix: ${{ steps.set-matrix.outputs.matrix }}
     steps:
       - name: Checkout code
-        uses: actions/checkout@v2
+        uses: actions/checkout@v4
 
       - id: set-matrix
         run: |
           $obj = @{
             languagePack = Get-ChildItem i18n | ForEach-Object Name
           }
-          Write-Host "::set-output name=matrix::$($obj | ConvertTo-Json -Depth 100 -Compress)"
+          "matrix=$($obj | ConvertTo-Json -Depth 100 -Compress)" >> $env:GITHUB_OUTPUT
         shell: pwsh
   build:
     name: Build
@@ -34,7 +36,7 @@ jobs:
       matrix: ${{fromJSON(needs.determine-matrix.outputs.matrix)}}
     steps:
       - name: Checkout code
-        uses: actions/checkout@v2
+        uses: actions/checkout@v4
 
       - name: Generate Name
         run: node -e "console.log('PACKAGE_NAME=' + require('./i18n/${{ matrix.languagePack }}/package.json').name + '-v' + require('./i18n/${{ matrix.languagePack }}/package.json').version)" >> $GITHUB_ENV
@@ -43,10 +45,10 @@ jobs:
         run: cd ./i18n/${{ matrix.languagePack }} && npm i
 
       - name: Build Extension
-        run: cd ./i18n/${{ matrix.languagePack }} && npx vsce package -o ${{ env.PACKAGE_NAME }}.vsix
+        run: cd ./i18n/${{ matrix.languagePack }} && npx @vscode/vsce package -o ${{ env.PACKAGE_NAME }}.vsix
 
       - name: Publish Test Artifact
-        uses: actions/upload-artifact@v2
+        uses: actions/upload-artifact@v4
         with:
           name: ${{ env.PACKAGE_NAME }}.vsix
           path: ./i18n/${{ matrix.languagePack }}/${{ env.PACKAGE_NAME }}.vsix

LICENSE.md

@@ -4,6 +4,7 @@ Copyright (c) Microsoft Corporation
 
 All rights reserved.
 
+
 MIT License
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
@@ -23,3 +24,4 @@ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE
+

README.md

@@ -1,14 +1,12 @@
 # Visual Studio Code Language Packs
 
-[![CI](https://github.com/microsoft/vscode-loc/actions/workflows/ci.yml/badge.svg)](https://github.com/microsoft/vscode-loc/actions/workflows/ci.yml)
+Visual Studio Code is localized into many different languages using the concept of Language Packs. Language Packs can be installed by running the `>Configure Display Language` command in Visual Studio Code's Command Palette or installed via the [Visual Studio Code Marketplace](https://marketplace.visualstudio.com/search?target=VSCode&category=Language%20Packs&sortBy=Installs).
 
-This repository contains files to build localized Language Pack extensions for Visual Studio Code. A Language Pack contains the localized string resources for a particular language. 
+The original English strings can be found in the source code of the [open source repository](https://github.com/microsoft/vscode), and the localized strings for supported languages can be found in this repository.
 
-Localized resource files are managed and edited in Microsoft Localization Community. Files will be exported to this repository when prepare the publishing of language pack.
+Localized resource files are managed and edited by Microsoft. Files will be exported to this repository when strings are updated to prepare for the publishing of language packs.
 
-Language pack extensions are published to the [Visual Studio Code Marketplace](https://marketplace.visualstudio.com/search?target=VSCode&category=Language%20Packs&sortBy=Installs)
-
-There are currently 14 "Core" languages for Visual Studio Code.
+There are currently 14 supported languages for Visual Studio Code.
 
 |Language|Visual Studio Code Language ID|MLCP Language Code|
 |--------|--------|--------|
@@ -24,23 +22,23 @@ There are currently 14 "Core" languages for Visual Studio Code.
 |**Czech**|cs|Czech (cs-CZ)
 |**Portuguese (Brazil)**|pt-br|Portuguese (Brazil) (pt-br)
 |**Turkish**|tr|Turkish (tr-tr)
-|**Polish**|pl| Polish (pl-pl)
+|**Polish**|pl|Polish (pl-pl)
 |**Pseudo Language**|qps-ploc|Pseudo (qps-ploc)
 
 ## Contributing
 
-If you want to give feedback or report issue, please create a [new GitHub issue](https://github.com/microsoft/vscode-loc/issues/new). Please check if a topic about your issue already exists!.
-Since translation strings are managed and edited in Microsoft Localization Platform. Change can only be made there. So pull request won't be accepted in vscode-loc repo except language pack readme.md.
+If you want to give feedback or report an issue with a translation, please create a [new GitHub issue](https://github.com/microsoft/vscode-loc/issues/new). Please check if a topic about your issue already exists!
+Translation strings are managed on the Microsoft Localization Platform, and changes to strings can only be made there. Consequently, pull requests fixing translations won't be accepted. All other PRs to things like `README.md`, `package.json`, etc., will be accepted at the discretion of the maintainers.
 
 ## Legal
 
-Before we can accept your pull request you will need to sign a **Contribution License Agreement**. All you need to do is to submit a pull request, then the PR will get appropriately labelled (e.g. `cla-required`, `cla-norequired`, `cla-signed`, `cla-already-signed`). If you already signed the agreement we will continue with reviewing the PR, otherwise system will tell you how you can sign the CLA. Once you sign the CLA all future PR's will be labeled as `cla-signed`.
+Before we can accept your pull request, you will need to sign a **Contribution License Agreement**. All you need to do is submit a pull request. It will then be appropriately labeled (e.g., `cla-required`, `cla-norequired`, `cla-signed`, `cla-already-signed`). If you already signed the agreement, we will continue with reviewing the PR; otherwise, our system will tell you how you can sign the CLA. Once you sign the CLA, all future PRs will be labeled as `cla-signed`.
 
 # Microsoft Open Source Code of Conduct
 
 This project has adopted the [**Microsoft Open Source Code of Conduct**](https://opensource.microsoft.com/codeofconduct/).
-For more information see the [**Code of Conduct FAQ**](https://opensource.microsoft.com/codeofconduct/faq/) or
-contact [**[email protected]**](mailto:[email protected]) with any additional questions or comments.
+For more information, see the [**Code of Conduct FAQ**](https://opensource.microsoft.com/codeofconduct/faq/) or contact [**[email protected]**](mailto:[email protected]) with any additional questions or comments.
+
+## License
 
-## License 
 [MIT](LICENSE.md)

SECURITY.md

@@ -0,0 +1,41 @@
+<!-- BEGIN MICROSOFT SECURITY.MD V0.0.8 BLOCK -->
+
+## Security
+
+Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
+
+If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below.
+
+## Reporting Security Issues
+
+**Please do not report security vulnerabilities through public GitHub issues.**
+
+Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report).
+
+If you prefer to submit without logging in, send email to [[email protected]](mailto:[email protected]).  If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey).
+
+You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). 
+
+Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
+
+  * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
+  * Full paths of source file(s) related to the manifestation of the issue
+  * The location of the affected source code (tag/branch/commit or direct URL)
+  * Any special configuration required to reproduce the issue
+  * Step-by-step instructions to reproduce the issue
+  * Proof-of-concept or exploit code (if possible)
+  * Impact of the issue, including how an attacker might exploit the issue
+
+This information will help us triage your report more quickly.
+
+If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs.
+
+## Preferred Languages
+
+We prefer all communications to be in English.
+
+## Policy
+
+Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd).
+
+<!-- END MICROSOFT SECURITY.MD BLOCK -->

build/release.yml

@@ -29,12 +29,20 @@ resources:
 extends:
   template: azure-pipelines/extension/pre-release.yml@templates
   parameters:
+    publishExtension: true
+    useContinuousReleaseSignal: false
     usePreReleaseChannel: false
+    ghCreateRelease: false
     workingDirectory: $(Build.SourcesDirectory)/i18n/$(languagePack)
     buildSteps:
       - pwsh: |
           [version]$version = Get-Content -Raw ./package.json | ConvertFrom-Json | Select-Object -ExpandProperty version
-          $patch = Get-Date -Format MddHHmm
+          $patch = Get-Date -Format yyyyMMddHH
           npm version "$($version.Major).$($version.Minor).$patch"
         displayName: Update version
         workingDirectory: $(Build.SourcesDirectory)/i18n/$(languagePack)
+
+      - pwsh: |
+          Join-Path $env:BUILD_SOURCESDIRECTORY LICENSE.md | Copy-Item -Destination .
+        displayName: Copy LICENSE.md file
+        workingDirectory: $(Build.SourcesDirectory)/i18n/$(languagePack)