g1t/services/repos/Cargo.toml

27 lines724 bytesCodeBlame

Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.

Rust repos service with shipping; pull requests kept in the model1[package]
2name = "g1t-repos"
3version = "0.1.0"
4edition.workspace = true
5license.workspace = true
6description = "Repository registry, contents, forks, landing and git over HTTPS."
7
8[lib]
9crate-type = ["cdylib"]
10
11[dependencies]
12g1t-contracts.workspace = true
13g1t-kit.workspace = true
Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API14g1t-scan.workspace = true
Mission control shows where you are needed and what agents landed without you; git answers in about 200ms15g1t-secrets.workspace = true
Rust repos service with shipping; pull requests kept in the model16serde.workspace = true
17serde_json.workspace = true
18worker.workspace = true
Agents as a team: lifecycle, merge queue, billing and a new shell19futures-util = { version = "0.3", default-features = false, features = ["alloc"] }
Diffs on attempts; hosted agent presented as the g1t agent20similar = "2"
Fast pages, required checks on the branch, self-hosted runners, honest incidents21miniz_oxide = "0.9"
Composer from the workspace's own repositories, and go get from g1t.sh22base64 = "0.22"
Deploys as code: a manifest of every Worker, a deploy tool that ships only what changed in parallel stages, and a g1t Actions workflow23
24# wasm-opt at -O1: about the same gzipped size as -O in a tenth of the
25# time (docs/DEPLOYING.md, "Build speed").
26[package.metadata.wasm-pack.profile.release]
27wasm-opt = ["-O1"]