Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 23, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
marked (source) ^4.2.12 -> ^9.0.0 age adoption passing confidence

Release Notes

markedjs/marked (marked)

v9.1.5

Compare Source

Bug Fixes

v9.1.4

Compare Source

Bug Fixes

v9.1.3

Compare Source

Bug Fixes

v9.1.2

Compare Source

Bug Fixes

v9.1.1

Compare Source

Bug Fixes

v9.1.0

Compare Source

Features

v9.0.3

Compare Source

Bug Fixes

v9.0.2

Compare Source

Bug Fixes

v9.0.1

Compare Source

Bug Fixes

v9.0.0

Compare Source

Bug Fixes
BREAKING CHANGES
    • remove built files from git repo.
    • If you need to use the latest version of marked on the web you can use a cdn to get marked.min.js from npm:
    • https://cdn.jsdelivr.net/npm/marked/marked.min.js

v8.0.1

Compare Source

Bug Fixes

v8.0.0

Compare Source

Bug Fixes
Features
BREAKING CHANGES

v7.0.5

Compare Source

Bug Fixes

v7.0.4

Compare Source

Bug Fixes

v7.0.3

Compare Source

Bug Fixes

v7.0.2

Compare Source

Bug Fixes

v7.0.1

Compare Source

Bug Fixes

v7.0.0

Compare Source

Bug Fixes
BREAKING CHANGES
  • change defaults for mangle and headerIds to false

v6.0.0

Compare Source

Bug Fixes
BREAKING CHANGES
  • Migrate to Typescript

v5.1.2

Compare Source

Bug Fixes

v5.1.1

Compare Source

Bug Fixes

v5.1.0

Compare Source

Bug Fixes
Features

v5.0.5

Compare Source

Bug Fixes

v5.0.4

Compare Source

Bug Fixes

v5.0.3

Compare Source

Bug Fixes

v5.0.2

Compare Source

Bug Fixes

v5.0.1

Compare Source

Bug Fixes
  • only warn if langPrefix is changed (#​2796) (d193694)
    The deprecated options warnings can be turned off by default by using:

    marked.use({
      mangle: false,
      headerIds: false,
    });

    For the cli you can use:

    marked --no-mangle --no-header-ids ...
    

v5.0.0

Compare Source

Bug Fixes
Features
BREAKING CHANGES
  • Warnings will be logged to the console if these options are used including headerIds, mangle, and langPrefix which are on by default.
    These warnings can be turned off by default by using:
    marked.use({
      mangle: false,
      headerIds: false,
    });
    If you need these options you can use the extensions listed below.
  • deprecate options
    Option Replacement
    highlight, langPrefix, and callback marked-highlight
    mangle marked-mangle
    baseUrl marked-base-url
    smartypants marked-smartypants
    xhtml marked-xhtml
    headerIds and headerPrefix marked-gfm-heading-id
  • minimum supported node version v18

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Oct 23, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: ngx-markdown@16.0.0
npm ERR! Found: marked@9.1.6
npm ERR! node_modules/marked
npm ERR!   marked@"^9.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer marked@"^4.3.0" from ngx-markdown@16.0.0
npm ERR! node_modules/ngx-markdown
npm ERR!   ngx-markdown@"^16.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: marked@4.3.0
npm ERR! node_modules/marked
npm ERR!   peer marked@"^4.3.0" from ngx-markdown@16.0.0
npm ERR!   node_modules/ngx-markdown
npm ERR!     ngx-markdown@"^16.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/2b52dc/626f35/cache/others/npm/_logs/2023-11-11T08_01_27_092Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/2b52dc/626f35/cache/others/npm/_logs/2023-11-11T08_01_27_092Z-debug-0.log

@renovate renovate bot force-pushed the renovate/marked-9.x branch from d321eea to 9a83a86 Compare October 24, 2023 10:42
@renovate renovate bot changed the title chore(deps): update dependency marked to v9 fix(deps): update dependency marked to v9 Oct 24, 2023
@renovate renovate bot force-pushed the renovate/marked-9.x branch 6 times, most recently from 08c5c15 to 14a44c5 Compare October 30, 2023 04:34
@renovate renovate bot force-pushed the renovate/marked-9.x branch 4 times, most recently from 6e27188 to 0a4e63f Compare November 8, 2023 21:34
@renovate renovate bot force-pushed the renovate/marked-9.x branch from 0a4e63f to fb7cf57 Compare November 11, 2023 00:49
@renovate renovate bot force-pushed the renovate/marked-9.x branch from fb7cf57 to 5487897 Compare November 11, 2023 08:01
@renovate renovate bot changed the title fix(deps): update dependency marked to v9 fix(deps): update dependency marked to v9 - autoclosed Nov 11, 2023
@renovate renovate bot closed this Nov 11, 2023
@renovate renovate bot deleted the renovate/marked-9.x branch November 11, 2023 08:05
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.

1 participant