remove publish.yml, for now

Author: dr-frmr

.github/workflows/publish.yml

@@ -1,57 +1,59 @@
-on:
-  push:
-    tags:
-      # runs every time a new tag is made
-      - '*'
-
-name: Publish
-
-jobs:
-  crates_io_publish:
-    name: Publish (crates.io)
-
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    steps:
-      - uses: actions/checkout@v3
-      - uses: dtolnay/rust-toolchain@nightly
-
-      - name: cargo-release Cache
-        id: cargo_release_cache
-        uses: actions/cache@v3
-        with:
-          path: ~/.cargo/bin/cargo-release
-          key: ${{ runner.os }}-cargo-release
-
-      - run: cargo install cargo-release
-        if: steps.cargo_release_cache.outputs.cache-hit != 'true'
-
-      - name: cargo login
-        run: cargo login ${{ secrets.CARGO_REGISTRY_TOKEN }}
-
-      # allow-branch HEAD is because GitHub actions switches
-      # to the tag while building, which is a detached head
-
-      # Publishing is currently messy, because:
-      #
-      # * `peace_rt_model_core` exports `NativeError` or `WebError` depending on the target.
-      # * `peace_rt_model_web` fails to build when publishing the workspace for a native target.
-      # * `peace_rt_model_web` still needs its dependencies to be published before it can be
-      #    published.
-      # * `peace_rt_model_hack` needs `peace_rt_model_web` to be published before it can be
-      #    published.
-      #
-      # We *could* pass through `--no-verify` so `cargo` doesn't build the crate before publishing,
-      # which is reasonable, since this job only runs after the Linux, Windows, and WASM builds
-      # have passed.
-      - name: "cargo release publish"
-        run: |-
-          cargo release \
-            publish \
-            --workspace \
-            --all-features \
-            --allow-branch HEAD \
-            --no-confirm \
-            --no-verify \
-            --execute
+#  TODO: use this once alloy-rpc is on crates.io
+
+# on:
+#   push:
+#     tags:
+#       # runs every time a new tag is made
+#       - '*'
+
+# name: Publish
+
+# jobs:
+#   crates_io_publish:
+#     name: Publish (crates.io)
+
+#     runs-on: ubuntu-latest
+#     timeout-minutes: 10
+#     steps:
+#       - uses: actions/checkout@v3
+#       - uses: dtolnay/rust-toolchain@nightly
+
+#       - name: cargo-release Cache
+#         id: cargo_release_cache
+#         uses: actions/cache@v3
+#         with:
+#           path: ~/.cargo/bin/cargo-release
+#           key: ${{ runner.os }}-cargo-release
+
+#       - run: cargo install cargo-release
+#         if: steps.cargo_release_cache.outputs.cache-hit != 'true'
+
+#       - name: cargo login
+#         run: cargo login ${{ secrets.CARGO_REGISTRY_TOKEN }}
+
+#       # allow-branch HEAD is because GitHub actions switches
+#       # to the tag while building, which is a detached head
+
+#       # Publishing is currently messy, because:
+#       #
+#       # * `peace_rt_model_core` exports `NativeError` or `WebError` depending on the target.
+#       # * `peace_rt_model_web` fails to build when publishing the workspace for a native target.
+#       # * `peace_rt_model_web` still needs its dependencies to be published before it can be
+#       #    published.
+#       # * `peace_rt_model_hack` needs `peace_rt_model_web` to be published before it can be
+#       #    published.
+#       #
+#       # We *could* pass through `--no-verify` so `cargo` doesn't build the crate before publishing,
+#       # which is reasonable, since this job only runs after the Linux, Windows, and WASM builds
+#       # have passed.
+#       - name: "cargo release publish"
+#         run: |-
+#           cargo release \
+#             publish \
+#             --workspace \
+#             --all-features \
+#             --allow-branch HEAD \
+#             --no-confirm \
+#             --no-verify \
+#             --execute