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

fix(deps): update dependency marked to v15 #3499

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 10, 2024

This PR contains the following updates:

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

Release Notes

markedjs/marked (marked)

v15.0.0

Compare Source

Bug Fixes
BREAKING CHANGES
  • escape html in renderers instead of tokenizers for all tokens.

v14.1.4

Compare Source

Bug Fixes

v14.1.3

Compare Source

Bug Fixes

v14.1.2

Compare Source

Bug Fixes

v14.1.1

Compare Source

Bug Fixes

v14.1.0

Compare Source

Bug Fixes
Features

v14.0.0

Compare Source

Bug Fixes
BREAKING CHANGES
  • Remove old renderer
  • throw an error if async: false is set when an extension sets async: true

v13.0.3

Compare Source

Bug Fixes
  • fix recursion-like stack overflow error caused by the old render… (#​3380) (89af0b8)

v13.0.2

Compare Source

Bug Fixes

v13.0.1

Compare Source

Bug Fixes

v13.0.0

Compare Source

Bug Fixes
  • Fix blockquote code continuation (#​3264) (7ab8185)
  • Add parser as a property on the Renderer object (#​3291)
  • Send block text tokens to the text renderer (#​3291)
Features
  • Send token objects to renderers (#​3291) (1ce59ea)
  • Add space renderer that returns empty string by default (#​3291)
  • Add header and align properties to TableCell token (#​3291)
  • Add TableRow token (#​3291)
  • Add Checkbox token (#​3291)
BREAKING CHANGES
  • Add space token after blockquote and hr if there are multiple newlines
  • Send token objects to renderers and move logic to parse tokens from the parser to the renderers.
    • Most extensions that update marked renderers should still work with this version but will break in a future major version.

    • Extensions that change marked renderers will need to be updated and use new option useNewRenderer and accept a token object instead of multiple parameters. See updated Renderer docs

      // v12 renderer extension
      
      const extension = {
        renderer: {
          heading(text, level) {
            // increase level by 1
            return `<h${level + 1}>${text}</h${level + 1}>`;
          }
        }
      };
      
      marked.use(extension);
      // v13 renderer extension
      
      const extension = {
        useNewRenderer: true,
        renderer: {
          heading(token) {
            // increase depth by 1
            const text = this.parser.parseInline(token.tokens);
            const level = token.depth;
            return `<h${level + 1}>${text}</h${level + 1}>`;
          }
        }
      };
      
      marked.use(extension);

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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Nov 10, 2024

⚠️ 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: marked-terminal@7.2.1
npm error Found: marked@15.0.4
npm error node_modules/marked
npm error   marked@"^15.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer marked@">=1 <15" from marked-terminal@7.2.1
npm error node_modules/marked-terminal
npm error   marked-terminal@"^7.0.0" from the root project
npm error   marked-terminal@"^7.0.0" from semantic-release@24.2.0
npm error   node_modules/semantic-release
npm error     peer semantic-release@">=20.1.0" from @semantic-release/commit-analyzer@13.0.0
npm error     node_modules/@semantic-release/commit-analyzer
npm error       @semantic-release/commit-analyzer@"^13.0.0-beta.1" from the root project
npm error       1 more (semantic-release)
npm error     3 more (@semantic-release/github, @semantic-release/npm, @semantic-release/release-notes-generator)
npm error
npm error Conflicting peer dependency: marked@14.1.4
npm error node_modules/marked
npm error   peer marked@">=1 <15" from marked-terminal@7.2.1
npm error   node_modules/marked-terminal
npm error     marked-terminal@"^7.0.0" from the root project
npm error     marked-terminal@"^7.0.0" from semantic-release@24.2.0
npm error     node_modules/semantic-release
npm error       peer semantic-release@">=20.1.0" from @semantic-release/commit-analyzer@13.0.0
npm error       node_modules/@semantic-release/commit-analyzer
npm error         @semantic-release/commit-analyzer@"^13.0.0-beta.1" from the root project
npm error         1 more (semantic-release)
npm error       3 more (@semantic-release/github, @semantic-release/npm, @semantic-release/release-notes-generator)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-12-23T05_09_10_335Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-23T05_09_10_335Z-debug-0.log

@renovate renovate bot force-pushed the renovate/marked-15.x branch 7 times, most recently from 0e2a54e to 0e05911 Compare November 18, 2024 03:19
@renovate renovate bot force-pushed the renovate/marked-15.x branch 10 times, most recently from eaf4bd4 to f14470b Compare November 25, 2024 04:13
@renovate renovate bot force-pushed the renovate/marked-15.x branch 3 times, most recently from 90abe1c to 7704c04 Compare December 2, 2024 04:22
@renovate renovate bot force-pushed the renovate/marked-15.x branch 4 times, most recently from 250eea3 to 2c1105f Compare December 9, 2024 05:27
@renovate renovate bot force-pushed the renovate/marked-15.x branch 5 times, most recently from b3991fb to 10c0ed0 Compare December 16, 2024 03:51
@renovate renovate bot force-pushed the renovate/marked-15.x branch 5 times, most recently from d207fb7 to 0962fa5 Compare December 21, 2024 02:19
@renovate renovate bot force-pushed the renovate/marked-15.x branch from 0962fa5 to bc79892 Compare December 23, 2024 05:09
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.

0 participants