Skip to content

[erlang][elixir] support arch transitions and constraints#25

Merged
denbeigh2000 merged 7 commits intomainfrom
denbeigh/platform-independent-output-no-example
Apr 6, 2026
Merged

[erlang][elixir] support arch transitions and constraints#25
denbeigh2000 merged 7 commits intomainfrom
denbeigh/platform-independent-output-no-example

Conversation

@denbeigh2000
Copy link
Copy Markdown
Member

This ensures we can build elixir for the appropriate platform, makes
use of the newly-introduced erlang_version setting from rules_erlang
(to prevent OTP version mismatches), and also adds an elixir_version setting,
so we can be sure we're not mixing and matching compiled code between
different versions of elixir.

@denbeigh2000 denbeigh2000 force-pushed the denbeigh/platform-independent-output-no-example branch 3 times, most recently from 3229057 to f9fd9a3 Compare April 3, 2026 21:02
@denbeigh2000 denbeigh2000 force-pushed the denbeigh/platform-independent-output-no-example branch from f9fd9a3 to c69d22a Compare April 3, 2026 21:19
@denbeigh2000 denbeigh2000 merged commit bb00505 into main Apr 6, 2026
0 of 4 checks passed
denbeigh2000 added a commit that referenced this pull request Apr 9, 2026
When we [split bytecode and priv
management](86a1136#diff-c5b4474261f9b757de19feb613663baf601ce6c946953fb1860820d13ea1ac7cR252)
in #25, we introduced a regression where we stopped copying priv assets
in `mix_release`, because artifacts are no longer in one, big, happy
tree 🧑‍🎨

This changeset ensures they are copied to the output release directory.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant