+27
-13
lines changedFilter options
+27
-13
lines changed Original file line number Diff line number Diff line change
@@ -1,5 +1,14 @@
1 1
# PowerShell Extension Release History
2 2 3 +
## v2025.1.0-preview
4 +
### Thursday, January 16, 2025
5 + 6 +
With PowerShell Editor Services [v4.2.0](https://github.com/PowerShell/PowerShellEditorServices/releases/tag/v4.2.0)!
7 + 8 +
VS Code engine update and snippet fix
9 + 10 +
See more details at the GitHub Release for [v2025.1.0-preview](https://github.com/PowerShell/vscode-powershell/releases/tag/v2025.1.0-preview).
11 + 3 12
## v2024.5.2-preview
4 13
### Wednesday, December 04, 2024
5 14
@@ -87,29 +87,34 @@ of Microsoft. Assume `origin` is GitHub and `ado` is Azure DevOps.
87 87
cd ./PowerShellEditorServices
88 88
git checkout -B release
89 89
./tools/updateVersion.ps1 -Version "4.0.0" -Changes "Major release!"
90 +
# Amend changelog as necessary
90 91
git push --force-with-lease origin
91 -
git push ado HEAD:main
92 - 92 +
# Open, approve, and merge PR on GitHub
93 93
cd ../vscode-powershell
94 94
git checkout -B release
95 95
./tools/updateVersion.ps1 -Version "2024.4.0" -Changes "Major release!"
96 +
# Amend changelog as necessary
96 97
git push --force-with-lease origin
97 -
git push ado HEAD:main
98 +
# Open, approve, and merge PR on GitHub
99 +
cd ../PowerShellEditorServices
100 +
git checkout main
101 +
git pull
102 +
git push ado HEAD:release
103 +
cd ../vscode-powershell
104 +
git checkout main
105 +
git pull
106 +
git push ado HEAD:release
107 +
# Download and test assets from draft GitHub Releases
108 +
# Publish releases, ensuring tag is at release commit in `main`
109 +
# Permit pipeline to publish to marketplace
98 110
```
99 111 100 -
1. Amend changelogs as necessary.
101 -
2. Push `release` branches to GitHub and to Azure DevOps `main` branch.
102 -
3. Download and test assets!
103 -
4. Publish draft releases and merge (don't squash!) branches.
104 -
5. Permit pipeline to publish to marketplace.
105 - 106 112
If rolling from pre-release to release, do not change the version of PowerShell
107 113
Editor Services between a pre-release and the subsequent release! We only
108 114
need to release the extension.
109 115 110 -
The Azure DevOps pipelines have to build off `main` branch for _reasons_,
111 -
but we still want to use PRs. Hence pushing `release` to `main` and then
112 -
merging (not squashing nor rebasing) those PRs so the commit stays the same.
116 +
The Azure DevOps pipelines have to build off a PR merged to `main` for _reasons_,
117 +
hence that repo is a superset including all our commits plus signed PR merge commits.
113 118 114 119
### Versioning
115 120
@@ -1,7 +1,7 @@
1 1
{
2 2
"name": "powershell",
3 3
"displayName": "PowerShell",
4 -
"version": "2024.5.2",
4 +
"version": "2025.1.0",
5 5
"preview": false,
6 6
"publisher": "ms-vscode",
7 7
"description": "Develop PowerShell modules, commands and scripts in Visual Studio Code!",
You can’t perform that action at this time.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4