Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump marked from 3.0.8 to 4.0.10 #1844

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 15, 2022

Bumps marked from 3.0.8 to 4.0.10.

Release notes

Sourced from marked's releases.

v4.0.10

4.0.10 (2022-01-13)

Bug Fixes

  • security: fix redos vulnerabilities (8f80657)

v4.0.9

4.0.9 (2022-01-06)

Bug Fixes

v4.0.8

4.0.8 (2021-12-19)

Bug Fixes

v4.0.7

4.0.7 (2021-12-09)

Bug Fixes

v4.0.6

4.0.6 (2021-12-02)

Bug Fixes

v4.0.5

4.0.5 (2021-11-25)

Bug Fixes

  • table after paragraph without blank line (#2298) (5714212)

v4.0.4

4.0.4 (2021-11-19)

... (truncated)

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [marked](https://github.com/markedjs/marked) from 3.0.8 to 4.0.10.
- [Release notes](https://github.com/markedjs/marked/releases)
- [Changelog](https://github.com/markedjs/marked/blob/master/.releaserc.json)
- [Commits](markedjs/marked@v3.0.8...v4.0.10)

---
updated-dependencies:
- dependency-name: marked
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@Gerrit0
Copy link
Collaborator

Gerrit0 commented Jan 15, 2022

FYI for those coming here because of the "high severity" vulnerability that is reported:

The vulnerability is a DOS caused by carefully crafted markdown. It can only happen to your project if you add markdown to trigger it. Last time I looked at upgrading marked was with the 4.0.0 release, which only shipped ESM. If they've fixed that so that TypeDoc doesn't have to be upgraded to ESM to upgrade Marked, I'm good with merging a PR which properly upgrades it.

@mikaello
Copy link

mikaello commented Jan 16, 2022

Last time I looked at upgrading marked was with the 4.0.0 release, which only shipped ESM. If they've fixed that so that TypeDoc doesn't have to be upgraded to ESM to upgrade Marked, I'm good with merging a PR which properly upgrades it.

I checked current version 4.0.10 and version 4.0.0, and both ship EMS + CJS + UMD:

$ npm install marked@4.0.0
$ ls node_modules/marked/lib
marked.cjs  marked.esm.js  marked.js

In v4.0.1 of marked, the main property in package.json was changed from lib/marked.ems.js to lib/marked.cjs:
markedjs/marked@v4.0.0...v4.0.1

stefanobaghino-da pushed a commit to stefanobaghino-da/typedoc that referenced this pull request Jan 17, 2022
Updates at superseding TypeStrong#1844
by bumping to a more recent `@types/marked` and fixing where breaking
changes happened.

Bumps [marked](https://github.com/markedjs/marked) from 3.0.8 to 4.0.10.
- [Release notes](https://github.com/markedjs/marked/releases)
- [Changelog](https://github.com/markedjs/marked/blob/master/.releaserc.json)
- [Commits](markedjs/marked@v3.0.8...v4.0.10)
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 18, 2022

Looks like marked is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Jan 18, 2022
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/marked-4.0.10 branch January 18, 2022 02:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants