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
Copy file name to clipboardExpand all lines: CONTRIBUTE.md
+3-6Lines changed: 3 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -199,9 +199,8 @@ So please first send an e-mail to [email protected] describing the issue, and then
199
199
## Releases, Versioning and Tagging
200
200
201
201
1. Commit changes
202
-
2. Update the `tauri.conf.json` manually to the new version.
203
-
3. Make sure all tests run properly
204
-
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.
202
+
1. Make sure all tests run properly
203
+
1. 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.
205
204
206
205
The following should be triggered automatically:
207
206
@@ -212,7 +211,6 @@ Note:
212
211
213
212
- We use [semver](https://semver.org/), and are still quite far from 1.0.0.
214
213
- 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.
215
-
- 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).
216
214
217
215
### CI situation
218
216
@@ -226,8 +224,7 @@ If the CI scripts for some reason do not do their job (buildin releases, docker
226
224
#### Building and publishing binaries
227
225
228
226
1.`cargo build --release`
229
-
2.`cargo tauri build` (on every OS!)
230
-
3. Create a release on github, add the binaries and tauri builds
Copy file name to clipboardExpand all lines: desktop/README.md
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,7 @@
1
1
# Atomic-Server Desktop (powered by Tauri)
2
2
3
+
[_WARNING: THIS SUB-PROJECT IS NOT ACTIVELY MAINTAINED_](https://github.com/atomicdata-dev/atomic-server/issues/718)
4
+
3
5
Desktop release for Atomic-Server.
4
6
[Tauri] takes care of native installers, app icons, system tray icons, menu items, self-update ([issue](https://github.com/atomicdata-dev/atomic-server/issues/158)) and more.
5
7
@@ -20,5 +22,5 @@ If you only want to work on the _server side_ of things, you can remove `devPath
20
22
21
23
## Limitations
22
24
23
-
- No way to pass flags to `atomic-sever` using the Tauri executable (although you can set ENV varibles)
25
+
- No way to pass flags to `atomic-sever` using the Tauri executable (although you can set ENV variables)
0 commit comments