diff options
-rw-r--r-- | .github/workflows/builds.yml | 12 | ||||
-rw-r--r-- | README.md | 9 | ||||
-rw-r--r-- | electron-builder.yml | 3 |
3 files changed, 7 insertions, 17 deletions
diff --git a/.github/workflows/builds.yml b/.github/workflows/builds.yml index fe24129ab..abc1b50d8 100644 --- a/.github/workflows/builds.yml +++ b/.github/workflows/builds.yml | |||
@@ -373,16 +373,14 @@ jobs: | |||
373 | env: | 373 | env: |
374 | GH_TOKEN: ${{ secrets.FERDIUM_PUBLISH_TOKEN }} | 374 | GH_TOKEN: ${{ secrets.FERDIUM_PUBLISH_TOKEN }} |
375 | CSC_IDENTITY_AUTO_DISCOVERY: true | 375 | CSC_IDENTITY_AUTO_DISCOVERY: true |
376 | # TODO: Commented out the code signing process for now (so as to at least get unsigned nightlies available for testing) | 376 | WIN_CSC_LINK: ${{ secrets.WIN_CSC_LINK }} |
377 | # WIN_CSC_LINK: ${{ secrets.WIN_CSC_LINK }} | 377 | WIN_CSC_KEY_PASSWORD: ${{ secrets.WIN_CSC_KEY_PASSWORD }} |
378 | # WIN_CSC_KEY_PASSWORD: ${{ secrets.WIN_CSC_KEY_PASSWORD }} | ||
379 | - name: Build Ferdium with publish for 'release' branch | 378 | - name: Build Ferdium with publish for 'release' branch |
380 | if: ${{ env.GIT_BRANCH_NAME == 'release' }} | 379 | if: ${{ env.GIT_BRANCH_NAME == 'release' }} |
381 | run: npm run build -- --publish always | 380 | run: npm run build -- --publish always |
382 | shell: bash | 381 | shell: bash |
383 | env: | 382 | env: |
384 | GH_TOKEN: ${{ secrets.FERDIUM_PUBLISH_TOKEN }} | 383 | GH_TOKEN: ${{ secrets.FERDIUM_PUBLISH_TOKEN }} |
385 | CSC_IDENTITY_AUTO_DISCOVERY: false | 384 | CSC_IDENTITY_AUTO_DISCOVERY: true |
386 | # TODO: Commented out the code signing process for now (so as to at least get unsigned nightlies available for testing) | 385 | WIN_CSC_LINK: ${{ secrets.WIN_CSC_LINK }} |
387 | # WIN_CSC_LINK: ${{ secrets.WIN_CSC_LINK }} | 386 | WIN_CSC_KEY_PASSWORD: ${{ secrets.WIN_CSC_KEY_PASSWORD }} |
388 | # WIN_CSC_KEY_PASSWORD: ${{ secrets.WIN_CSC_KEY_PASSWORD }} | ||
@@ -14,8 +14,6 @@ | |||
14 | - [Ferdium](#ferdium) | 14 | - [Ferdium](#ferdium) |
15 | - [Screenshots](#screenshots) | 15 | - [Screenshots](#screenshots) |
16 | - [Download](#download) | 16 | - [Download](#download) |
17 | - [Unsigned Nightlies on MacOS](#unsigned-nightlies-on-macos) | ||
18 | - [Unsigned Nightlies on Windows](#unsigned-nightlies-on-windows) | ||
19 | - [Migrating from Ferdi](#migrating-from-ferdi) | 17 | - [Migrating from Ferdi](#migrating-from-ferdi) |
20 | - [Contributing](#contributing) | 18 | - [Contributing](#contributing) |
21 | - [Contributors ✨](#contributors-) | 19 | - [Contributors ✨](#contributors-) |
@@ -54,13 +52,6 @@ Assets made available via [GitHub releases](https://github.com/ferdium/ferdium-a | |||
54 | 52 | ||
55 | _Find answers to frequently asked questions on [ferdium.org/faq](https://ferdium.org/faq)._ | 53 | _Find answers to frequently asked questions on [ferdium.org/faq](https://ferdium.org/faq)._ |
56 | 54 | ||
57 | ## Unsigned Nightlies on Windows | ||
58 | |||
59 | Similarly to the MacOS, we do not currently have a certificate to sign the nightlies on Windows. For this reason, an error will appear when launching the setup tool or the portable app if your execution policy is not set to `Bypass` or `Unrestricted`. In order to allow the script to run, it is sufficient to right-click on the `.exe` to access its properties and to tick the box labeled `Unblock` at the bottom of the General tab. Alternatively, you could execute the following in a PowerShell: | ||
60 | ```PowerShell | ||
61 | Unblock-File -Path .\Ferdium-Setup-6.0.0-nightly.xx.exe; .\Ferdium-Setup-6.0.0-nightly.xx.exe | ||
62 | ``` | ||
63 | |||
64 | ## Migrating from Ferdi | 55 | ## Migrating from Ferdi |
65 | 56 | ||
66 | If you are a pre-existing user of Ferdi, and are thinking of switching to Ferdium, you might want to run [the following scripts](./scripts/migration) to migrate your existing Ferdi profile such that Ferdium can pick up the configurations. (.ps1 for PowerShell/Windows users and .sh for UNIX (Linux and MacOS users) | 57 | If you are a pre-existing user of Ferdi, and are thinking of switching to Ferdium, you might want to run [the following scripts](./scripts/migration) to migrate your existing Ferdi profile such that Ferdium can pick up the configurations. (.ps1 for PowerShell/Windows users and .sh for UNIX (Linux and MacOS users) |
diff --git a/electron-builder.yml b/electron-builder.yml index a7763ebf0..93c59e52e 100644 --- a/electron-builder.yml +++ b/electron-builder.yml | |||
@@ -64,7 +64,8 @@ win: | |||
64 | arch: [x64, ia32] | 64 | arch: [x64, ia32] |
65 | - target: portable | 65 | - target: portable |
66 | arch: [x64, ia32] | 66 | arch: [x64, ia32] |
67 | publisherName: "Ferdium Contributors" | 67 | # The name of the CN appearing in the certificate must be present in the publisherName list below |
68 | publisherName: ["Ferdium Contributors", "Ambroise Grau"] | ||
68 | 69 | ||
69 | linux: | 70 | linux: |
70 | icon: ./build-helpers/images/icons | 71 | icon: ./build-helpers/images/icons |