don't build a docker image and attach to the release. Scrutiny is public now, images hosted on docker-hub.

.github/workflows/release-docker.yaml

@@ -1,34 +0,0 @@
-#TODO: once scrutiny is public, this file can be deleted.
-# builds a docker image and attaches it to the latest release.
-name: Release Docker
-
-on:
-  release:
-    # Only use the types keyword to narrow down the activity types that will trigger your workflow.
-    types: [published]
-jobs:
-  docker-release:
-    name: Docker Release
-    runs-on: ubuntu-latest
-    container: docker:19.03.2
-    env:
-      PROJECT_PATH: /go/src/github.com/analogj/scrutiny
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v2
-        with:
-          ref: ${{github.event.release.tag_name}}
-      - name: Build Docker
-        run: |
-          docker build -t analogj/scrutiny:latest -t analogj/scrutiny:${{ github.event.release.tag_name }} -f docker/Dockerfile .
-          docker save -o docker-analogj-scrutiny-${{ github.event.release.tag_name }}.tar analogj/scrutiny
-      - name: Upload Collector Release Asset
-        id: upload-release-asset3
-        uses: actions/upload-release-asset@v1
-        env:
-          GITHUB_TOKEN: ${{ secrets.SCRUTINY_GITHUB_TOKEN }}
-        with:
-          upload_url: ${{ github.event.release.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
-          asset_path: docker-analogj-scrutiny-${{ github.event.release.tag_name }}.tar
-          asset_name: docker-analogj-scrutiny-${{ github.event.release.tag_name }}.tar
-          asset_content_type: application/octet-stream