1.202.0

microsoft · Mar 16, 2022 · 53d952e · 53d952e
1 parent b792d6e
commit 53d952e
Show file tree

Hide file tree

Showing 5 changed files with 2,244 additions and 2,198 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -3,6 +3,14 @@ All notable changes to the Azure Pipelines extension will be documented in this
 
 The format is based on [Keep a Changelog](http://keepachangelog.com/). Versioning follows an internal Azure DevOps format that is not compatible with SemVer.
 
+## 1.202.0
+### Added
+- Your organization's schema will now be auto-detected and used if your repo is hosted in Azure Repos
+### Fixed
+- Updated dependencies to fix security vulnerabilities
+### Updated
+- M200 schema
+
 ## 1.195.0
 ### Fixed
 - Emojis no longer cause validation to fail (thanks @PaulTaykalo!)

diff --git a/RELEASE.md b/RELEASE.md
@@ -1,8 +1,9 @@
 # Releasing the extension
 
 0. Work in a branch. I sometimes go with `ship-<version-num>`, for example, `ship-191`.
-0. Ensure package.json and package-lock.json have the version number you want to release.
-  - You can do this with `npm version --no-git-tag-version <patch|minor|major>` to get both files at once.
+0. Find the current sprint using https://whatsprintis.it.
+0. Update the version to the major sprint number using `npm version --no-git-tag-version THE_SPRINT_VERSION`.
+  - Replace `THE_SPRINT_VERSION` with `patch` if you are doing a bugfix release.
 0. Ensure the CHANGELOG is up to date.
 0. Update the [service schema](#bumping-service-schema).
 0. Create a PR on GitHub, mostly for tracking reasons.

diff --git a/package-lock.json b/package-lock.json
diff --git a/package.json b/package.json
@@ -2,7 +2,7 @@
     "name": "azure-pipelines",
     "displayName": "Azure Pipelines",
     "description": "Syntax highlighting, IntelliSense, and more for Azure Pipelines YAML",
-    "version": "1.201.0",
+    "version": "1.202.0",
     "publisher": "ms-azure-devops",
     "aiKey": "AIF-d9b70cd4-b9f9-4d70-929b-a071c400b217",
     "repository": {