Skip to content

catalog: add CI assertion that build output is a single DLL #27

Description

@CCoupel

Context

Emby catalog requires that a plugin be distributed as a single `.dll` file. There is currently no CI check to enforce this constraint.

Problem

A dependency update or csproj change could silently introduce additional DLLs in the build output. If a PR is merged that breaks the single-DLL requirement, it will only be caught at catalog submission time.

Fix

Add a step in the GitHub Actions release workflow to assert exactly one `.dll` is present in `dist/`:

```yaml

  • name: Assert single DLL output
    run: |
    count=$(find dist/ -name ".dll" | wc -l)
    if [ "$count" -ne 1 ]; then
    echo "ERROR: Expected 1 DLL in dist/, found $count"
    find dist/ -name "
    .dll"
    exit 1
    fi
    ```

Priority

Medium — Prevents silent regressions before catalog submission.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    catalog-complianceEmby catalog publication complianceciCI/CD related

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions