Store built binaries in the release assets #812

New Issue

OVERLORD · 2026-02-04T22:46:57+03:00

OVERLORD commented

2026-02-04 22:46:57 +03:00

Originally created by @GerardoGR on GitHub (Sep 26, 2020).

For convenience it would be nice to have the pre-built binaries in the Github release assets.

I've seen that there is Release github action for uploading the asset, but this doesn't get triggered:

    - name: Release
      uses: Shopify/upload-to-release@1.0.0
      if: startsWith(github.ref, 'refs/tags/')
      with:
        name: bitwarden_rs-${{ matrix.db-backend }}-${{ matrix.target }}${{ matrix.ext }}
        path: target/${{ matrix.target }}/release/bitwarden_rs${{ matrix.ext }}
        repo-token: ${{ secrets.GITHUB_TOKEN }}

Originally created by @GerardoGR on GitHub (Sep 26, 2020). For convenience it would be nice to have the pre-built binaries in the Github release assets. I've seen that there is **Release** github action for uploading the asset, but this doesn't get triggered: ``` - name: Release uses: Shopify/upload-to-release@1.0.0 if: startsWith(github.ref, 'refs/tags/') with: name: bitwarden_rs-${{ matrix.db-backend }}-${{ matrix.target }}${{ matrix.ext }} path: target/${{ matrix.target }}/release/bitwarden_rs${{ matrix.ext }} repo-token: ${{ secrets.GITHUB_TOKEN }} ```

OVERLORD added the better for forum label 2026-02-04 22:46:57 +03:00

OVERLORD closed this issue

2026-02-04 22:47:09 +03:00

OVERLORD referenced this issue

2026-02-05 04:56:43 +03:00

[PR #812] [MERGED] Fixes #635 - Unique constraint violation when using U2F tokens on PostgreSQL #2778

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#812