Releases: stefanbuck/github-issue-parser
Releases · stefanbuck/github-issue-parser
v3.2.1
v3.2.0
v3.1.1
v3.0.1
What's Changed
- feat: add issue-body default by @joshjohanning in #47
New Contributors
- @joshjohanning made their first contribution in #36
Full Changelog: v3.0.0...v3.0.1
v2.0.6
- Update node.js to use v16
BREAKING CHANGES
Original this change was meant for v3, but it slipped into this release. See #50 and #21 for details.
The previous checkbox output produced this:
{
"laravel": true,
"svelte": true,
}
whereas the new checkbox output will be an array like this
{
"fav_frameworks": ["Laravel", "Svelte"]
}
Full Changelog: v2.0.5...v2.0.6
v2.0.5
What's Changed
- build(deps-dev): bump jest from 28.1.3 to 29.0.1 by @dependabot in #35
- document the issueparser_ outputs by @joshjohanning in #36
- fix: Ensure releases can be pinned to SHAs by @stefanbuck in #39
- doc: Add example
advanced-issue-labeler
by @jamacku in #40 - build(deps-dev): bump jest from 29.0.1 to 29.1.2 by @dependabot in #44
Full Changelog: v2.0.3...v2.0.5
v3.0.0
3.0.0 (2022-10-19)
Bug Fixes
- deps: bump @actions/core from 1.9.1 to 1.10.0 (284e5eb)
- Ensure releases can be pinned to SHAs #23 (#39) (428eec3)
Features
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
The previous checkbox output produced this:
{
"laravel": true,
"svelte": true,
}
whereas the new output will be an array like this
{
"fav_frameworks": ["Laravel", "Svelte"]
}