Fix publish workflow - #12
Merged
Merged
Conversation
The workflow was using an action for the publish which uses an hard-coded, old (1.11) version of Elixir, which now fails with the following error: ``` ** (Mix) You're trying to run :opentelemetry_function on Elixir v1.11.3 but it has declared in its mix.exs file it supports only Elixir ~> 1.12 ``` Because the publishing itself is essentially just a `mix hex.publish` call, then this workflow now uses a similar structure to the CI workflow to set everything up and call the publish function, avoiding the need for using third-party action for the publish.
nsalong
approved these changes
Mar 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The workflow was using an action for the publish which uses an
hard-coded, old (1.11) version of Elixir, which now fails with the
following error:
Because the publishing itself is essentially just a
mix hex.publishcall, then this workflow now uses a similar structure to the CI workflow
to set everything up and call the publish function, avoiding the need
for using third-party action for the publish.