ci: noverify on publish (#3760)

We publish 33 crates, and sometimes toward the end of the publish job,
we timeout waiting for crates.io to reflect the publication.

This can be for a number of reasons, commonly because crates.io is
overloaded and we are supposed to come back later.

This leaves the release in a weird unfinished state where it becomes
hard to complete it. It's also very slow, taking on average about 40
minutes to re-check and publish the entire dependency tree for every
crate that we publish.

If we switch to `--no-verify` that should free us from both issues, at
the risk of potentially creating a release of a crate that doesn't build
outside of the workspace properly.

Signed-off-by: Andrew Duffy <[email protected]>

Author: a10y

.github/workflows/publish.yml

@@ -28,7 +28,7 @@ jobs:
 
       - name: Release
         run: |
-          cargo publish -Z package-workspace --allow-dirty --workspace \
+          cargo publish -Z package-workspace --no-verify --allow-dirty --workspace \
           --exclude bench-vortex \
           --exclude vortex-python \
           --exclude vortex-duckdb \