Closed
Description
Release candidate (Nov 3, 2023)
- Announce the release, leave enough time for teams to surface any last minute issues that need to get in before freeze. Make sure debugger and gopls teams are looped in as well.
- Check the milestone and resolve/move unresolved issues.
- Update
master
for the release- Update hardcoded latest version for
gopls
. - Update
CHANGELOG.md
. - Make sure the "Thanks" section is up-to-date.
- Check the Markdown rendering to make sure everything looks good.
- Update hardcoded latest version for
- Update
release
for the release- Create a branch against
release
for a pull request. - Merge changes from
master
to prepare for the release. - Change the version in
package.json
from a-dev
suffix - Run
npm install
to make surepackage-lock.json
is up-to-date - Update the license file (
$ tools/license.sh; mv LICENSE.prod LICENSE
)
- Create a branch against
- Check the Long Tests status is green. Otherwise, fix the tests, send cls for review, submit them, and repeat.
- Perform manual smoke tests
- Create new RC version tag for v0.36.0-rc.1 at gerrit’s vscode-go repo management page
- Go to the release page https://github.com/golang/vscode-go/releases and check if the new release candidate is up. If necessary, you can manually edit the comment by clicking the “Edit” button. Don’t mutate uploaded vsix.
- Ask @golang/tools-team and contributors to this release to test the release candidate
Final (Nov 7, 2023)
- Tag the new release for v0.36.0
- Update the release description with CHANGELOG contents
- Close the milestone
Prepare for the Next Release
- Update
master
post-release- Bump the
version
number to the next monthly release in themaster
branch- Update
package.json
- Update
package-lock.json
- Update
- Bump the