the-answerai / the-answerai/answer-engine
release: make the OSS repository and runtime image public
Open
Nobody has claimed this yet.
enhancement
needs-human-input
priority:high
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
Summary
Publish the audited OSS repository and GHCR runtime image after policy, history, workflow, and GitHub hardening prerequisites pass.
Proposed Approach
- Confirm history/identity approval and clean security audit.
- Confirm branch and Actions hardening.
- Change repository visibility to public.
- Change the GHCR runtime package to public through GitHub's supported administrative surface.
- Verify anonymous source access and digest-pinned image pulls.
Acceptance Criteria
- Policy, history, workflow, and settings prerequisites are complete.
- Repository is publicly browsable and anonymously cloneable.
- Runtime package is anonymously pullable by immutable digest.
- No private dependency blocks a fresh user.
- Publication state is re-read anonymously and recorded.
- Incident and disclosure instructions are visible.
Related
- Parent epic: #40
- Blocks installer publication and clean-machine acceptance.
- Do not publish npm.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with parent epic #40 and review the policy, history, security-audit, branch, Actions, and GitHub settings prerequisites named here. Then use GitHub's administrative surfaces to verify anonymous repository access and immutable-digest runtime image pulls. Done means all acceptance criteria are satisfied, including no private dependency and recorded anonymous publication state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, github-actions
- Domain
- cloud, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100