From df0dda965bd13c782e1765eb9778e41299fb68a4 Mon Sep 17 00:00:00 2001 From: Ira Hopkinson Date: Mon, 27 Feb 2023 13:10:49 +1300 Subject: [PATCH] Release v0.0.2 - this is a pre-release --- CHANGELOG.md | 18 ++++++++++++++++++ README.md | 4 ++-- release/app/package-lock.json | 4 ++-- release/app/package.json | 2 +- 4 files changed, 23 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 20d85328c5..053fa14332 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,21 @@ +# 0.0.2 (2023.2.28) + +## What's Changed + +### Other Changes + +- Update release instructions by @irahopkinson in https://github.com/paranext/paranext-core/pull/20 +- Added websocket communication between main and renderer, improved build process and dev experience by @tjcouch-sil in https://github.com/paranext/paranext-core/pull/24 +- Add Code Spell Checker by @irahopkinson in https://github.com/paranext/paranext-core/pull/33 +- Create C# client for handling requests for existing Paratext data. by @FoolRunning in https://github.com/paranext/paranext-core/pull/28 +- Run the dotnet Data Provider from electron by @irahopkinson in https://github.com/paranext/paranext-core/pull/36 + +## New Contributors + +- @FoolRunning made their first contribution in https://github.com/paranext/paranext-core/pull/28 + +**Full Changelog**: https://github.com/paranext/paranext-core/compare/v0.0.1...v0.0.2 + # 0.0.1 (2023.2.4) ## What's Changed diff --git a/README.md b/README.md index 762600a797..8682497efc 100644 --- a/README.md +++ b/README.md @@ -83,8 +83,8 @@ npm run package ## Publishing 1. Create a branch of the form `release/*`, e.g. `release/v1.2.3`, or `release/v1.2.3-rc1`. -2. Update the _version_ in your project's `package.json` file (e.g. _1.2.3_). -3. Run `npm i` to update `package-lock.json`. +2. Update the _version_ in your project's `release/app/package.json` file (e.g. _1.2.3_). +3. Run `npm i` in that folder to update it's `package-lock.json`. 4. Create a new draft [GitHub **Release**](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository), ensure the following are included: - a _Tag version_, e.g. `v1.2.3`, choose _Create new tag on publish_. - set the **Target** to the release branch. diff --git a/release/app/package-lock.json b/release/app/package-lock.json index 6029ebbe7f..06e3d2841d 100644 --- a/release/app/package-lock.json +++ b/release/app/package-lock.json @@ -1,12 +1,12 @@ { "name": "Paranext", - "version": "0.0.1", + "version": "0.0.2", "lockfileVersion": 2, "requires": true, "packages": { "": { "name": "Paranext", - "version": "0.0.1", + "version": "0.0.2", "hasInstallScript": true, "license": "MIT" } diff --git a/release/app/package.json b/release/app/package.json index 7ebb751ee6..512bf7bf6c 100644 --- a/release/app/package.json +++ b/release/app/package.json @@ -1,6 +1,6 @@ { "name": "Paranext", - "version": "0.0.1", + "version": "0.0.2", "description": "Extensible Bible translation software", "license": "MIT", "author": {