Skip to content

Finish the organization-wide migration to hayatepy.dev and create-hayate 0.13.2 #36

Closed

Description

@yhay81

Problem

The canonical generator and hayatepy.dev now use Hayate 0.15.2 and
create-hayate 0.13.2, but several public default branches still route users
through the superseded .github/blob/main/docs/ tree. golden-app and one
family quickstart also retain actionable create-hayate==0.13.1 pins.

This is a public-discovery and PyPI long-description consistency gap, not a
runtime compatibility failure.

Audited default-branch scope

  • organization profile and llms.txt
  • create-hayate frontend compatibility documentation
  • golden-app
  • hayate-admin
  • hayate-auth
  • hayate-fetch
  • hayate-htmx
  • hayate-mcp
  • hayate-openapi
  • hayate-sql
  • design-partner links in .github and docs

Acceptance criteria

  • route public Start here links to https://hayatepy.dev/
  • route compatibility links to https://hayatepy.dev/evidence/compatibility/
  • route production/first-app links to their canonical hayatepy.dev pages
  • update actionable generator pins to create-hayate==0.13.2
  • synchronize golden-app with the released generator and rerun its complete gate
  • preserve immutable historical evidence links when they intentionally identify a source snapshot
  • add a default-branch regression audit so the superseded prefix and stale actionable pins cannot return
  • publish patch releases where README changes must reach PyPI long descriptions
  • verify every changed main branch, release artifact, and public page

Already completed

Owner-external design-partner and independent-security-review gates remain
separate; this owned-channel cleanup does not count toward either.

Activity

  1. yhay81 commented on Jul 30, 2026

    @yhay81
    ContributorAuthor

    Progress update (2026-07-30):

    Remaining in this issue: migrate the individual package README/template links (including generated create-hayate README text), add an organization-wide drift gate, and patch-release published packages whose distribution metadata changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions