1.0.0 (2024-12-28)
Bug Fixes
semantic-release
require node >= 18 (#55) (0d89a54)- checkboxes: correctly parse checkboxes when the template is wrong or missing (#71) (a87a2d9)
- deps: bump @actions/core from 1.10.0 to 1.10.1 (1747e32)
- deps: bump @actions/core from 1.10.1 to 1.11.1 (aff753a)
- deps: bump @actions/core from 1.9.1 to 1.10.0 (284e5eb)
- deps: bump @vercel/ncc from 0.38.2 to 0.38.3 (513fe55)
- Do not convert ids to dashes in output (#19) (6cfd00c)
- do not lowercase values (bee0997)
- do not publish
node_modules
folder (4bf5102) - Ensure releases can be pinned to SHAs #23 (#39) (428eec3)
- Fix issue with path construction on windows #22 (fb73b92)
- Handle correctly issues with an empty body (#34) (7da1c3a), closes #33
- handle linebreaks using
\\r\\n
(698f150) - multi paragraphs parsing (#15) (e78326b)
- package.json & package-lock.json to reduce vulnerabilities (#28) (53206f2)
- replace
"\_No Response\_"
values with with""
(6169285) - Revert "test: set
RUNNER_TEMP
instead ofHOME
" (#75) (4c1d1d7) - semantic-release setup (21b7212)
- semantic-release setup (#18) (44d26c5)
Features
- add issue-body default (#47) (741688b)
- mitigating script injection attacks by passing issue body as env var (#42) (0b27d4a)
- parse checkboxes (#21) (1d341cb)
- update to node20 (#70) (2ac1a18)
- using env.runner_temp instead of home directory to write json file (#59) (7296f08)
Reverts
BREAKING CHANGES
- Add
issue-body
argument which is required from v3 onwards
To mitigate script injection attacks, github-issue-parser v3 will require workflow authors to pass the issue body as an argument. By doing so you will follow GitHub's Good practices for mitigating script injection attacks
- uses: stefanbuck/github-issue-parser@v3
id: issue-parser
with:
issue-body: ${{ github.event.issue.body }} # required
template-path: .github/ISSUE_TEMPLATE/bug-report.yml # optional but recommended
- Before this change, IDs defined in a GitHub issue template that included a hyphen got converted to dashes for the Action output. This was mainly done to ensure nice-looking output variables. However, this is confusing as discussed in stefanbuck/github-issue-parser#15 (comment).