chore(deps): use ranges for dependencies and lock devDependencies

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# Global rule:
+* @microsoft/akvelon-build-task-team    @microsoft/azure-pipelines-platform

.github/workflows/autoAssignABTT.yml

@@ -0,0 +1,25 @@
+name: Auto Assign ABTT to Project Board
+
+on:
+  issues:
+    types:
+      - opened
+
+jobs:
+  assign_one_project:
+    runs-on: ubuntu-latest
+    name: Assign to ABTT Project
+    steps:
+    - name: "Add triage and area labels"
+      uses: actions-ecosystem/action-add-labels@v1
+      with:
+        github_token: ${{ secrets.GITHUB_TOKEN }}
+        labels: |
+          Area: TaskLib
+          triage
+
+    - name: "Assign newly opened issues to project board"
+      uses: actions/add-to-project@v0.4.1
+      with:
+        project-url: https://github.com/orgs/microsoft/projects/755
+        github-token: ${{ secrets.ABTT_TOKEN }}

.github/workflows/localization-automerge.yml

@@ -0,0 +1,25 @@
+name: 'LEGO automerge'
+
+on:
+  pull_request:
+    types:
+      - opened
+    branches:
+      - Localization
+
+jobs:
+  worker:
+    runs-on: ubuntu-latest
+
+    if: github.actor == 'csigs'
+    steps:
+      - uses: actions/github-script@v3
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          script: |
+            github.pulls.merge({
+              owner: context.payload.repository.owner.login,
+              repo: context.payload.repository.name,
+              pull_number: context.payload.pull_request.number,
+              merge_method: 'squash'
+            })

.github/workflows/stale.yml

@@ -0,0 +1,21 @@
+
+name: Mark stale issues and pull requests
+
+on:
+  schedule:
+  - cron: "0 * * * *"
+
+jobs:
+  stale:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/stale@v3
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        stale-issue-message: 'This issue has had no activity in 90 days. Please comment if it is not actually stale'
+        stale-issue-label: 'stale'
+        days-before-stale: 90
+        days-before-close: 7
+        exempt-pr-label: 'no-stale'

.gitignore

@@ -44,4 +44,7 @@ node/.taskKey
 
 # powershell compiled helper
 powershell/CompiledHelpers/bin
-powershell/CompiledHelpers/obj
+powershell/CompiledHelpers/obj
+
+# generate third party notice script
+!generate-third-party-notice.js

CONTRIBUTING.md

@@ -0,0 +1,33 @@
+# Instructions for Contributing Code
+
+## Contributing bug fixes
+
+We are currently accepting contributions in the form of bug fixes. A bug must have an issue tracking it in the issue tracker. Your pull request should include a link to the bug that you are fixing. If you've submitted a PR for a bug, please post a comment in the bug to avoid duplication of effort.
+
+## Contributing features
+
+Features (things that add new or improved functionality) may be accepted, but will need to first be approved in the form of a suggestion issue.
+
+Design changes will not be accepted at this time. If you have a design change proposal, please log a suggestion issue.
+
+## Legal
+
+You will need to complete a Contributor License Agreement (CLA). Briefly, this agreement testifies that you are granting us permission to use the submitted change according to the terms of the project's license, and that the work being submitted is under appropriate copyright.
+
+Please submit a Contributor License Agreement (CLA) before submitting a pull request. You may visit <https://cla.microsoft.com> to sign digitally.
+
+## Housekeeping
+
+Your pull request should:
+
+* Include a description of what your change intends to do
+* Be a child commit of a reasonably recent commit in the **master** branch
+  * Requests need not be a single commit, but should be a linear sequence of commits (i.e. no merge commits in your PR)
+* It is desirable, but not necessary, for the tests to pass at each commit
+* Have clear commit messages
+  * e.g. "Refactor feature", "Fix issue", "Add tests for issue"
+* Include adequate tests
+  * At least one test should fail in the absence of your non-test code changes. If your PR does not match this criteria, please specify why
+  * Tests should include reasonable permutations of the target fix/change
+  * Include baseline changes with your change
+  * All changed code must have 100% code coverage

ISSUE_TEMPLATE.md

@@ -0,0 +1,23 @@
+Please check our current Issues to see if someone already reported this https://github.com/Microsoft/azure-pipelines-task-lib/issues
+
+### Environment
+azure-pipelines-task-lib version: 
+
+### Issue Description
+<!--- Please provide a short description of the issue -->
+
+### Expected behaviour
+<!--- Tell us what should happen -->
+
+### Actual behaviour
+<!--- Tell us what happens instead -->
+
+### Steps to reproduce
+1. 
+2. 
+3. 
+4. 
+5. 
+
+### Logs
+<!-- Any logs you have/stack traces/etc. -->

README.md

@@ -1,16 +1,22 @@
 
-# VSTS DevOps Task SDK
+# Azure Pipelines Task SDK
 
-Libraries for writing [Visual Studio Team Services](https://www.visualstudio.com/en-us/products/visual-studio-team-services-vs.aspx) build and deployment tasks
+Libraries for writing [Azure Pipelines](https://azure.microsoft.com/en-us/services/devops/pipelines/) tasks
 
-Reference examples of our in the box tasks [are here](https://github.com/Microsoft/vsts-tasks)
+Reference examples of our in the box tasks [are here](https://github.com/microsoft/azure-pipelines-tasks)
 
 ## Status
+
 |   | Build & Test |
 |---|:-----:|
-|![Win](res/win_med.png) **Windows**|![Build & Test](https://mseng.visualstudio.com/DefaultCollection/_apis/public/build/definitions/b924d696-3eae-4116-8443-9a18392d8544/2553/badge?branch=master)| 
-|![Apple](res/apple_med.png) **OSX**|![Build & Test](https://mseng.visualstudio.com/_apis/public/build/definitions/b924d696-3eae-4116-8443-9a18392d8544/5471/badge?branch=master)|
-|![Ubuntu14](res/ubuntu_med.png) **Ubuntu 14.04**|![Build & Test](https://mseng.visualstudio.com/_apis/public/build/definitions/b924d696-3eae-4116-8443-9a18392d8544/4123/badge?branch=master)|
+|![Win-x64](res/win_med.png) **Windows**|[![Build & Test][win-build-badge]][build]| 
+|![macOS](res/apple_med.png) **macOS**|[![Build & Test][macOS-build-badge]][build]| 
+|![Linux-x64](res/ubuntu_med.png) **Linux**|[![Build & Test][linux-build-badge]][build]|
+
+[win-build-badge]: https://dev.azure.com/mseng/PipelineTools/_apis/build/status/azure-pipelines-task-lib-ci?branchName=master&jobname=windows
+[macOS-build-badge]: https://dev.azure.com/mseng/PipelineTools/_apis/build/status/azure-pipelines-task-lib-ci?branchName=master&jobname=macOS
+[linux-build-badge]: https://dev.azure.com/mseng/PipelineTools/_apis/build/status/azure-pipelines-task-lib-ci?branchName=master&jobname=linux
+[build]: https://dev.azure.com/mseng/PipelineTools/_build/latest?definitionId=7623
 
 ## Highlights
 
@@ -20,9 +26,9 @@ Reference examples of our in the box tasks [are here](https://github.com/Microso
  * __Consistent API:__ The TypeScript and PowerShell libs are largely consistent. They only differ where it makes sense (being true to the platform).
  * __Tracing for free:__ Tracing has been built-in to many of the commands. Use the SDK and get some debug tracing for free.
 
-## Typescript Tasks  
+## TypeScript Tasks
 
-Cross platform tasks are written in Typescript.  It is the preferred way to write tasks once.
+Cross platform tasks are written in TypeScript.  It is the preferred way to write tasks once.
 
 [![NPM version][npm-lib-image]][npm-lib-url] ![VSTS](https://mseng.visualstudio.com/DefaultCollection/_apis/public/build/definitions/b924d696-3eae-4116-8443-9a18392d8544/2553/badge)
 
@@ -34,8 +40,16 @@ A task which automates Powershell technologies can be written with our Powershel
 
 Documentation: [PowerShell API](powershell/Docs/README.md)
 
+## Notes on authoring Tasks
+
+Starting from [version v2.141.0](https://github.com/Microsoft/azure-pipelines-agent/releases/tag/v2.141.0), the agent can now run on three OS architectures: x86, x64, and 32-bit ARM. When authoring a new task, you can check agent variable: `Agent.OSArchitecture` (possible values: X86, X64, ARM) to restrict running said task to a particular set of OS architectures.
 
-[npm-lib-image]: https://img.shields.io/npm/v/vsts-task-lib.svg?style=flat
-[npm-lib-url]: https://www.npmjs.com/package/vsts-task-lib
+
+[npm-lib-image]: https://img.shields.io/npm/v/azure-pipelines-task-lib.svg?style=flat
+[npm-lib-url]: https://www.npmjs.com/package/azure-pipelines-task-lib
 [npm-sdk-image]: https://img.shields.io/npm/v/vsts-task-sdk.svg?style=flat
 [npm-sdk-url]: https://www.npmjs.com/package/vsts-task-sdk
+
+## Security issues
+
+Do you think there might be a security issue? Have you been phished or identified a security vulnerability? Please don't report it here - let us know by sending an email to secure@microsoft.com.

SECURITY.md

@@ -0,0 +1,41 @@
+<!-- BEGIN MICROSOFT SECURITY.MD V0.0.7 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 [secure@microsoft.com](mailto:secure@microsoft.com).  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 -->

azure-pipelines-steps-node.yml

@@ -0,0 +1,16 @@
+parameters:
+- name: nodeVersion 
+  type: string
+
+steps:
+  # npm install
+- task: Npm@1
+  displayName: npm install
+  inputs:
+    command: install
+    workingDir: node
+
+- task: NodeTool@0
+  displayName: use node ${{parameters.nodeVersion}}
+  inputs:
+    versionSpec: ${{parameters.nodeVersion}}

azure-pipelines-steps-test-build.yml

@@ -0,0 +1,10 @@
+steps:
+  # test
+- script: node make.js test
+  workingDirectory: node
+  displayName: node make.js test  
+
+  # build
+- script: node make.js build
+  displayName: node make.js build
+  workingDirectory: node