Skip to content

Launch blockers: npm publish token and domain verification #7

Description

@ElxMaj

The code-owned public launch checks are green, but launch is still blocked by owner/account actions.

Evidence from pnpm launch:preflight on main at e7c6a05:

  • GitHub CI passes.
  • Launch site is live at https://marrow-six.vercel.app/.
  • Canonical, hero capitalization, sitemap, Vercel inspect, benchmark honesty, and package file checks pass.
  • npm registry still has 0.2.1; repo packages are 0.4.0.
  • marrowhq.com is on Namecheap failed WHOIS/contact-verification nameservers.

Owner actions:

  • Create an npm Automation token for the @marrowhq packages.
  • Add it as repo secret NPM_TOKEN in ElxMaj/marrow.
  • Publish @marrowhq/shared, @marrowhq/core, @marrowhq/web, @marrowhq/mcp-server, and @marrowhq/cli at 0.4.0.
  • Verify npm view @marrowhq/cli version returns 0.4.0.
  • Verify the Namecheap contact details for marrowhq.com so the failed-verification nameservers clear.
  • Add marrowhq.com to the Vercel project once the registrar hold clears.
  • Set DNS: apex A 76.76.21.21 and www CNAME cname.vercel-dns.com.
  • Re-run pnpm launch:preflight from the public repo and confirm it passes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is needed

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions