Skip to content

Prevent monitor status TCC prompts in Git-Same 3.2.0 #21

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

Open
manuelgruber wants to merge 10 commits into
base: main
Choose a base branch
from
Open

Prevent monitor status TCC prompts in Git-Same 3.2.0 #21

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
0a6e4f0
Mirror status.json to host dir to stop cross-app TCC prompts
manuelgruber Jun 27, 2026
8cc5621
Bump transitive deps in Cargo.lock to latest in-range patches
manuelgruber Jun 30, 2026
657c45d
Cap time at <0.3.52 so tauri's cookie 0.18.1 keeps compiling
manuelgruber Jul 1, 2026
f3f593f
Bump version to 3.2.0 across workspace, app, and badges for release
manuelgruber Jul 1, 2026
8f7bce5
Bump Cargo and pnpm dependencies to latest in-range versions
manuelgruber Jul 1, 2026
5f72649
Fix legacy status symlink errors to prevent container reads
manuelgruber Jul 2, 2026
83728f1
Harden status mirroring and fix review findings on TCC branch
manuelgruber Jul 7, 2026
4804d90
Guide users to restart the monitor after an upgrade when stale
manuelgruber Jul 9, 2026
d59f5f8
Stamp monitor build version in status so the app can flag skew
manuelgruber Jul 10, 2026
9edcf79
Auto-restart stale monitor on app launch to recover host status
manuelgruber Jul 10, 2026
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
108 changes: 55 additions & 53 deletions Cargo.lock
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 Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ members = [
resolver = "2"

[workspace.package]
version = "3.1.0"
version = "3.2.0"
edition = "2021"
authors = ["Manuel Gruber"]
license = "MIT"
Expand Down
4 changes: 4 additions & 0 deletions crates/git-same-app/Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,10 @@ serde = { workspace = true }
serde_json = { workspace = true }
shellexpand = { workspace = true }
tauri = { version = "2", features = [] }
# Pin: tauri's transitive `cookie` 0.18.1 calls time's Parsable::parse with the
# pre-0.3.52 one-arg signature; time 0.3.52 made it two-arg and fails to compile.
# No fixed cookie release exists yet. Remove this cap once cookie ships a fix.
time = ">=0.3, <0.3.52"

@cubic-dev-ai cubic-dev-ai Bot Jul 18, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3: The time version cap >=0.3, <0.3.52 is tighter than necessary and the rationale comment is slightly stale. time 0.3.53 (released 2026-07-01) already reverts the internal Parsable::parse breaking change from 0.3.52 to make the cookie crate compile again, so 0.3.53+ is now compatible. Consider relaxing the constraint to >=0.3, !=0.3.52 or updating the comment to note that time 0.3.53 already resolved the issue, and that the cap can be relaxed now rather than waiting for a cookie release.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At crates/git-same-app/Cargo.toml, line 30:

<comment>The `time` version cap `>=0.3, <0.3.52` is tighter than necessary and the rationale comment is slightly stale. `time` 0.3.53 (released 2026-07-01) already reverts the internal `Parsable::parse` breaking change from 0.3.52 to make the `cookie` crate compile again, so 0.3.53+ is now compatible. Consider relaxing the constraint to `>=0.3, !=0.3.52` or updating the comment to note that time 0.3.53 already resolved the issue, and that the cap can be relaxed now rather than waiting for a cookie release.</comment>

<file context>
@@ -24,6 +24,10 @@ serde = { workspace = true }
+# Pin: tauri's transitive `cookie` 0.18.1 calls time's Parsable::parse with the
+# pre-0.3.52 one-arg signature; time 0.3.52 made it two-arg and fails to compile.
+# No fixed cookie release exists yet. Remove this cap once cookie ships a fix.
+time = ">=0.3, <0.3.52"
 tauri-plugin-dialog = "2"
 tokio = { workspace = true }
</file context>
Suggested change
time = ">=0.3, <0.3.52"
time = ">=0.3, !=0.3.52"

tauri-plugin-dialog = "2"
tokio = { workspace = true }
toml = { workspace = true }
Loading