vercel/hyper

Canary builds should use canary channel by default

Open

#2704 opened on Feb 24, 2018

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (44,582 stars) (3,558 forks)batch import
help wanted🎨 Type: Enhancement

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

Tech stack
typescriptelectronreact
Domain
desktoprelease
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with Hyper's build systemBasic knowledge of CI/CD
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The issue suggests creating a new config file (e.g., config default.canary.js) to override the updateChannel setting from config default.js. Investigate how CI currently determines whether a build is canary and how it could copy or use the new config file before building. Look into the existing config default.js and any build scripts to understand the current flow.