LaunchRepo.

Changelog

LaunchRepo changelog

Every tagged release of the private repository and the changes on its main branch since, newest first. Dates are the day the change was published on GitHub.

LaunchRepo is delivered as a private GitHub repository, so “updates” are simply new commits and tags in that repository. Buyers pull them with git; nothing is installed and nothing phones home. Release notes for the repository itself ship as CHANGELOG.md inside it.

  1. main branch · not tagged yet

    Launch-date floor and representation briefing

    • Owner-set earliest launch date in product.json; record.py requires --launch-date for “scheduled” and refuses anything earlier than that floor.
    • ONBOARDING.md now asks when launches should go live and states plainly that free-tier directories can take several weeks to review and publish.
    • New PR-BRIEFING.md: a short session that shows the owner factual representation examples (maker bio, launch intro, “why I built this”) for correction before any personal fact reaches a public listing.
    • Approved examples and corrections are kept in templates/project/representation.md.
  2. main branch · not tagged yet

    Local dashboard and one-prompt start

    • scripts/dashboard.py and dashboard/: a zero-dependency local web UI (Python standard library, 127.0.0.1 only) showing products, what the agent knows about each one, onboarding checks, submission states grouped by needs-you / problems / in review / scheduled / live, follow-up dates, the catalog with playbooks, agent prompts and the docs.
    • Product JSON and notes can be edited in the browser; outcomes are recorded through record.py with identical validation. --demo serves a throwaway sample workspace.
    • START.md and prompts/start.md: one pasted prompt makes the agent create the private workspace, start the dashboard and hand back the link; AGENTS.md contains the exact procedure with verification.
    • scripts/init-workspace.py copies dashboard/, DASHBOARD.md, START.md and PR-BRIEFING.md into new workspaces.
  3. Version 1.2.0

    346 platform playbooks

    • New platform playbooks, including CodeHype and additional launch boards, AI, developer-tool and startup directories — 346 in total.
    • Catalog, platform index and search tool updated to include every new entry.
    • To update an existing workspace: copy the new playbooks and the updated catalog and index files; keep workspace.json, projects/, credentials and submission records.
  4. main branch · not tagged yet

    Priority evidence and catalog screening

    • Dated, claim-specific priority evidence, current tracker overlays and score explanations; unstructured inputs stay readable but cannot earn unsupported SEO or audience credit.
    • Full catalog HTTP screening snapshot with explicit unknowns plus a bounded listing-candidate screen — discovery success is not listing indexation.
    • Public sample audit references added on the main branch; previously issued immutable release archives keep their original contents.
  5. Version 1.1.0

    275 platform playbooks

    • Platform playbook library expanded to 275 files with submission steps, required assets, account setup, badge placement, follow-up and troubleshooting.
    • Every catalog entry now links to its own playbook; new platforms added.
    • Platform selection simplified by product category and name.
    • Product credentials and execution history stay in your separate private workspace; follow PRIVATE-WORKSPACE.md before any push.
  6. Version 1.0.1

    First immutable release

    • Canonical immutable GitHub release of the private customer repository (v1.0.0 was the initial non-immutable publication).
    • 222 directory candidates in the catalog, 30 of them with detailed reviewed playbooks; the remaining entries are marked as research candidates, not verified free routes.
    • Guided onboarding for product, browser, verification email, private credential storage and website badges; workspace and tracker tools (record.py, submissions.csv).
    • No pilot identities, credentials or execution history in the customer archive.

How updates reach you

After purchase you clone the repository once. New playbooks, catalog and index files arrive as normal commits — pull them whenever you like.

Your products, credentials and submission records live in your own private workspace next to the checkout, so an update never touches them. Keep workspace.json, projects/ and your tracker files; copy the new playbooks and catalog over.

Updates we publish are included for everyone who bought. We do not promise a specific update, cadence or future scope — see the terms of service.