Skip to content

Repinned the server and api-go forks to the stream heads. - #5

Closed
moetemp wants to merge 1 commit into
moe/AI-198-ch-cli-1-channelfrom
moe/AI-198-st-cli-0-repin
Closed

moetemp wants to merge 1 commit into
moe/AI-198-ch-cli-1-channelfrom
moe/AI-198-st-cli-0-repin

Conversation

@moetemp

@moetemp moetemp commented Oct 3, 2026 •

Copy link
Copy Markdown
Owner

This PR moves the server and api pins from the channel heads to the stream heads.

What changed?

  • go.mod replaces go.temporal.io/server with github.com/moetemp/temporal at the top of the stream server chain.
  • go.mod replaces go.temporal.io/api with github.com/moetemp/api-go at the stream api head.

Part of AI-198 (epic AI-37).

Why?

Nothing here is a feature. The stream commands in the next PR need the stream protos and a server that serves the stream service in start-dev. Both heads sit on top of the channel heads, so the channel commands keep the server they were written against. Go, nexus and the sdk don't move.

How did you test it?

Link to a test plan if any -

  • Unit Tests
  • Staging
  • End to End Tests

go build ./... passes and go mod tidy leaves both modules as they are. The TestChannel unit tests and suite cases still pass on the new pins.

The stream commands need the stream protos in the api fork and a server that serves the stream
service. Both heads sit on the channel heads, so the channel commands keep working.
@moetemp

moetemp commented Oct 6, 2026

Copy link
Copy Markdown
Owner Author

Paused per the 2026-10-05 design review (the decision record is on the proposal page, section 14). Resumes in phase 2 with the CHASM notification work. The branch stays as a pin.

@moetemp moetemp closed this Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant