You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[bug] Regression in 4.2.0 -- download-path is no longer populated if no artifacts are found with pattern match #390
Using the v4 tag broke automation that relies on the download-path output always being populated. I've determined this to be a regression in v4.2.0 release that was just put out -- where if an inputs.pattern matches no artifacts, the output is left empty instead of being populated.
This is a behavioral regression from a minor tag bump
What did you expect to happen?
I expect an output to still exist.
More formally, I expect no behavioral regressions when relying on a minor version update -- as per semantic versioning.
How can we reproduce it?
Run a workflow that uses a pattern and matches on no artifacts. The output in v4.2.0 is empty, but in v4.1.* and before is non-empty.
Nothing more to say on the ticket, though I'm interested in whether this was a deliberate change, and whether the output-path was not meant to be reliable when no artifacts are discovered? Was I relying on an implicit behavior I shouldn't have been?
What version of the action are you using?
v4.2.0
What are your runner environments?
linux
Are you on GitHub Enterprise Server? If so, what version?
Activity
bitwizeshift commentedon Mar 18, 2025
From the release-notes on 4.2.0, I am assuming #383 is likely responsible for this regression since the other change only changes the
README.mdfile.CC @JoannaaKL since it appears you merged this PR and kicked off the release.
GhadimiR commentedon Mar 19, 2025
👋 Thanks for reporting this issue! We've rolled
v4back tov4.1.9and are working on a fix.bitwizeshift commentedon Mar 19, 2025
Thank you so much for the quick action on this!