Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ ret (0.3.1 → 0.3.2) · Repo
Release Notes
0.3.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 14 commits:
chore(ci): use semantic-release for auto publish and releasechore(package): fix pointing to main compiled entry pointchore(ci): update action versionsfix: fix parsing class ranges that contain square brackets and backslashes (#29)chore(lint): add eslint config, script, and workflowdocs(readme): use shields badgerefactor: typescript conversion (#24)chore(package): add author emailchore(ci): drop support for node 4, 6, 8chore: add security contact informationtest(coverage): remove istanbul, use nycchore(ci): use github actionschore: add FUNDING.ymlrefactor: use arrow functions and `let`Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands