diff --git a/CHANGELOG.md b/CHANGELOG.md index a83bf75b..176b50a8 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -14,6 +14,12 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), ## Security +## [0.1.2] + +### Added + +- VS Code version 1.40.1. + ## [0.1.1] ### Fixed diff --git a/docs/dev/Release.md b/docs/dev/Release.md index 04e57d8c..a6d0b0b6 100644 --- a/docs/dev/Release.md +++ b/docs/dev/Release.md @@ -1,4 +1,3 @@ - # Releases Version number format follows [Semantic Versioning](https://semver.org/) of ... @@ -24,10 +23,7 @@ Follow these steps to publish a new release to the [Visual Studio Marketplace](h Include the following checklist in the PR description when creating a new release. ```markdown -Release Checklist: - - [ ] Update version number - - [ ] Update [CHANGELOG.md](./CHANGELOG.md) - - [ ] Link to PR for the release blog post (if any) +Release Checklist: - [ ] Update version number - [ ] Update [CHANGELOG.md](./CHANGELOG.md) - [ ] Link to PR for the release blog post (if any) ``` Note: Ensure all checklist items are completed before merging the release PR. @@ -47,6 +43,14 @@ To publish a **patch** release: IMPORTANT: You do not need to merge the patch branch back into `main` as it is a temporary branch. However, you will need to update the version number in the `main` branch after the patch release is published. +## Rollback + +In case of a critical issue with the latest release, a rollback may be necessary. The new release should be published as soon as possible to replace the faulty release. + +However, rolling back a release is not a straightforward process. It requires a new release with a fix for the issue and a new version number, while the main Cody repository tag should be updated to the previous version. + +The rest of the release process remains the same as for a patch release. + ## Nightly build Nightly build is currently not supported. @@ -61,4 +65,4 @@ To do this: 2. Run `cd src; dotnet cake`. 3. Open the [src/Cody.sln](src/Cody.sln) file in Visual Studio. 4. Right click on the [Cody.Visual Studio](src/Cody.VisualStudio/) project and select `Rebuild Project`. -5. Once the project is built, it will create a `Cody.VisualStudio.vsix` file in the `src/Cody.VisualStudio/bin/Debug` folder, which you can double-click to install the extension. \ No newline at end of file +5. Once the project is built, it will create a `Cody.VisualStudio.vsix` file in the `src/Cody.VisualStudio/bin/Debug` folder, which you can double-click to install the extension. diff --git a/src/Cody.VisualStudio/source.extension.vsixmanifest b/src/Cody.VisualStudio/source.extension.vsixmanifest index 7feb560c..36af98d2 100644 --- a/src/Cody.VisualStudio/source.extension.vsixmanifest +++ b/src/Cody.VisualStudio/source.extension.vsixmanifest @@ -1,7 +1,7 @@ - + Cody for Visual Studio - AI Coding Assistant AI coding assistant that uses search and codebase context to help you write code faster! https://sourcegraph.com/cody diff --git a/src/build.cake b/src/build.cake index ec4524b8..fc9df8ba 100644 --- a/src/build.cake +++ b/src/build.cake @@ -46,7 +46,7 @@ var nodeBinaryUrl = "https://github.com/sourcegraph/node-binaries/raw/main/v20.1 var nodeArmBinaryUrl = "https://github.com/sourcegraph/node-binaries/raw/main/v20.12.2/node-win-arm64.exe"; // The latest tag of the stable release from the cody repository https://github.com/sourcegraph/cody/tags -var codyStableReleaseTag = "vscode-v1.38.3"; +var codyStableReleaseTag = "vscode-v1.40.1"; var codyBranch = Argument("cody-branch", codyStableReleaseTag); var marketplaceToken = EnvironmentVariable("CODY_VS_MARKETPLACE_RELEASE_TOKEN");