clean up workflows

.github/workflows/pyth-cosmwasm-contract.yml → .github/workflows/ci-cosmwasm-contract.yml

@@ -1,4 +1,4 @@
-name: Pyth CosmWasm Contract
+name: Test CosmWasm Contract
 
 on:
   pull_request:

.github/workflows/publish-js.yml

@@ -1,13 +1,12 @@
 name: Publish Pyth JS packages
 
 on:
-  release:
-    types:
-      - created
+  push:
+    tags:
+      - pyth-js-v*
 jobs:
   publish-js:
     name: Publish Javascript Packages to NPM
-    if: ${{ startsWith(github.ref, 'refs/tags/pyth-js-v') }}
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v2

.github/workflows/publish-pyth-sdk-cw.yml

@@ -1,13 +1,12 @@
 name: Publish Pyth SDK for Cosmwasm to crates.io
 
 on:
-  release:
-    types:
-      - created
+  push:
+    tags:
+      - pyth-sdk-cw-v*
 jobs:
   publish-pyth-sdk-cw:
     name: Publish Pyth SDK CW
-    if: ${{ startsWith(github.ref, 'refs/tags/pyth-sdk-cw-v') }}
     runs-on: ubuntu-latest
     steps:
       - name: Checkout sources

.github/workflows/release-pyth-cosmwasm-contract.yml

@@ -4,7 +4,6 @@ on:
   push:
     tags:
       - pyth-cosmwasm-contract-v*
-
 jobs:
   release-contract:
     name: Build and Release cosmwasm contract

README.md

@@ -62,7 +62,7 @@ To perform a release, follow these steps:
 
 1. Update the version number in the `package.json` file for the package(s) you wish to release. Please follow [Semantic Versioning](https://semver.org/) for package versions.
 2. Submit a PR with the changes and merge them in to main.
-3. Create a new release in github with a tag of the form `pyth-js-v<number>`. You can simply increment the version number each time -- it doesn't affect any of the published information.
+3. Create a new tag `pyth-js-v<number>` and push to github. You can simply increment the version number each time -- it doesn't affect any of the published information.
 4. When this release is published, it will automatically trigger a CI workflow to publish the updated packages to NPM.
 
 If you have a javascript package that shouldn't be published, simply add `"private": "true"` to the `package.json` file