Skip to content

New beta #174

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 27, 2021
Merged

New beta #174

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,10 +166,10 @@ In the future, we should consier showing the format errors when `.compiler.log`

Currently the release is vetted and done by @chenglou.

- Bump the version properly in `package.json` and `server/package.json` and their lockfiles and make a new commit.
- Make sure @ryyppy is aware of your changes. He needs to sync them over to the vim plugin.
- Download and unzip the 3 platforms' production binaries from the Github CI. Put them into `server/analysis_binaries`.
- Use `vsce publish` to publish. Official VSCode guide [here](https://code.visualstudio.com/api/working-with-extensions/publishing-extension). Only @chenglou has the publishing rights right now.
- Not done! Make a new manual release [here](https://github.com/rescript-lang/rescript-vscode/releases); use `vsce package` to package up a standalone `.vsix` plugin and attach it onto that new release. This is for folks who don't use the VSCode marketplace.
1. Bump the version properly in `package.json` and `server/package.json` and their lockfiles and make a new commit.
2. Make sure @ryyppy is aware of your changes. He needs to sync them over to the vim plugin.
3. Download and unzip the 3 platforms' production binaries from the Github CI. Put them into `server/analysis_binaries`.
4. Use `vsce publish` to publish. Official VSCode guide [here](https://code.visualstudio.com/api/working-with-extensions/publishing-extension). Only @chenglou has the publishing rights right now.
5. Not done! Make a new manual release [here](https://github.com/rescript-lang/rescript-vscode/releases); use `vsce package` to package up a standalone `.vsix` plugin and attach it onto that new release. This is for folks who don't use the VSCode marketplace.

For beta releases, we just do the last step and ask folks to try it.
For beta releases, skip step 4. Ask folks to try the `.vsix` directly.
5 changes: 3 additions & 2 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
"description": "The official VSCode plugin for ReScript.",
"author": "chenglou",
"license": "MIT",
"version": "1.0.8",
"version": "1.1.0-beta.2",
"repository": {
"type": "git",
"url": "https://github.com/rescript-lang/rescript-vscode"
Expand Down
5 changes: 3 additions & 2 deletions server/package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion server/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "rescript-language-server",
"description": "ReScript's language-server",
"version": "1.0.0",
"version": "1.1.0-beta.2",
"author": "chenglou",
"license": "MIT",
"engines": {
Expand Down