From d644d4c92e910bfb7a4d374bb97f6736643b4da2 Mon Sep 17 00:00:00 2001 From: Don Jayamanne Date: Thu, 3 Mar 2022 06:41:50 +1100 Subject: [PATCH 1/2] Bump package.json version --- .github/release_plan.md | 3 +++ package-lock.json | 2 +- package.json | 2 +- 3 files changed, 5 insertions(+), 2 deletions(-) diff --git a/.github/release_plan.md b/.github/release_plan.md index 3ebffd189cb..1ec6d5affc8 100644 --- a/.github/release_plan.md +++ b/.github/release_plan.md @@ -23,6 +23,9 @@ - [ ] If there are `release` branches that are two versions old (e.g. release-2020.[current month - 2]) you can delete them at this time (you would have to un-protect the release branches temporarily to delete them). - [ ] Update `main` after creating the release branch. (Warning: this should happen right after creating the release branch. If this is deferred till later, the `main` and `release` branches can diverge significantly, which may cause merge conflicts.) - [ ] Merge the changes from release (Changelog, delete news, ThirdPartyNotices) into `main` branch + - [ ] Update version in `package.json` branch to point to the next version, + - If latest is `2022.2.100`, them bump it to `2022.3.100`, + - This ensures the new new pre-release targets the next version. - [ ] Create a pull request against `main` - [ ] Merge pull request into `main` - [ ] GDPR bookkeeping (@greazer) (🤖; Notes in OneNote under Python VS Code -> Dev Process -> GDPR) diff --git a/package-lock.json b/package-lock.json index 83a73f80f9f..c5fd5807ca4 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,6 +1,6 @@ { "name": "jupyter", - "version": "2022.2.101", + "version": "2022.3.100", "lockfileVersion": 1, "requires": true, "dependencies": { diff --git a/package.json b/package.json index 6716dab4d80..dc639fe94ea 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "jupyter", "displayName": "Jupyter", - "version": "2022.2.101", + "version": "2022.3.100", "description": "Jupyter notebook support, interactive programming and computing that supports Intellisense, debugging and more.", "publisher": "ms-toolsai", "author": { From cc68ba9372215b7a988a5816f3a597f98bb48fd7 Mon Sep 17 00:00:00 2001 From: Don Jayamanne Date: Thu, 3 Mar 2022 06:44:05 +1100 Subject: [PATCH 2/2] Misc --- .github/release_plan.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/.github/release_plan.md b/.github/release_plan.md index 1ec6d5affc8..221730252f4 100644 --- a/.github/release_plan.md +++ b/.github/release_plan.md @@ -23,9 +23,12 @@ - [ ] If there are `release` branches that are two versions old (e.g. release-2020.[current month - 2]) you can delete them at this time (you would have to un-protect the release branches temporarily to delete them). - [ ] Update `main` after creating the release branch. (Warning: this should happen right after creating the release branch. If this is deferred till later, the `main` and `release` branches can diverge significantly, which may cause merge conflicts.) - [ ] Merge the changes from release (Changelog, delete news, ThirdPartyNotices) into `main` branch - - [ ] Update version in `package.json` branch to point to the next version, + - [ ] Bump the version number to the next monthly ("YYYY.M.100") release in the `main` branch - If latest is `2022.2.100`, them bump it to `2022.3.100`, - This ensures the new new pre-release targets the next version. + - [ ] `package.json` + - [ ] `package-lock.json` + - [ ] Confirm the 3rd part of the version ends with `100`. - [ ] Create a pull request against `main` - [ ] Merge pull request into `main` - [ ] GDPR bookkeeping (@greazer) (🤖; Notes in OneNote under Python VS Code -> Dev Process -> GDPR) @@ -72,11 +75,6 @@ * If released version is `YYYY.MM.110`, then hot fix will be `YYYY.MM.120` # Day of VS Code publishing (Wednesday, XXX XX) -- [ ] Update `main` after the next insider version is made available. - - [ ] Bump the version number to the next monthly ("YYYY.M.100") release in the `main` branch - - [ ] `package.json` - - [ ] `package-lock.json` - - [ ] Confirm the 3rd part of the version ends with `100`. - [ ] Go through [`info needed` issues](https://github.com/Microsoft/vscode-jupyter/issues?q=is%3Aopen+sort%3Aupdated-asc+label%3Ainfo-needed) and close any that have no activity for over a month (🤖) - [ ] GDPR bookkeeping (🤖) ((@greazer does regular classification every Monday evening)) - [ ] If any steps were unclear or changed in this release plan please update the `release_plan.md` file to make it clear for the next release