Reactive Resume now lives at reactive-resume/reactive-resume. The repository was previously named amruthpillai/reactive-resume, then reactive-resume/app. Git history, stars, issues, pull requests, and fork relationships remain attached to the same repository.
| Resource |
Address |
| GitHub repository |
reactive-resume/reactive-resume |
| Docker Hub |
Unchanged: amruthpillai/reactive-resume |
| GitHub Container Registry |
ghcr.io/reactive-resume/reactive-resume |
Verified images and production deployment
On September 12, 2026, the current version 5.3.0 was rebuilt from commit f89acb436865cf536fffed2b23d4d72a7ecff0db and production was redeployed. No version bump, new Git tag, or new GitHub release was created for this rename. Existing stable image aliases were updated.
latest, v5, v5.3, and v5.3.0 on both registries resolve to:
sha256:7c7b7824785d1386fa6e0e6132c1abe43e3c281f90dbf3b1474b60bffb64d89e
Build and deployment run 34685606073 completed successfully: native AMD64/ARM64 builds, SBOMs and provenance, Cosign signing, anonymous pulls on both architectures from both registries, production redeployment, and Cloudflare cache purge. Independent manifest checks confirmed all eight registry/tag combinations above. Production's health endpoint reported healthy version 5.3.0; its homepage served the new repository URL.
What changes for users
- Hosted users: No account or resume changes at rxresu.me.
- Docker Hub users: Keep
amruthpillai/reactive-resume with your existing tag.
- GHCR users: Use
ghcr.io/reactive-resume/reactive-resume with a verified tag listed above. Future builds publish to this namespace. Previous GHCR namespaces are retained for historical pulls and no longer receive new builds. Other historical tags have not been migrated to the final namespace.
services:
app:
image: ghcr.io/reactive-resume/reactive-resume:latestNo database reset, volume deletion, or resume-data migration is required. Normal version-upgrade guidance still applies when changing application versions.
Contributors: Existing GitHub repository URLs redirect. Update your remote:
Sponsors: Continue supporting Amruth Pillai on GitHub Sponsors and Reactive Resume on Open Collective. Funding recipients are unchanged.
Signatures and historical images
New builds use https://github.com/reactive-resume/reactive-resume/.github/workflows/docker-build.yml@refs/heads/main and issuer https://token.actions.githubusercontent.com. GitHub reports immutable OIDC subject prefix repo:reactive-resume@245328954/reactive-resume@249995750; inspect actual claims before changing external trust policies.
The original v5.3.0 image copied on September 11 remains at ghcr.io/reactive-resume/app@sha256:c487ec5edcfe054bcb312fcd498f868e56f274756d0046b01c83f210855017ab. Its original signature identity is https://github.com/amruthpillai/reactive-resume/.github/workflows/docker-build.yml@refs/heads/main. Historical labels, digests, and signature identities intentionally remain unchanged. This original image is different from the current-version rebuild above; pin the historical digest if you need that exact artifact.
Documentation and integrations
Repository links, badges, clone instructions, image examples, metadata, funding manifests, and the GitHub star-count API use the new repository. The MCP registry identifier remains io.github.amruthpillai/reactive-resume.
See the publishing runbook for verification commands and historical-image guidance. Documentation-hosting, Crowdin, and other externally managed integration settings should be checked in their owning accounts; repository renaming alone does not verify those settings.
Reactive Resume now lives at reactive-resume/reactive-resume. The repository was previously named
amruthpillai/reactive-resume, thenreactive-resume/app. Git history, stars, issues, pull requests, and fork relationships remain attached to the same repository.reactive-resume/reactive-resumeamruthpillai/reactive-resumeghcr.io/reactive-resume/reactive-resumeVerified images and production deployment
On September 12, 2026, the current version 5.3.0 was rebuilt from commit
f89acb436865cf536fffed2b23d4d72a7ecff0dband production was redeployed. No version bump, new Git tag, or new GitHub release was created for this rename. Existing stable image aliases were updated.latest,v5,v5.3, andv5.3.0on both registries resolve to:Build and deployment run 34685606073 completed successfully: native AMD64/ARM64 builds, SBOMs and provenance, Cosign signing, anonymous pulls on both architectures from both registries, production redeployment, and Cloudflare cache purge. Independent manifest checks confirmed all eight registry/tag combinations above. Production's health endpoint reported healthy version
5.3.0; its homepage served the new repository URL.What changes for users
amruthpillai/reactive-resumewith your existing tag.ghcr.io/reactive-resume/reactive-resumewith a verified tag listed above. Future builds publish to this namespace. Previous GHCR namespaces are retained for historical pulls and no longer receive new builds. Other historical tags have not been migrated to the final namespace.No database reset, volume deletion, or resume-data migration is required. Normal version-upgrade guidance still applies when changing application versions.
Contributors: Existing GitHub repository URLs redirect. Update your remote:
Sponsors: Continue supporting Amruth Pillai on GitHub Sponsors and Reactive Resume on Open Collective. Funding recipients are unchanged.
Signatures and historical images
New builds use
https://github.com/reactive-resume/reactive-resume/.github/workflows/docker-build.yml@refs/heads/mainand issuerhttps://token.actions.githubusercontent.com. GitHub reports immutable OIDC subject prefixrepo:reactive-resume@245328954/reactive-resume@249995750; inspect actual claims before changing external trust policies.The original v5.3.0 image copied on September 11 remains at
ghcr.io/reactive-resume/app@sha256:c487ec5edcfe054bcb312fcd498f868e56f274756d0046b01c83f210855017ab. Its original signature identity ishttps://github.com/amruthpillai/reactive-resume/.github/workflows/docker-build.yml@refs/heads/main. Historical labels, digests, and signature identities intentionally remain unchanged. This original image is different from the current-version rebuild above; pin the historical digest if you need that exact artifact.Documentation and integrations
Repository links, badges, clone instructions, image examples, metadata, funding manifests, and the GitHub star-count API use the new repository. The MCP registry identifier remains
io.github.amruthpillai/reactive-resume.See the publishing runbook for verification commands and historical-image guidance. Documentation-hosting, Crowdin, and other externally managed integration settings should be checked in their owning accounts; repository renaming alone does not verify those settings.