gitbutlerapp/gitbutler
1
1
Fork 0
mirror of https://github.com/gitbutlerapp/gitbutler.git synced 2024-11-25 07:45:41 +03:00
Code Issues Packages Projects Releases Wiki Activity
6aaf2d89ec
gitbutler/Cargo.toml

97 lines
3.7 KiB
TOML
Raw Normal View History

new structure
2023-09-06 11:46:07 +03:00
[workspace]
members = [
update config to refer to new crate structure
2024-04-04 12:56:56 +03:00
"crates/gitbutler-tauri",
"crates/gitbutler-git",
add `watcher` crate with code copied from `gitbutler-tauri/src/watcher`. It's not functional yet, but exactly at the spot where it needs fixing across the boundary that is: - a stand-in for application events - analytics
2024-04-17 20:11:24 +03:00
"crates/gitbutler-watcher",
move debouncer code into its own crate That way the public API that isn't used doesn't have to be `dead_code`. Also adjust CI to run the tests we have in the debouncer crate. Previously, it might not have run them though.
2024-06-02 16:14:47 +03:00
"crates/gitbutler-watcher/vendor/debouncer",
Add a new `testsupport` crate that contains `core/tests/shared`. It's code shared by multiple crates, and should be reusable by means of a crate.
2024-04-06 11:03:07 +03:00
"crates/gitbutler-testsupport",
Split branch creation and deletion into their own home
2024-07-09 17:43:58 +03:00
"crates/gitbutler-cli",
rename gitbutler-virtual to gitbutler-branch-actions This is to establish a patter of which crates represent a higher level logic
2024-07-10 15:49:48 +03:00
"crates/gitbutler-branch-actions",
move cloud sync functionality to its own crate
2024-07-07 20:22:41 +03:00
"crates/gitbutler-sync",
Split branch creation and deletion into their own home
2024-07-09 17:43:58 +03:00
"crates/gitbutler-oplog",
move rebase module to a new repo crate
2024-07-08 01:27:17 +03:00
"crates/gitbutler-repo",
Split branch creation and deletion into their own home
2024-07-09 17:43:58 +03:00
"crates/gitbutler-command-context",
"crates/gitbutler-feedback",
move config module to a separate gitbutler-config crate
2024-07-08 15:49:45 +03:00
"crates/gitbutler-config",
move project module in a separate gitbutler-project crate
2024-07-08 16:33:26 +03:00
"crates/gitbutler-project",
Split branch creation and deletion into their own home
2024-07-09 17:43:58 +03:00
"crates/gitbutler-user",
move branch related modules to separate crate Unfortunatelly diff and branch types form a cyclical dependency via the "HunkLock" type. This will have to be refactored as a followup
2024-07-09 01:10:55 +03:00
"crates/gitbutler-branch",
move reference module from core to its own crate
2024-07-09 02:14:28 +03:00
"crates/gitbutler-reference",
move error module to it's own crate
2024-07-09 12:13:39 +03:00
"crates/gitbutler-error",
Split branch creation and deletion into their own home
2024-07-09 17:43:58 +03:00
"crates/gitbutler-serde",
"crates/gitbutler-secret",
"crates/gitbutler-id",
"crates/gitbutler-storage",
move fs and storage intor separate crates
2024-07-09 13:54:08 +03:00
"crates/gitbutler-fs",
Split branch creation and deletion into their own home
2024-07-09 17:43:58 +03:00
"crates/gitbutler-time",
"crates/gitbutler-commit",
"crates/gitbutler-tagged-string",
Introduce operating modes
2024-07-29 14:19:38 +03:00
"crates/gitbutler-url",
move hunk and diff code to a separate crate, out of the branch one
2024-07-17 21:16:48 +03:00
"crates/gitbutler-diff",
Introduce operating modes
2024-07-29 14:19:38 +03:00
"crates/gitbutler-operating-modes",
Add edit mode actions More edit mode
2024-08-19 12:03:51 +03:00
"crates/gitbutler-edit-mode",
Somethign somethign matchy matchy design
2024-08-26 20:23:15 +03:00
"crates/gitbutler-cherry-pick",
new structure
2023-09-06 11:46:07 +03:00
]
pin resolver version on workspace level to have deterministic build behaviour
2023-10-13 11:52:44 +03:00
resolver = "2"
new structure
2023-09-06 11:46:07 +03:00
add gitbutler-core package and move IDs to it
2023-12-28 16:53:29 +03:00
[workspace.dependencies]
Revert "remove unnecessary BString-related serde functions." This reverts commit 3043f099b79d796ad1cc892035f1cdd01936269c. We actually need this - me removing it just means it wasn't properly documented and clarified in the type-system as to why this is needed.
2024-08-09 11:37:23 +03:00
bstr = "1.10.0"
Prevent MacOS popups each startup on MacOS MacOS is the only known platform that exhibits this behaviour - if an app is recompiled, the hash of the binary is used to identify it towards the keychain. As this changes each time, the keychain will ask for permission, which is fair. However, it's also an impediment which leads to the implementation of a keystore that uses git credentials as backend. For this to work, the latest version of `gitoxide` is required for now.
2024-06-25 22:42:04 +03:00
# Add the `tracing` or `tracing-detail` features to see more of gitoxide in the logs. Useful to see which programs it invokes.
Use the latest version of `gix` for performance improvements.
2024-08-27 12:16:09 +03:00
gix = { git = "https://github.com/Byron/gitoxide", rev = "0fe5133598c6f843fb3172a4e0c4f58932405647", default-features = false, features = [] }
Split branch creation and deletion into their own home
2024-07-09 17:43:58 +03:00
git2 = { version = "0.18.3", features = [
"vendored-openssl",
"vendored-libgit2",
] }
chore(app): move library-portion to top-level `src/` folder. This allows the tauri-specific parts to remain in the `app` crate, which will help to eventually release a `cli` crate as well.
2024-03-29 12:04:26 +03:00
uuid = { version = "1.8.0", features = ["serde"] }
add gitbutler-core package and move IDs to it
2023-12-28 16:53:29 +03:00
serde = { version = "1.0", features = ["derive"] }
Bump the rust-updates group across 1 directory with 8 updates Bumps the rust-updates group with 8 updates in the / directory: | Package | From | To | | --- | --- | --- | | [thiserror](https://github.com/dtolnay/thiserror) | `1.0.62` | `1.0.63` | | [tokio](https://github.com/tokio-rs/tokio) | `1.38.0` | `1.39.2` | | [console-subscriber](https://github.com/tokio-rs/console) | `0.3.0` | `0.4.0` | | [serde_json](https://github.com/serde-rs/json) | `1.0.120` | `1.0.121` | | [assert_cmd](https://github.com/assert-rs/assert_cmd) | `2.0.14` | `2.0.15` | | [clap](https://github.com/clap-rs/clap) | `4.5.9` | `4.5.13` | | [bstr](https://github.com/BurntSushi/bstr) | `1.9.1` | `1.10.0` | | [toml](https://github.com/toml-rs/toml) | `0.8.14` | `0.8.15` | Updates `thiserror` from 1.0.62 to 1.0.63 - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](https://github.com/dtolnay/thiserror/compare/1.0.62...1.0.63) Updates `tokio` from 1.38.0 to 1.39.2 - [Release notes](https://github.com/tokio-rs/tokio/releases) - [Commits](https://github.com/tokio-rs/tokio/compare/tokio-1.38.0...tokio-1.39.2) Updates `console-subscriber` from 0.3.0 to 0.4.0 - [Release notes](https://github.com/tokio-rs/console/releases) - [Changelog](https://github.com/tokio-rs/console/blob/main/release-plz.toml) - [Commits](https://github.com/tokio-rs/console/compare/console-subscriber-v0.3.0...console-subscriber-v0.4.0) Updates `serde_json` from 1.0.120 to 1.0.121 - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.120...v1.0.121) Updates `assert_cmd` from 2.0.14 to 2.0.15 - [Changelog](https://github.com/assert-rs/assert_cmd/blob/master/CHANGELOG.md) - [Commits](https://github.com/assert-rs/assert_cmd/compare/v2.0.14...v2.0.15) Updates `clap` from 4.5.9 to 4.5.13 - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/clap_complete-v4.5.9...v4.5.13) Updates `bstr` from 1.9.1 to 1.10.0 - [Commits](https://github.com/BurntSushi/bstr/compare/1.9.1...1.10.0) Updates `toml` from 0.8.14 to 0.8.15 - [Commits](https://github.com/toml-rs/toml/compare/toml-v0.8.14...toml-v0.8.15) --- updated-dependencies: - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-updates - dependency-name: tokio dependency-type: direct:production update-type: version-update:semver-minor dependency-group: rust-updates - dependency-name: console-subscriber dependency-type: direct:production update-type: version-update:semver-minor dependency-group: rust-updates - dependency-name: serde_json dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-updates - dependency-name: assert_cmd dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-updates - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-updates - dependency-name: bstr dependency-type: direct:production update-type: version-update:semver-minor dependency-group: rust-updates - dependency-name: toml dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-updates ... Signed-off-by: dependabot[bot] <support@github.com>
2024-08-01 22:45:06 +03:00
thiserror = "1.0.63"
Bump the rust-updates group with 3 updates Bumps the rust-updates group with 3 updates: [tokio](https://github.com/tokio-rs/tokio), [sysinfo](https://github.com/GuillaumeGomez/sysinfo) and [rstest](https://github.com/la10736/rstest). Updates `tokio` from 1.39.3 to 1.40.0 - [Release notes](https://github.com/tokio-rs/tokio/releases) - [Commits](https://github.com/tokio-rs/tokio/compare/tokio-1.39.3...tokio-1.40.0) Updates `sysinfo` from 0.31.3 to 0.31.4 - [Changelog](https://github.com/GuillaumeGomez/sysinfo/blob/master/CHANGELOG.md) - [Commits](https://github.com/GuillaumeGomez/sysinfo/compare/v0.31.3...v0.31.4) Updates `rstest` from 0.21.0 to 0.22.0 - [Release notes](https://github.com/la10736/rstest/releases) - [Changelog](https://github.com/la10736/rstest/blob/master/CHANGELOG.md) - [Commits](https://github.com/la10736/rstest/compare/v0.21.0...v0.22.0) --- updated-dependencies: - dependency-name: tokio dependency-type: direct:production update-type: version-update:semver-minor dependency-group: rust-updates - dependency-name: sysinfo dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-updates - dependency-name: rstest dependency-type: direct:production update-type: version-update:semver-minor dependency-group: rust-updates ... Signed-off-by: dependabot[bot] <support@github.com>
2024-09-01 18:57:33 +03:00
tokio = { version = "1.40.0", default-features = false }
auto-migrate secrets from user.json to their location in the keyring This will also remove them from their plain-text location. Further, when the secrets are required they will be obtained specifically, instead of always having them at hand. The frontend doesn't ever show these, but needs them, and it now asks for them when it needs them.
2024-06-24 18:18:33 +03:00
keyring = "2.3.3"
Split branch creation and deletion into their own home
2024-07-09 17:43:58 +03:00
anyhow = "1.0.86"
enforce in-process-synchronization during worktree updates and prolonged reads in `oplog` That way it's assured that reads and writes don't intersect, but assure we only hold such lock for the shortest amount of time for reads and and for the full duration of writes.
2024-07-14 22:51:28 +03:00
fslock = "0.2.1"
parking_lot = "0.12.3"
add ability to create add projects in CLI and create vbranches This allows actual GitButler setups and more complex tests, which are also added here.
2024-07-27 20:15:02 +03:00
futures = "0.3.30"
Introduce edit mode asdf
2024-08-07 16:17:58 +03:00
toml = "0.8.13"
add `--trace` to enable tracing This is useful to get simple performance metrics.
2024-08-11 15:55:00 +03:00
tracing = "0.1.40"
tracing-subscriber = "0.3.17"
add gitbutler-core package and move IDs to it
2023-12-28 16:53:29 +03:00
Split branch creation and deletion into their own home
2024-07-09 17:43:58 +03:00
gitbutler-id = { path = "crates/gitbutler-id" }
update config to refer to new crate structure
2024-04-04 12:56:56 +03:00
gitbutler-git = { path = "crates/gitbutler-git" }
reintegrate `watcher` crate into `tauri` crate
2024-04-17 22:46:40 +03:00
gitbutler-watcher = { path = "crates/gitbutler-watcher" }
use workspace dependencies for workspace crates
2024-04-10 14:06:49 +03:00
gitbutler-testsupport = { path = "crates/gitbutler-testsupport" }
Split branch creation and deletion into their own home
2024-07-09 17:43:58 +03:00
gitbutler-cli = { path = "crates/gitbutler-cli" }
rename gitbutler-virtual to gitbutler-branch-actions This is to establish a patter of which crates represent a higher level logic
2024-07-10 15:49:48 +03:00
gitbutler-branch-actions = { path = "crates/gitbutler-branch-actions" }
move cloud sync functionality to its own crate
2024-07-07 20:22:41 +03:00
gitbutler-sync = { path = "crates/gitbutler-sync" }
move oplog to its own crate This protects us from cyclic dependencies. Unfortunatelly as part of this, i had to introduce the imp Project as trait implementations since now Project is foreign
2024-07-07 21:00:01 +03:00
gitbutler-oplog = { path = "crates/gitbutler-oplog" }
move rebase module to a new repo crate
2024-07-08 01:27:17 +03:00
gitbutler-repo = { path = "crates/gitbutler-repo" }
move ProjectRepo into its own crate This type currently acts more or less like a command context that lives for the duration of the request. Regardless of if we wanna keep this pattern or not, separating it out helps us split up core
2024-07-08 14:23:03 +03:00
gitbutler-command-context = { path = "crates/gitbutler-command-context" }
separate sending zipped logs functionality into gitbutler-feedback crate
2024-07-08 14:52:22 +03:00
gitbutler-feedback = { path = "crates/gitbutler-feedback" }
move config module to a separate gitbutler-config crate
2024-07-08 15:49:45 +03:00
gitbutler-config = { path = "crates/gitbutler-config" }
move project module in a separate gitbutler-project crate
2024-07-08 16:33:26 +03:00
gitbutler-project = { path = "crates/gitbutler-project" }
extract user as its own crate out of core
2024-07-08 19:58:29 +03:00
gitbutler-user = { path = "crates/gitbutler-user" }
move branch related modules to separate crate Unfortunatelly diff and branch types form a cyclical dependency via the "HunkLock" type. This will have to be refactored as a followup
2024-07-09 01:10:55 +03:00
gitbutler-branch = { path = "crates/gitbutler-branch" }
move reference module from core to its own crate
2024-07-09 02:14:28 +03:00
gitbutler-reference = { path = "crates/gitbutler-reference" }
move error module to it's own crate
2024-07-09 12:13:39 +03:00
gitbutler-error = { path = "crates/gitbutler-error" }
move serde functions into their own crate
2024-07-09 12:49:12 +03:00
gitbutler-serde = { path = "crates/gitbutler-serde" }
move secret module out of core into own crate
2024-07-09 13:11:12 +03:00
gitbutler-secret = { path = "crates/gitbutler-secret" }
move fs and storage intor separate crates
2024-07-09 13:54:08 +03:00
gitbutler-storage = { path = "crates/gitbutler-storage" }
gitbutler-fs = { path = "crates/gitbutler-fs" }
move time module to it's own crate
2024-07-09 14:08:12 +03:00
gitbutler-time = { path = "crates/gitbutler-time" }
extract commit crate out of core
2024-07-09 14:19:49 +03:00
gitbutler-commit = { path = "crates/gitbutler-commit" }
extract tagged string to its own crate
2024-07-09 15:57:43 +03:00
gitbutler-tagged-string = { path = "crates/gitbutler-tagged-string" }
move url module to a separate crate this code is awful - lets nuke it asap
2024-07-09 16:29:24 +03:00
gitbutler-url = { path = "crates/gitbutler-url" }
move hunk and diff code to a separate crate, out of the branch one
2024-07-17 21:16:48 +03:00
gitbutler-diff = { path = "crates/gitbutler-diff" }
Introduce operating modes
2024-07-29 14:19:38 +03:00
gitbutler-operating-modes = { path = "crates/gitbutler-operating-modes" }
Add edit mode actions More edit mode
2024-08-19 12:03:51 +03:00
gitbutler-edit-mode = { path = "crates/gitbutler-edit-mode" }
Somethign somethign matchy matchy design
2024-08-26 20:23:15 +03:00
gitbutler-cherry-pick = { path = "crates/gitbutler-cherry-pick" }
update config to refer to new crate structure
2024-04-04 12:56:56 +03:00
new structure
2023-09-06 11:46:07 +03:00
[profile.release]
codegen-units = 1 # Compile crates one after another so the compiler can optimize better
lto = true # Enables link to optimizations
opt-level = "s" # Optimize for binary size
remove sentry rust dependencies
2024-04-29 16:54:13 +03:00
debug = true # Enable debug symbols, for profiling
Allow the `bench` profile to compile faster There we don't necessarily need every last bit of optimization like one would want in release profiles, but build performance is of the essence for developer productivity.
2024-08-28 09:36:53 +03:00
[profile.bench]
codegen-units = 256
lto = false
opt-level = 3
Reference in New Issue Copy Permalink