Rename CI scaffolding from luminarr to prism#1
Merged
Conversation
Prism's .github scaffolding was byte-identical to luminarr/luminarr from the original fork and still contained every reference to "luminarr" throughout the CI workflows, issue templates, and contributing guide. This sync renames everything to prism: - ci.yml — module paths from github.com/luminarr/luminarr/... to github.com/beacon-stack/prism/..., binary name luminarr → prism, artifact names updated - ISSUE_TEMPLATE/bug_report.yml — "Luminarr version" → "Prism version", LUMINARR_LOG_LEVEL → PRISM_LOG_LEVEL - CONTRIBUTING.md — retitled and git clone URL updated - claude.yml — unchanged (not app-specific) - feature_request.yml — Radarr parity dropdown retained (Prism is Radarr-family) No structural changes to the CI flow itself — same jobs, same docker variants, same secrets list. Prism's ci.yml is the closest of the four Beacon apps to the luminarr baseline since it inherited from it. Requires GHCR_TOKEN, ANTHROPIC_API_KEY, TMDB_API_KEY, and TRAKT_CLIENT_ID secrets on the repo before the workflows run green. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Before this change prism's go.mod had a local replace directive
pointing the pulse SDK dependency at the author's working copy:
replace github.com/beacon-stack/pulse => /data/home/davidfic/dev/beacon/pulse
That works on the author's laptop but breaks every CI run — runners
don't have /data/home/davidfic/dev/beacon/pulse, so go mod download
fails and cascades into test, lint, build, and docker.
Replaces it with a normal module require pinned to the newly tagged
pulse v0.1.0 on github.com/beacon-stack/pulse. Cross-module local dev
is preserved via go.work (gitignored) at the beacon monorepo root.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Triggers on v* tag pushes and produces:
- Cross-platform binaries (linux/darwin/windows × amd64/arm64, minus
windows/arm64) archived as tar.gz / zip with LICENSE, README, and
config.example.yaml alongside
- checksums.txt for all archives
- A GitHub Release with auto-generated notes from commit messages
(excludes docs/chore/test/ci prefixes)
- Two Docker image variants pushed to ghcr.io/beacon-stack/prism:
* `:{{version}}` / `:v{{major.minor}}` / `:v{{major}}` / `:latest`
built from docker/Dockerfile (alpine with ffprobe)
* `:{{version}}-minimal` / `:latest-minimal` built from
docker/Dockerfile.minimal (scratch, no ffprobe)
TMDB and Trakt keys are baked into the binary and docker images via
-ldflags at build time — requires TMDB_API_KEY and TRAKT_CLIENT_ID
secrets on the repo in addition to GHCR_TOKEN.
Tag a release with `git tag v0.1.0 && git push --tags` and the
workflow takes over.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Prism's `.github` directory was inherited byte-for-byte from the original `luminarr/luminarr` fork and still referenced `luminarr` throughout. This PR renames everything to match the current project identity without changing the CI flow itself.
What changed
Required repo secrets
Test plan