Commit 190d38d
committed
build(cli): pin SDK to dev integration branch, drop local-path replace
CI failures since Phase 1 (commit f86006c) traced to a local-path replace
directive that pointed at /Users/ysy/go/src/github.com/flashcatcloud/
flashduty-sdk — fine for the workstation that authored it, fatal for
GitHub Actions runners that have no such path.
The CLI legitimately depends on unreleased SDK methods (Phase 1's
CreateMCPServer + Phase 2's MonitQuery / MonitAgent). Until both
underlying SDK PRs (#12 mcp-server-create, #13 monit-types) merge and a
v0.10.0 tag ships, we pin to a pseudo-version of the integration branch
flashduty-sdk@dev/sdk-cli-phase2-deps (HEAD 3203385), which merges both
feature branches together. Resolves to:
v0.9.1-0.20260527160039-3203385df5ad
When SDK v0.10.0 tags, the next commit on this PR just bumps the require
to v0.10.0 and we delete the integration branch — no other CLI code
change needed. The replace directive does not return.1 parent a09fa2c commit 190d38d
2 files changed
Lines changed: 3 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2 | 2 | | |
3 | 3 | | |
4 | 4 | | |
5 | | - | |
6 | | - | |
7 | 5 | | |
8 | | - | |
| 6 | + | |
9 | 7 | | |
10 | 8 | | |
11 | 9 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | 3 | | |
| 4 | + | |
| 5 | + | |
4 | 6 | | |
5 | 7 | | |
6 | 8 | | |
| |||
0 commit comments