mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 04:46:56 +00:00
[GH-ISSUE #7850] [FR] Please use GitHub CI to build AppFlowy packages for Linux Arm64 architecture #3443
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#3443
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nissimk on GitHub (Apr 28, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7850
Description
The GitHub workflows create Linux packages for x64 architecture but not for Arm64. Having release packages available for Arm64 will unlock users on Raspberry pi, snapdragon X laptops and Chromebooks with ARM CPU architectures. I have successfully built from source on Arm64 and tested on Raspberry pi and chromeOS and I will send a pull request. I changed a .yml file in the .github folder and also a shell script in frontend/scripts. I can test the script but I don't know how to test the changes to the GitHub workflow. Should I submit the PR without testing the GitHub workflows change or is there some way that I can test it myself in my fork?
Impact
This will create release artifacts that can be installed on Raspberry pi, Snapdragon X laptops and Chromebooks with ARM cpu's.
Additional Context
No response
@LucasXu0 commented on GitHub (Apr 29, 2025):
@nissimk I'll do that.