michangarrito/apps/backend/node_modules/chrome-launcher/contributing.md
rckrdmrd 48dea7a5d0 feat: Initial commit - michangarrito
Marketplace móvil para negocios locales mexicanos.

Estructura inicial:
- apps/backend (NestJS API)
- apps/frontend (React Web)
- apps/mobile (Expo/React Native)
- apps/mcp-server (Claude MCP Server)
- apps/whatsapp-service (WhatsApp Business API)
- database/ (PostgreSQL DDL)
- docs/ (Documentación)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-07 04:41:02 -06:00

559 B

Release Procedure

  1. When good, do npm publish. it'll run the prepublish script (build & test)
    • complete publishing to npm. (we now have the tagged commit, too).
  2. To complete the changelog: Do git log --oneline and then edit the resulting text to match the style in changelog.md. it's pretty manual. update that file. commit.
  3. Push back up to origin. Do git push --tags to ensure the tag is there.
  4. Open up https://github.com/GoogleChrome/chrome-launcher/releases and Draft a New Release. Use the same changelog.md markdown. Publish.