Canary builds should use canary channel by default
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
If a canary build is installed from scratch, it should not be configured to have updates from stable channel.
The idea is to create a new config file that will override updateChannel setting in config-default.js. Something like conig-default.canary.js.
CI would use/copy this file before build app if this is a canary build.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading config-default.js and the CI build configuration to see how updateChannel is selected for canary builds. Check how a canary build is identified and how configuration files are copied before packaging. Done means a fresh canary installation defaults to the canary update channel without changing the stable build behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100