Skip to content

Commit

Permalink
Build only Mac x64 for the current releases (#1659)
Browse files Browse the repository at this point in the history
  • Loading branch information
gagik authored Jun 7, 2024
1 parent acd925e commit ac93be2
Show file tree
Hide file tree
Showing 3 changed files with 16 additions and 6 deletions.
4 changes: 2 additions & 2 deletions .github/workflows/publish-release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -186,7 +186,7 @@ jobs:
# update mechanism
- name: Prepare installer contents
run: |
npx electron-builder -m --publish never --c.mac.target=zip --c.mac.identity=null
npx electron-builder -m --publish never --c.mac.target=zip --c.mac.identity=null --x64
#npx electron-builder -m --publish never --c.mac.target=zip --c.mac.identity=null --universal
# Renaming the .zip to make it easier to distinguish
mv dist/*.zip dist/unsigned-app.zip
Expand All @@ -203,7 +203,7 @@ jobs:
#unzip -d dist/mac-universal -o output.zip
- name: Build installers
run: |
npx electron-builder -m --publish never --pd "dist/mac/Realm Studio.app"
npx electron-builder -m --publish never --pd "dist/mac/Realm Studio.app" --x64
#npx electron-builder -m --publish never --universal --pd "dist/mac-universal/Realm Studio.app"
- name: Rename yaml files
run: |
Expand Down
11 changes: 11 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,16 @@
# Changelog

## vNext (TBD)

### Enhancements
* None

### Fixed
* None

### Internals
* None

## 15.1.0 (2024-06-07)

### Enhancements
Expand Down
7 changes: 3 additions & 4 deletions docs/RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,17 +20,16 @@ When preparing the action does the following:

## Release a prepared release

Currently the release building is triggered manually after merging the release PR, using the "Build, sign and publish
release" workflow. Once everything is confirmed stable merging of the release PR can be added to that workflow to
eliminate one step.
Currently the release building is meant to be triggered by using the "Build, sign and publish release" workflow and selecting the release PR.

This workflow:

1. Builds and signs artifacts for macOS, Linux and Windows
2. Extract the latest release notes from the changelog.
3. Uploads the packaged artifacts and auto-update yaml files to S3
4. Creates a GitHub release, with the artifacts attached.
5. Announces the release on Slack.
5. Merges the release PR.
6. Announces the release on Slack.

# How do I roll-back a release?

Expand Down

0 comments on commit ac93be2

Please sign in to comment.