Action crashing on Github

[Gustavo-Ziaugra-Arvo]

The bug

Hi,
We just started to see this error this morning using the setup-beam step.

Do someone knows what may be going on?
Thanks in advance for this amazing action.
Zig

Software versions

 steps:
      - uses: actions/checkout@v4
      - uses: erlef/setup-beam@v1
        with:
          elixir-version: ${{needs.versions.outputs.elixir}}
          otp-version: ${{needs.versions.outputs.otp}}

[paulo-ferraz-oliveira]

Is this a self-hosted runner?

[paulo-ferraz-oliveira]

Doesn't break for me: https://github.com/paulo-ferraz-oliveira/setup-beam-example/actions/runs/15883789625/job/44790626318#step:3:2

So I'll need further information... Unfortunately I don't have self-hosted runners available so debugging is much harder. Can you create a minimal repo. where you try to isolate the issue?

[Gustavo-Ziaugra-Arvo]

@paulo-ferraz-oliveira Hi Paulo, we are not using a self-hosted runner, it just started randomly.

[sufyanadam]

Started seeing this same issue in our pipeline depending on this action today. We will lock down our version to last known working version

[Gustavo-Ziaugra-Arvo]

We just reverted to v1.19.0, looks to be working fine.

[Gustavo-Ziaugra-Arvo]

@paulo-ferraz-oliveira Here's a repo: https://github.com/Gustavo-Ziaugra-Arvo/setup-beam-bug-350/actions/runs/15884596302/job/44793311206

[paulo-ferraz-oliveira]

@paulo-ferraz-oliveira Here's a repo: https://github.com/Gustavo-Ziaugra-Arvo/setup-beam-bug-350/actions/runs/15884596302/job/44793311206

Cool. Can you check how that differs from the one I posted above and lemme know about the differences?

[sufyanadam]

@Gustavo-Ziaugra-Arvo I just confirmed in our repo reverting to v1.19.0 works

[paulo-ferraz-oliveira]

@paulo-ferraz-oliveira Hi Paulo, we are not using a self-hosted runner, it just started randomly.

I guess that you define ImageOS distracted me. That's typically only useful for self-hosted runners, since otherwise it's already given to us by GHA. And if you define that and then change runs-on I'm not sure what'll happen.

[paulo-ferraz-oliveira]

I'll test (in the above repo) with your workflow file verbatim.

[paulo-ferraz-oliveira]

Found a couple of things:

1. (not the issue, but) steps.node.outputs.node.value has an extra node
2. value=' shouldn't have the single quotes, which causes the issue 👀

I'm not sure this was a library update, but it's possible.

[paulo-ferraz-oliveira]

My latest test, where I have

        uses: erlef/setup-beam@v1
        with:
          # using a mix of single, quote and no-quote
          elixir-version: '1.18.4'
          otp-version: "27.3"
          rebar3-version: 3.25

passes, so this is some GitHub Actions -specific stuff when passing a value through the environment. I'm not sure we should support a hack for this, but I'll give it a thought regarding our tests...

⚠ In your pasted example, the code assumes the same as "'1'", which is wrong.

[paulo-ferraz-oliveira]

@Gustavo-Ziaugra-Arvo, @sufyanadam, is this the same case, that you're passing in versions that have '? Because if that's so, I'm not sure we should be messing with the consumer's input in trying to coerce versions to what they're not.

You're passing a string that is a single-quote -wrapped term, not a string.

[paulo-ferraz-oliveira]

The "issue", it seems, was introduced by #341 which is now stricter in the way the input is handled. I'll let this sit open, for a while, to gather more intel and consumer reports. I'd prefer to not have to deal with regexes where I don't have to, but that consumers fix their input, although I understand sometimes compromises are required if changes affect a big portion of the user base.