changeset-bot[bot]
commented
3 months ago 🦋 Changeset detected
Latest commit: 08d986ea98e2af6904f502c863ede1f51e14070e
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 9 packages
| Name | Type | | --------------------------------- | ----- | | electron-publish | Major | | app-builder-lib | Major | | dmg-builder | Major | | electron-builder-squirrel-windows | Major | | electron-builder | Major | | electron-forge-maker-appimage | Major | | electron-forge-maker-nsis-web | Major | | electron-forge-maker-nsis | Major | | electron-forge-maker-snap | Major |Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
netlify[bot]
mmaietta
AndrewEQ
Reference: https://github.com/electron-userland/electron-builder/issues/5688 - Discussion about keeping two separate tokens; one for publishing to Github releases and the other used by the app to make requests for auto-update updates.
Now you can set a release token that has write permissions to publish your release.
The release token will be used instead of a GH_TOKEN || GITHUB_TOKEN ONLY during publishing.
The Github token defined via the Github options or environment variable will still be used as normal.
mac:
export GITHUB_RELEASE_TOKEN=<my token>I used the Contents permission for a New fine-grained personal access token with "Read and write". "Read-only" for the usual app-update token.
So even if the app-update token is inside your app-update.yml its only read-only, yay! (Mac: you can find the app-update.yml by right-click > Show Package Contents > Contents > Resources)