Commit ffcb2bf
authored
chore(cli): set binding version in release workflow (#263)
### TL;DR
Fix version handling in the release workflow to ensure consistent versioning across Rust and npm packages.
### What changed?
- Added a new step in the release workflow to set the binding version using the commit SHA
- Renamed the existing version step to "Set npm packages version" for clarity
- Updated the version in `packages/cli/binding/Cargo.toml` from "0.0.1" to "0.0.0" to match the npm versioning pattern
- Corresponding update in `Cargo.lock` to reflect the version change
### How to test?
1. Trigger the release workflow
2. Verify that both the Rust binding and npm packages have the same version format (`0.0.0-{commit-sha}`)
3. Check that the artifacts are properly versioned in the release
### Why make this change?
This change ensures version consistency between the Rust bindings and npm packages during the release process. By using the same version pattern across all components, we avoid potential compatibility issues and make it easier to track which versions belong together.1 parent a74a40b commit ffcb2bf
3 files changed
Lines changed: 7 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
47 | 47 | | |
48 | 48 | | |
49 | 49 | | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
50 | 54 | | |
51 | 55 | | |
52 | 56 | | |
| |||
108 | 112 | | |
109 | 113 | | |
110 | 114 | | |
111 | | - | |
| 115 | + | |
112 | 116 | | |
113 | 117 | | |
114 | 118 | | |
| |||
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
| 3 | + | |
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| |||
0 commit comments