You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the process of releasing a new version of Langium is done manually one package after another. It requires to carefully update versions and dependencies. Proposals for automation of parts of this process are welcome.
104
+
105
+
1. Prepare the workspace
106
+
* Pull the latest changes
107
+
*`npm install`
108
+
*`npm test`
109
+
2.`packages/langium`
110
+
* Update version in `package.json`
111
+
*`npm run publish:latest`
112
+
3.`packages/langium-cli`
113
+
* Update version in `package.json`
114
+
* Update dependency to `langium` with `~` as version prefix (include bugfix versions)
115
+
*`npm run publish:latest`
116
+
4.`packages/langium-sprotty`
117
+
* Update version in `package.json`
118
+
* Update dependency to `langium` with `~` as version prefix
119
+
*`npm run publish:latest`
120
+
5.`packages/generator-langium`
121
+
* Update version in `package.json`
122
+
* Update dependency to `langium` and dev-dependency to `langium-cli` in `langium-template/package.json` with `^` as version prefix (include minor and bugfix versions)
123
+
*`npm run publish:latest`
124
+
6.`packages/langium-vscode`
125
+
* Update version in `package.json`
126
+
* Update dependency to `langium`
127
+
*`npm install -g vsce`
128
+
*`vsce publish -p <token> --yarn` (the last argument is due to an npm bug)
129
+
*`npm i -g ovsx`
130
+
*`ovsx publish -p <token> --yarn`
131
+
7.`examples/*`
132
+
* Update dependency to `langium` and dev-dependency to `langium-cli`
133
+
8.`npm install` again in the repository root to update `package-lock.json`
134
+
9. Commit, tag and push your changes
135
+
10. Close the corresponding GitHub milestone
136
+
137
+
In order to publish `next` versions from the current state of the `main` branch, use `npm run publish:next`, and don't update the `version` numbers manually as this is done by the npm script.
138
+
The changes must not be committed to the repository after publishing a `next` version.
139
+
Usually we don't publish `next` versions for the VS Code extension, only for the npm packages.
0 commit comments