chore: retarget IsanAgent to git main after oneshot merge - #223
Conversation
![amazon-q-developer[bot]](https://avatars.githubusercontent.com/in/1220912?s=60&v=4){kind=small}
There was a problem hiding this comment.
This PR successfully retargets the IsanAgent dependency from the temporary local path to the upstream git repository after isanagent#101 was merged to main. The dependency migration is implemented correctly across all Cargo.toml files, documentation has been updated consistently to reflect the change, and the Cargo.lock reflects the expected dependency source changes. The approach follows standard Rust dependency management practices and maintains reproducibility through the lockfile.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
Drop the temporary tools/isanagent-oneshot path pin now that altaidevorg/isanagent#101 landed on main (ea90fa0), and restore the branch-tracked git dependency used by isanagent:sync / CI. Co-authored-by: Cursor <cursoragent@cursor.com>
1207587 to
7336c3b
Compare
1 participant
Summary
isanagentdeps fromtools/isanagent-oneshotback togit = …/isanagent.git,branch = mainnow that isanagent#101 (ea90fa0) is on upstream main.pnpm isanagent:sync/ CIcargo update -p isanagentagainst the lockfile tip.Test plan
cargo test -p altai-core -p altai-cli(56 tests)cargo check -p altai --libcargo update -p isanagentsucceeds against git mainMade with Cursor