# Unraid Community Applications release and submission checklist - [x] Create the public GitHub repository. - [x] Replace repository placeholders with the public ReelSpace URLs. - [x] Enable the GitHub Container Registry package in the release workflow. - [x] Publish the package and set it to **public**. - [x] Publish semantic release `v0.1.3`. - [x] Pull the published manifest anonymously and verify amd64/arm64 images. - [x] Confirm the raw Unraid XML URL is public. - [x] Confirm the raw square PNG icon URL is public and renders correctly. - [x] Provide stable support and issue tracking through GitHub Issues. - [x] Add the required root `ca_profile.xml` with repository profile information. - [x] Verify project, support, registry, template, and icon URLs. - [x] Keep the Docker application XML under `templates/`, as required by the current Community Applications starter repository. - [ ] Validate `ca_profile.xml` and `templates/reelspace.xml` with the current Community Applications template scanner. The `` element is the Docker image source; no separate repository wrapper is currently required. - [x] Test template installation on Unraid 7.2.x with `/config`, `/data/media:ro`, and port 8080. - [x] Confirm the container is not privileged, has no Docker socket, and media is read-only. - [ ] Test scans against user shares, individual disks, a pool, Unicode paths, sparse VM images, hardlinked imports, permission failures, and one million files. - [x] Test upgrade from v0.1.2 to v0.1.3 with an existing `/config`. - [ ] Document migration rollback planning and backup. - [ ] Test uninstall without deleting appdata unless the user explicitly chooses it. - [ ] Submit the template repository through the current Unraid Community Applications submission portal. - [ ] Respond to moderator feedback and document every change. - [ ] Maintain semantic tags, stable `latest`, changelog, security advisories, and the forum support thread. Do not claim affiliation with Plex, Unraid, or Lime Technology.