Bump marked and jsdoc-to-markdown
Bumps marked to 4.3.0 and updates ancestor dependency jsdoc-to-markdown. These dependencies need to be updated together.
Updates marked from 0.7.0 to 4.3.0
Release notes
Sourced from marked's releases.
v4.3.0
4.3.0 (2023-03-22)
Bug Fixes
- always return promise if async (#2728) (042dcc5)
- fenced code doesn't need a trailing newline (#2756) (3acbb7f)
Features
v4.2.12
4.2.12 (2023-01-14)
Sorry for all of the quick releases. We were testing out different ways to build the files for releases. v4.2.5 - v4.2.12 have no changes to how marked works. The only addition is the version number in the comment in the build files.
Bug Fixes
- revert to build script in ci (d2ab474)
v4.2.11
4.2.11 (2023-01-14)
Bug Fixes
- just build in version (22ac2cf)
v4.2.10
4.2.10 (2023-01-14)
Bug Fixes
- use version (fd759b3)
v4.2.9
4.2.9 (2023-01-14)
Bug Fixes
- fix version (96380c3)
... (truncated)
Commits
d65cf63chore(release): 4.3.0 [skip ci]28f4342🗜️ build v4.3.0 [skip ci]9b452bcfeat: add preprocess and postprocess hooks (#2730)042dcc5fix: always return promise if async (#2728)3acbb7ffix: fenced code doesn't need a trailing newline (#2756)d1f1319chore(deps-dev): Bump rollup from 3.19.1 to 3.20.0 (#2760)0ced8a5chore(deps-dev): Bump jasmine from 4.5.0 to 4.6.0 (#2758)a5bbe19chore(deps-dev): Bump@babel/corefrom 7.21.0 to 7.21.3 (#2761)00f6e2achore(deps-dev): Bump semantic-release from 20.1.1 to 20.1.3 (#2759)8c7bca8chore(deps-dev): Bump node-fetch from 3.3.0 to 3.3.1 (#2754)- Additional commits viewable in compare view
Updates jsdoc-to-markdown from 5.0.3 to 8.0.0
Release notes
Sourced from jsdoc-to-markdown's releases.
v8.0.0
Breaking change since 7.1.1
- Upgraded jsdoc-api which now uses jsdoc version v4.0.0 internally. From v4.0.0 onward, jsdoc requires Node v12. This was a breaking change for jsdoc but not for jsdoc2md as it already requires v12+, however this jsdoc2md release is a major version increment just to be on the safe side.
Minor Updates
- Upgraded dmd which now uses marked v4.2.3
v7.1.0
- Restored support for Node v12
v7.0.0
This is a refresher release - there are no API or functional changes.
Breaking change
- Dropped support for Node.js versions less than v14.
Minor updates
- Refreshed dependency tree.
v6.0.0
Breaking changes since v5.0.0
- Node versions less than v10 are no longer supported
Other fixes
- Fixed crash when generating very large documentation sets using
renderSyncjsdoc2md/jsdoc-api#21- All dependencies upgraded
Commits
efcc8278.0.01afddcbupgrade deps, dates, CIf0ff0acMerge pull request #275 from KonkenBonken/patch-1c3e6b0aUpdated expired urle9fe5e57.1.1029c198update deps and datesfec2ec77.1.00f0eba1extend support back to Node.js v12.17261af7bMerge pull request #258 from martijnversluis/update-jsdoc-api-to-7.1.09c5ae4dUpdate jsdoc-api to 7.1.0- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.