add dbg prints

ci/build_linux_artifacts.sh

@@ -77,8 +77,8 @@ build_node_binary() {
     fi
     # We don't pass in target, since the native target here already matches
     # and openblas-src doesn't do well with cross-compilation.
-    npm run build-release
-    npm run pack-build
+    npm run build-release --script-shell bash
+    npm run pack-build --script-shell bash
 
     popd
 }

ci/build_macos_artifacts.sh

@@ -2,6 +2,20 @@
 # Usage: ./build_macos_artifacts.sh [target]
 # Targets supported: x86_64-apple-darwin aarch64-apple-darwin
 
+prebuild_rust() {
+    # Building here for the sake of easier debugging.
+    pushd rust/ffi/node
+
+    for target in $1
+    do
+        echo "Building rust library for $target"
+        export RUST_BACKTRACE=1
+        cargo build --release --target $target
+    done
+
+    popd
+}
+
 build_node_binaries() {
     pushd node
     

ci/release_process.md

@@ -35,18 +35,14 @@ git push --tag vX.X.X
 ```
 
 When the tag is pushed, GitHub actions will start building the libraries and
-will upload them to a draft release. Wait for those jobs to complete.
+will upload them to a draft release.
 
-### 3. Publish the release
+While those jobs are running, edit the release notes as needed. For example, 
+bring relevant new features and bugfixes to the top of the notes and the testing
+and CI changes to the bottom.
 
-Once the jobs are complete, you can edit the 
-
-2. Push a tag, such as vX.X.X. Once the tag is pushrf, GitHub actions will start
-   building the native libraries and uploading them to a draft release. Wait for
-   those jobs to complete.
-3. If the libraries are successful, edit the changelog and then publish the
-   release. Once you publish, a new action will start and upload all the 
-   release artifacts to npm.
+Once the jobs have finished, the release will be marked as not draft and the
+artifacts will be released to crates.io, NPM, and PyPI.
 
 ## Manual process