rainbo 0.1.0 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -96,6 +96,7 @@ rainbo data-sync cmt-jobs --data-file cmt-jobs.json
96
96
  rainbo data-verify lineage-verify-table --data-file verify-table.json
97
97
  rainbo toolbox sql-debug --datasource-id 1 --sql "select 1"
98
98
  rainbo toolbox lineage-spark --data-file lineage-spark.json
99
+ rainbo toolbox volume-content --datasource-id 1 --volume public.v --file-path dir/result.json
99
100
 
100
101
  rainbo lineage graph create --data-file lineage-graph.json
101
102
  rainbo lineage graph get "lineage_graph:migration:1001"
@@ -107,7 +108,9 @@ rainbo lineage graph delete "lineage_graph:migration:1001"
107
108
 
108
109
  ## Release
109
110
 
110
- 1. Update `package.json` and `rust/Cargo.toml` to the same version.
111
+ 1. Update `package.json`, `rust/Cargo.toml`, and the `rainbo` package entry in
112
+ `Cargo.lock` to the same version. Do not publish a metadata-only version
113
+ bump; the bundled Rust binary must report the same version as npm.
111
114
  2. Export the npm publish token from the release machine:
112
115
 
113
116
  ```bash
@@ -127,6 +130,10 @@ whose `package.json` name is not `rainbo`.
127
130
  npm run publish:npm:local
128
131
  ```
129
132
 
133
+ The publish script refuses to continue if `package.json` and `rust/Cargo.toml`
134
+ versions differ. After building the current-platform binary, it also runs the
135
+ bundled binary and verifies `rainbo version` matches `package.json`.
136
+
130
137
  If npm returns `EOTP`, use an automation-capable publish token or pass the
131
138
  current OTP:
132
139
 
@@ -143,7 +150,7 @@ RAINBO_NPM_BUILD_TARGETS=darwin-arm64,darwin-x64 npm run publish:npm:local
143
150
  ```
144
151
 
145
152
  The package source lives under the Rainbo GitLab repository as
146
- `packages/rainbo-cli`; npm publishing is intentionally local and does not depend
153
+ `packages/rainbo`; npm publishing is intentionally local and does not depend
147
154
  on a separate repository or CI workflow.
148
155
 
149
156
  ## Skills
@@ -155,7 +162,7 @@ npx skills add git@gitlab.clickzetta-inc.com:ee/rainbo.git -y -g
155
162
  ```
156
163
 
157
164
  `git@gitlab.clickzetta-inc.com:ee/rainbo.git` is the skills repository
158
- source used by `rainbo update`. The old aggregate `rainbo-cli` skill has
165
+ source used by `rainbo update`. The old aggregate `rainbo` skill has
159
166
  been removed; current Rainbo skills use focused names such as `rainbo-auth`.
160
167
 
161
168
  New Rainbo skills should follow the style in the repository-level
@@ -166,7 +173,7 @@ to `rainbo-auth` first instead of duplicating session rules.
166
173
 
167
174
  ## Project layout
168
175
 
169
- `packages/rainbo-cli/`:
176
+ `packages/rainbo/`:
170
177
 
171
178
  ```text
172
179
  rust/ Rust CLI implementation
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "rainbo",
3
- "version": "0.1.0",
3
+ "version": "0.1.2",
4
4
  "description": "Rainbo command line tools for data migration workflows",
5
5
  "bin": {
6
6
  "rainbo": "packaging/npm/run.js"
@@ -31,7 +31,7 @@ function installIfMissing() {
31
31
  : `unsupported platform ${currentPlatformKey()}`;
32
32
  console.error(`rainbo binary package is missing for ${currentPlatformKey()}.`);
33
33
  console.error(`Expected bundled npm binary: ${packageHint}`);
34
- console.error("Rebuild and reinstall the npm package from packages/rainbo-cli.");
34
+ console.error("Rebuild and reinstall the npm package from packages/rainbo.");
35
35
  process.exit(1);
36
36
  }
37
37