AYLITH
←

GitHerald

Studio notes · GitHerald

Changelog

Dated studio notes are distinct from package releases and current setup requirements.

  1. · docs

    A draft becomes a local public changelog

    The public GitHerald overview explains the product boundary. It is a static information page, not a hosted account, OAuth connection, generation service, or changelog host. The separate June entry records the source publish feature and keeps its old marketing stills withdrawn. This September study shows the actual locally run app UI with a disposable SQLite database and synthetic session.

    A fictional draft, reviewed and published locally

    The repository fixture-studio/newsroom-demo, two source identities, PR #12, release note, and displayed dates are hand-authored fictional fixture data, not observed provider events. The source activity links are unavailable, not verified GitHub references. No GitHub OAuth, GitHub API, LLM generation, customer data, or deployed GitHerald app was exercised. The visible Publish changelog action did run against this disposable database and created the row shown on the local public route; the published row was not preseeded. Blog and social copy were still drafts, not posted or scheduled.

    Annotated diagnostic poster composed from actual local GitHerald Published status and public changelog screenshots, with fictional/no-provider qualifiers
    An independently reviewed diagnostic poster study. The two embedded UI crops are real source-run pixels; framing, arrow and labels were added for explanation. This is not a final narrated-film cover.
    Actual local GitHerald dashboard with the fictional newsroom-demo repository and one draft generation
    The dashboard comes from a synthetic session and disposable local store. The repository is fictional and has no GitHub connection.
    Actual GitHerald draft review with expanded source activity listing two fictional commits and one fictional merged PR with links unavailable
    Review exposes the seeded source identities and marks their links unavailable; they are not evidence of a GitHub fetch.
    Actual GitHerald draft body and Markdown, HTML and JSON export controls; draft text explicitly says it was hand-authored for a visual fixture
    The hand-authored changelog body is shown in the real draft view. Export controls are visible; this capture did not verify a downloaded export file.
    Actual local GitHerald review page after clicking Publish changelog, showing Published status and a view-live-page link
    The actual Publish changelog button changed the disposable generation to Published and exposed a local public-page link.
    Actual local public GitHerald changelog route displaying fictional release v0.2.0 and explicit hand-authored fixture disclosure
    The local public route rendered the row created by that publish action. The URL was loopback, not a hosted customer changelog.

    The source-run stills and poster are independently reviewed and all 19 hosted media assets matched their versioned manifest by HTTP status, bytes and SHA-256. The current GitHub reader still has first-page limits and a PR end-date gap; this fictional capture does not validate provider retrieval or date-range fidelity. Actual paired motion footage, Cartesia narration, Remotion release films, timed captions, and a final film cover remain open.

  2. · added / changed

    Publish flow, persistence, and distribution

    GitHerald added an explicit changelog publish action. A signed-in user can review a generated draft, then publish its changelog to the configured app’s public page. Blog and social copy remain drafts for manual copy or export; this release did not add direct posting or scheduling.

    The release also added a SQLite-backed store, Markdown/HTML/JSON export, an RSS feed, an embeddable changelog view, conventional-commit version inference, and a minimal GET /health endpoint. The AI provider can be selected through configuration.

    The previous paired landing images were archived from this entry because they advertised an unconnected waitlist, pricing, editing, and publishing behavior that this product release did not provide. Product UI screenshots and films for this release still need to be captured and verified.

  3. · added

    Origins

    Githerald entered the umbrella: the runnable app and the landing were vendored in.