Skip to content

[Brook K1] Added the crate skeleton, the Stream protos and CI. - #43

Closed
moetemp wants to merge 1 commit into
moe/brook/review/basefrom
moe/brook/review/k1-skeleton
Closed

moetemp wants to merge 1 commit into
moe/brook/review/basefrom
moe/brook/review/k1-skeleton

Conversation

@moetemp

@moetemp moetemp commented Oct 25, 2026 •

Copy link
Copy Markdown
Owner

What changed?

This PR adds the temporalio-streams crate skeleton, the Stream protos and CI.

  • The three Stream protos are byte for byte A1's files (temporalio/api#895). Their enums build here.
  • The crate builds on temporalio-common 1.1 from crates.io, with no git dependency on Core.
  • fips turns on the FIPS mode of aws-lc-rs, and CI fails when ring is in that build.

Depends on nothing. Review lane is the proto and WIT reviewers.
Part of the Brook review series.

Why?

The protos are the contract with every SDK, so they're first and alone. The crate needs nothing
unreleased from Core, so we can publish it on crates.io after review (KR).

How did you test it?

cargo fmt, clippy (both feature sets), cargo test and the FIPS tree check. Fork CI passes.

Link to a test plan if any -

  • Unit Tests
  • Staging
  • End to End Tests

The crate builds on `temporalio-common` 1.1 from crates.io and
generates only the Stream service and runtime protos. CI runs lint,
the tests and the FIPS dependency check.
@moetemp
moetemp force-pushed the moe/brook/review/k1-skeleton branch from 6c8ca5c to d81d3c6 Compare October 26, 2026 08:00
@moetemp

moetemp commented Oct 27, 2026

Copy link
Copy Markdown
Owner Author

Moved to moetemp/sdk-rust#212 (K1). The crate split in two. The shared runtime is now the crate temporalio-streams in sdk-rust (moetemp/sdk-rust#212 to #220), and the Redis Store is temporalio-streams-redis in temporal-community/sdk-streams (#1 to #3).

@moetemp moetemp closed this Oct 27, 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