Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
It will be based off coho nightly. Multi-step process. Proposal below. Still figuring out some details (what to pass in). Feel free to comment and provide feedback.
Step 1) coho prepare-tools-release --jira ISSUENUMBER
- Use latest tags in platform repos; use in platformsConfig.json
- Include cordova-js & plugman (nightlies don't)(cordova-js: only if changes exist)
- Update package.json files + relevant dependencies
- npm link relevant repos
- run tests
- generate release notes for tools repos
- Ask user for manual curation for changes in release notes
Step 2) coho publish-tools --rc --jira ISSUENUMBER
- branch tools repos (no need to cherry-pick release log changes)
- update versions on master with -dev
- Commit changes
- Build archive
- publish archive to npm under rc tag
- publish to dist/dev
Step 3) (manual for now)
- Start vote thread
- close vote thread
Step 4) coho publish-tools --final --jira ISSUENUMBER
- Publish to dist & delete dist/dev
- Change npm latest tags to point to new versions
Not including for now:
- Generating issue on Jira (should be done manually pre step 1)
- Pinning dependencies (should be done manually pre step 1)
- license checks (should be done manually pre step 1)
- audit-license-headers (should be done manually pre step 1)
- Changes to docs.cordova.io
- Creating blog post
Attachments
Issue Links
- depends upon
-
CB-7904 Built nightly releases using coho
- Closed