Delete old nightly release (#36)

.github/workflows/nightly.yml

@@ -36,14 +36,21 @@ jobs:
           name: companion.apk
           path: companion/build/outputs/apk/nightly/signed/companion-nightly-signed.apk
           if-no-files-found: error
+      - name: Delete existing nightly tag
+        run: git push origin --delete nightly || true
+      - name: Delete existing nightly release
+        run: |
+          curl -X DELETE
+            -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}"
+            https://api.github.com/repos/${{ github.repository }}/releases/tags/nightly
       - name: Release
         uses: softprops/action-gh-release@v2
         with:
           files: |
             authenticator/build/outputs/apk/nightly/signed/authenticator-nightly-signed.apk
             companion/build/outputs/apk/nightly/signed/companion-nightly-signed.apk
+          name: Nightly Release
           tag_name: nightly
-          release_name: Nightly Release
           body: |
             Nightly build for commit ${{ github.sha }}.
           draft: false

README.md

@@ -30,6 +30,10 @@ Many websites allow you to additionally protect your accounts via certain types
 
 Traditionally, security keys take the form of USB sticks, but there are also models that can be used via NFC, Bluetooth or Lightning. But many computers and phones even come with security key functionality built-in: Windows Hello, macOS Touch ID (with Chrome) or your Android 7+ phone can all be used with sites asking for a security key. Unfortunately, Wear OS watches could so far not be used as security keys, even though many of them are equipped with hardware facilities for cryptographic keys used for Google Pay. This is where WearAuthn comes in.
 
+## Installation
+
+In addition to the Google Play Store, you can also download the latest [nightly build](https://github.com/fmeum/WearAuthn/releases/tag/nightly).
+
 ## Usage
 
 Watch a demo: