asfenis.blogg.se - Electron api document

Electron api document update#
Electron api document password#

Is determined and set automatically when publishing.Īcl = public-read “private” | “public-read” | “undefined” - The ACL. Region String | “undefined” - The region.

Electron api document password#

Is set programmatically explicitly during publishing.ĭefine BITBUCKET_TOKEN environment variable.įor converting an app password to a usable token, you can utilize this convertAppPassword( owner: string, token: string)

platform String | “undefined” - The target Platform.

Set to null to not add.ĭefine KEYGEN_TOKEN environment variable.

acl = public-read “private” | “public-read” | “undefined” - The ACL.

path = / String | “undefined” - The directory path.

Electron api document update#

channel = latest String | “undefined” - The update channel.channels = String | Array | “undefined” - The list of channels the snap would be released.Īccess key is required, define DO_KEY_ID and DO_SECRET_KEY environment variables.If EP_DRAFTis set to true - draft, if EP_PRE_RELEASEis set to true - prerelease. By default draft release will be created.Īlso you can set release type using environment variable. ReleaseType = draft “draft” | “prerelease” | “release” | “undefined” - The type of release. See Private GitHub Update Repo.Ĭhannel = latest String | “undefined” - The channel. Private Boolean | “undefined” - Whether to use private github auto-update provider if GH_TOKEN environment variable is defined. Never specify it in the configuration files. Token String | “undefined” - The access token to support auto-update from private github repositories. Protocol = https “https” | “http” | “undefined” - The protocol.

Host = String | “undefined” - The host (including the port if need). VPrefixedTagName = true Boolean - Whether to use v-prefixed tag name. Repo String | “undefined” - The repository name. The access token should have the repo scope/permission. GitHub personal access token is required. RequestHeaders module:http.OutgoingHttpHeaders - Any custom request headers Thus, probably, there`s no need to upload the metadata files for the other configured providers. PublishAutoUpdate = true Boolean - Whether to publish auto update info files.Īuto update relies only on the first provider in the list (you can specify several publishers). Defaults to true if url doesn’t contain s3.

useMultipleRangeRequest Boolean - Whether to use multiple range requests for differential update.

channel = latest String | “undefined” - The channel.

In all publish options File Macros are supported.

or CIRCLE_PROJECT_USERNAME/ CIRCLE_PROJECT_REPONAME,.

repository in the application or development package.json,.

Change the version back to a snapshot version right after, i.e.

Usually you’ll git-tag this version as well (just to keep track of it). This will then produce a latest.yml and something.exe on s3.

When you are ready to deploy, simply change you package version to 1.9.0 and push.

This will publish a file named snapshot.yml and a build named something-snapshot.exe (and corresponding for mac) to S3.

Set your version in your application package.json to 1.9.0-snapshot (or 1.9.0-master or whatever you want your development channel to be named).

"dist": "electron-builder -publish always" in your package.json.

Setup your CI to publish on each commit.

This example workflow is modelled on how releases are handled in maven (it is an example of one of many possible workflows, you are not forced to follow it). Continuous Deployment Workflow on Amazon S3 and other non-GitHub ¶ The benefit of this workflow is that it allows you to always have the latest artifacts, and the release can be published once it is ready.

GitHub will tag the latest commit for you. Once you are done, publish the release.Every CI build will update the artifacts attached to this draft. “Release title” can be anything you want.įor example, if your application package.json version is 1.0, your draft’s “Tag version” would be v1.0. Set the “Tag version” to the value of version in your application package.json, and prefix it with v. Recommended GitHub Releases Workflow ¶ĭraft a new release. And if you run yarn release, a release will be drafted (if doesn’t already exist) and artifacts published.