zio/guardia-messenger
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
8e5a5b7e6f
guardia-messenger/node_modules/chrome-launcher/contributing.md
DESKTOP-TKLFCPRython f29f525c77 refactor: 101.79.17.164 → zioinfo.co.kr 전체 도메인 변환 + Manager UI 배포 
- 37개 파일 IP → zioinfo.co.kr 치환 (소스/매뉴얼/설정/하네스)
- Manager DrConsole/NetworkConsole/CsapConsole 빌드 + /var/www/manager/ 배포
- 테스트: Manager HTTP 200, ITSM 신규 API 7개 전체 200

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-31 10:09:17 +09:00

559 B
Raw Blame History

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.