Skip to content

RSCBC-257: Update publish workflow to use cargo release#453

Open
chvck wants to merge 1 commit intomainfrom
rscbc257
Open

RSCBC-257: Update publish workflow to use cargo release#453
chvck wants to merge 1 commit intomainfrom
rscbc257

Conversation

@chvck
Copy link
Collaborator

@chvck chvck commented Mar 3, 2026

No description provided.

@chvck chvck requested a review from Copilot March 3, 2026 12:00
@chvck chvck marked this pull request as draft March 3, 2026 12:00
@chvck
Copy link
Collaborator Author

chvck commented Mar 3, 2026

Marking draft as requires repo level changes that need to be made first.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the tag-based crates.io publishing pipeline to use cargo-release across the workspace, with CI running the integration test workflow before attempting publication.

Changes:

  • Add release.toml to configure cargo-release (including excluding protostellar from publishing).
  • Update publish.yml to run tests via a reusable workflow, then perform a cargo-release dry run followed by an execute publish step.
  • Update tests.yml to support being invoked as a reusable workflow (workflow_call) and stop triggering on tag pushes directly.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File Description
release.toml Introduces cargo-release configuration for workspace publishing and package exclusion.
.github/workflows/tests.yml Makes the tests workflow callable from other workflows.
.github/workflows/publish.yml Replaces manual cargo publish -p ... steps with cargo-release dry-run + publish gated by tests.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@github-actions
Copy link

github-actions bot commented Mar 3, 2026

🐰 Bencher Report

Branchrscbc257-22622036216-104-1
Testbedubuntu-latest
Click to view all benchmark results
BenchmarkLatencyBenchmark Result
microseconds (µs)
(Result Δ%)
Upper Boundary
microseconds (µs)
(Limit %)
query📈 view plot
🚷 view threshold
440.53 µs
(+6.82%)Baseline: 412.39 µs
474.25 µs
(92.89%)
upsert_and_get📈 view plot
🚷 view threshold
445.75 µs
(+12.38%)Baseline: 396.66 µs
456.16 µs
(97.72%)
🐰 View full continuous benchmarking report in Bencher

@chvck chvck force-pushed the rscbc257 branch 2 times, most recently from c0f029c to 4e12a05 Compare March 11, 2026 16:15
@github-actions
Copy link

🐰 Bencher Report

Branchrscbc257-22962352049-143-1
Testbedubuntu-latest
Click to view all benchmark results
BenchmarkLatencyBenchmark Result
microseconds (µs)
(Result Δ%)
Upper Boundary
microseconds (µs)
(Limit %)
query📈 view plot
🚷 view threshold
375.06 µs
(-10.75%)Baseline: 420.23 µs
483.26 µs
(77.61%)
upsert_and_get📈 view plot
🚷 view threshold
256.24 µs
(-35.97%)Baseline: 400.20 µs
460.23 µs
(55.68%)
🐰 View full continuous benchmarking report in Bencher

@chvck chvck marked this pull request as ready for review March 11, 2026 16:22
@github-actions
Copy link

🐰 Bencher Report

Branchrscbc257-22962558271-145-1
Testbedubuntu-latest
Click to view all benchmark results
BenchmarkLatencyBenchmark Result
microseconds (µs)
(Result Δ%)
Upper Boundary
microseconds (µs)
(Limit %)
query📈 view plot
🚷 view threshold
421.53 µs
(+0.31%)Baseline: 420.23 µs
483.26 µs
(87.23%)
upsert_and_get📈 view plot
🚷 view threshold
405.05 µs
(+1.21%)Baseline: 400.20 µs
460.23 µs
(88.01%)
🐰 View full continuous benchmarking report in Bencher

@github-actions
Copy link

🐰 Bencher Report

Branchrscbc257-22962543828-144-1
Testbedubuntu-latest
Click to view all benchmark results
BenchmarkLatencyBenchmark Result
microseconds (µs)
(Result Δ%)
Upper Boundary
microseconds (µs)
(Limit %)
query📈 view plot
🚷 view threshold
426.88 µs
(+1.58%)Baseline: 420.23 µs
483.26 µs
(88.33%)
upsert_and_get📈 view plot
🚷 view threshold
405.19 µs
(+1.25%)Baseline: 400.20 µs
460.23 µs
(88.04%)
🐰 View full continuous benchmarking report in Bencher

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.

3 participants