Bug: `unassigned_issues` is empty instead of `[]`

[koppor]

Describe the bug

I use edge

I output steps.unassign.outputs.unassigned_issues.

Expected: [] for no unassignments

Got: empty string.

Docs says, it should be array.

https://github.com/JabRef/jabref/blob/e0b95b31fe856bcc5a0f9c45507351f0a375b441/.github/workflows/unassign-issues.yml#L57

Steps to reproduce

see above

Browsers

No response

Additional context (Is this in dev or production?)

prod

Code of Conduct

• I agree to follow this project's Code of Conduct

Contributing Docs

• I agree to follow this project's Contribution Docs

[koppor]

Example run: https://github.com/JabRef/jabref/actions/runs/14314579233/job/40117620837

[koppor]

@takanome-dev should I change my workflow or would it be possible to update the edge version? 😅

[koppor]

Workaround: JabRef/jabref@2271c3b

-      unassigned_issues: ${{ steps.unassign.outputs.unassigned_issues }}
+      unassigned_issues: ${{ steps.unassign.outputs.unassigned_issues || '[]' }}