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
If you encounter serious security risks, please refrain from posting these publicly in the issue tracker.
138
139
We could minimize the impact by first patching the issue, publishing the patch, and then (after 30 days) disclose the bug.
139
140
So please first send an e-mail to joep@ontola.io describing the issue, and then we will work on fixing it as soon as possible.
140
141
141
142
## Releases, Versioning and Tagging
142
143
143
-
- We use Github Actions for building, testing and creating releases.
144
-
- Use `cargo workspaces version patch --force *` (and maybe replace `patch` with the `minor`) to update all `cargo.toml` files in one command. You'll need to `cargo install cargo-workspaces` if this command is not possible.
145
-
- Update the `tauri.conf.json` manually
146
-
- Push the `v*` tag, a Release will automatically be created on Github with the binaries. This will read `CHANGELOG.md`, so make sure to add the changes from there.
147
-
- The main action required on this repo, is to _update the changelog_ and _tag releases_. The tags trigger the build and publish processes in the CI.
148
-
- We use [semver](https://semver.org/), and are still quite far from 1.0.0.
149
-
- The version for `atomic-lib` is the most important, and dictates the versions of `cli` and `server`. When `lib` changes minor version, `cli` and `server` should follow.
150
-
- After publishing, update the `./desktop/latest-version.json` file. This is used for auto-updating desktop distributions. See [tauri docs](https://tauri.studio/docs/distribution/updater).
144
+
1. Update the `tauri.conf.json` manually to the new version.
145
+
2. Commit changes
146
+
3. Make sure all tests run properly
147
+
4. Use `cargo workspaces version patch` (and maybe replace `patch` with the `minor`) to update all `cargo.toml` files in one command. You'll need to `cargo install cargo-workspaces` if this command is not possible.
148
+
149
+
The following should be triggered automatically:
150
+
151
+
- Push the `v*` tag, a Release will automatically be created on Github with the binaries. This will read `CHANGELOG.md`, so make sure to add the changes from there.
152
+
- The main action required on this repo, is to _update the changelog_ and _tag releases_. The tags trigger the build and publish processes in the CI.
153
+
154
+
Note:
155
+
156
+
- We use [semver](https://semver.org/), and are still quite far from 1.0.0.
157
+
- The version for `atomic-lib` is the most important, and dictates the versions of `cli` and `server`. When `lib` changes minor version, `cli` and `server` should follow.
158
+
- After publishing, update the `./desktop/latest-version.json` file. This is used for auto-updating desktop distributions. See [tauri docs](https://tauri.studio/docs/distribution/updater).
0 commit comments