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

⬆️ Updates typedoc-plugin-markdown to v4 #2374

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 3, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
typedoc-plugin-markdown (source) ^3.10.2 -> ^4.0.0 age adoption passing confidence

Release Notes

typedoc2md/typedoc-plugin-markdown (typedoc-plugin-markdown)

v4.0.0

Compare Source

v4 is a major release that includes a number of bug fixes, new features and UI improvements.

Architectural Changes
  • Handlebars as a dependency has been removed.
  • Updated customization model with the ability to set hooks, events and custom theming.
  • Exposed navigation structure.
Features
  • Updated output file structure.
  • Improved and cleaner UI.
  • A set of updated and additional new options with comprehensive documentation.
  • Exported option types and JSON schema.
Structural Changes
  • Each module member is now output to its own file by default. See option --outputFileStrategy. To achieve the same output as v3 (whereby only Classes, Enums and Interfaces have their own file), set the option membersWithOwnFile option.
  • Parameters are output as a list by default. To achieve the same output as v3 (where parameters are output as a table), use option --parametersFormat=table.
Breaking Changes
  • Because the file structure has changed you may need to update any cross references to files in your documentation.
  • Setting theme to "markdown" is no longer required and should be removed.
  • The option indexTitle has been removed. Please use the "title.indexPage" key with option --textContentMappings.
  • The option allReflectionsHaveOwnDocument has been removed (this behaviour is now the default). Please see option outputFileStrategy](/docs/options#outputfilestrategy).
  • The option entryDocument has been renamed to entryFileName to better reflect its purpose.
  • The option namedAnchors has been renamed to useHTMLAnchors to better reflect its purpose.
  • The option hideInPageTOC has been removed. In-page TOC are no longer included by default. You can include in-page TOCs by using typedoc-plugin-remark and the remark-toc plugin.
  • The option objectLiteralTypeDeclarationStyle has been removed. Please use option --typeDeclarationFormat=list.
Bug Fixes
  • Duplication in callback/callable/function properties. (#​581).
  • @​experimental / @​internal annotations. (#​556)
  • Fix events output and strike-through deprecated items. (#​534)
  • Class static functions are no longer marked. (#​533)
  • @​example block not rendered with Headline (#​501)
  • Support for categories (#​499)
  • Correctly resolve package readme urls from member pages. (#​483)
  • Add the ability to add a separate frontmatter for readme file. (#​469)
  • Items in tables are not linkable. (#​463)
  • Custom i18n texts. (#​458)
  • How to improve the formatting for types?. (#​456)
  • How to change title format. (#​450)
  • Export Docusaurus plugin options type. (#​440)
  • How to export interface as a table. (#​403)
  • Broken Link caused by Typescript class being defined in an index file. (#​402)
  • Markdown plugin inserts unnecessary escape characters. (#​398)
  • Potential bug with optional function argument. (#​396)
  • Respect monorepo readmeFile configuration (#​383)
  • Embed all objects under a Module/Namespace onto single page. (#​338)
  • Extra spaces when merging lines in a table. (#​331)
  • Does not support namespace (or module) and interface with same name. (#​300)
  • Integration with VitePress? (#​287)
  • Typedoc comments with text wrapped in < and > breaks Docusaurus Markdown parser. (#​276)
  • Navigation support? (#​262)
  • Sidebar Category Support? (#​213)
  • Properties as Table like function properties. (#​109)
  • Provide a link/excerpt/screenshot to a demo/example rendered output (#​102)

Earlier changelog entries can be found in CHANGELOG_ARCHIVE.md.


Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Moscow, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 has been generated by Mend Renovate. View repository job log here.

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Copy link
Author

renovate bot commented May 3, 2024

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

Copy link

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@arkweid/lefthook@0.7.7 environment, shell 0 40.2 MB envek
npm/@material/button@4.0.0 None 0 253 kB abhiomkar
npm/@material/checkbox@4.0.0 None +1 589 kB abhiomkar
npm/@material/elevation@4.0.0 None 0 47.3 kB abhiomkar
npm/@material/layout-grid@4.0.0 None 0 90.5 kB abhiomkar
npm/@material/radio@4.0.0 None +1 424 kB abhiomkar
npm/@material/ripple@4.0.0 None +1 414 kB abhiomkar
npm/@material/switch@4.0.0 None +1 422 kB abhiomkar
npm/@material/theme@4.0.0 None 0 75.5 kB abhiomkar
npm/@material/typography@4.0.0 None 0 63.8 kB abhiomkar
npm/@semantic-release/github@7.2.3 filesystem, network +1 125 kB semantic-release-bot
npm/@semantic-release/npm@7.1.3 filesystem +1 48.7 kB semantic-release-bot
npm/@semantic-release/release-notes-generator@9.0.3 None +1 45.3 kB semantic-release-bot
npm/@types/d3-array@1.2.12 None 0 28.9 kB types
npm/@types/d3-scale@2.2.10 None 0 119 kB types
npm/@types/d3-shape@1.3.12 None 0 139 kB types
npm/@types/got@9.6.12 None 0 19.8 kB types
npm/@types/humps@2.0.6 None 0 6.66 kB types
npm/@types/jest@26.0.24 None 0 71.7 kB types
npm/@types/lodash.mergewith@4.6.9 None 0 3.21 kB types
npm/@types/minimatch@3.0.5 None 0 8.2 kB types
npm/@types/prettier@2.7.3 None 0 49.8 kB types
npm/@types/shelljs@0.8.15 None 0 49.4 kB types
npm/@types/winston@2.4.4 None 0 1.71 kB types
npm/@typescript-eslint/eslint-plugin@4.33.0 None +3 2.76 MB jameshenry
npm/@typescript-eslint/parser@4.33.0 None 0 71.5 kB jameshenry
npm/async-retry@1.3.3 None 0 5.21 kB leerobinson
npm/axios@0.21.4 environment, network +1 405 kB jasonsaayman
npm/bcryptjs@2.4.3 None 0 221 kB dcode
npm/boxen@5.1.2 None +1 30.1 kB sindresorhus
npm/brotli-size@4.0.0 filesystem 0 140 kB erwinmombay
npm/canvas@2.8.0 filesystem +1 802 kB linusu
npm/codecov@3.8.3 environment, filesystem, shell 0 83.9 kB thomasrockhu
npm/conventional-changelog-cli@2.2.2 None 0 34.7 kB oss-bot
npm/coveralls@3.1.1 environment, filesystem, shell Transitive: eval +3 693 kB nickmerwin
npm/crypto@1.0.1 None 0 778 B ehsalazar
npm/cuid@2.1.8 None 0 27.2 kB ericelliott
npm/d3-array@1.2.4 None 0 103 kB mbostock
npm/d3-scale@2.2.2 None 0 195 kB mbostock
npm/d3-shape@1.3.7 None 0 231 kB mbostock
npm/dateformat@4.6.3 None 0 20.7 kB chase-manning
npm/dayjs-precise-range@1.0.1 None 0 10.5 kB huangjinlin
npm/dayjs@1.11.11 None 0 666 kB iamkun
npm/del-cli@4.0.1 None 0 3.83 kB sindresorhus
npm/dockerfile_lint@0.3.4 environment, eval, filesystem 0 193 kB lphiri
npm/dotenv@10.0.0 environment, filesystem 0 24.9 kB motdotla
npm/env-cmd@10.1.0 environment, filesystem Transitive: shell +1 139 kB toddbluhm
npm/es6-promisify@7.0.0 None 0 6.5 kB mikehall314
npm/eslint-config-prettier@8.10.0 None 0 19.9 kB lydell
npm/eslint-plugin-github@4.10.2 Transitive: environment, filesystem, unsafe +1 8.45 MB githubbot
npm/eslint-plugin-import@2.29.1 filesystem, unsafe Transitive: environment +2 1.27 MB ljharb
npm/eslint-plugin-jest@24.7.0 filesystem 0 292 kB simenb
npm/eslint-plugin-node@11.1.0 filesystem +1 320 kB mysticatea
npm/eslint-plugin-prettier@3.4.1 filesystem 0 52.5 kB bpscott
npm/eslint-plugin-spellcheck@0.0.17 filesystem 0 2.56 MB aotaduy
npm/eslint@7.32.0 filesystem Transitive: environment, unsafe +16 4.12 MB eslintbot
npm/folio@0.3.18 filesystem Transitive: shell, unsafe +3 432 kB pavelfeldman
npm/fs-extra@10.1.0 Transitive: environment, filesystem +2 100 kB ryanzim
npm/functools-ts@1.0.3 None 0 129 kB chaabaj
npm/github-url-parse@0.1.0 None 0 8.1 kB stefanbuck
npm/got@11.8.6 filesystem, network +1 272 kB sindresorhus
npm/gradient-string@1.2.0 None 0 11.1 kB bokub
npm/grommet@2.37.0 environment 0 8.82 MB jcfilben
npm/gzip-size@6.0.0 filesystem +1 13.4 kB sindresorhus
npm/hasha@5.2.2 filesystem +2 79.9 kB sindresorhus
npm/isomorphic-unfetch@3.1.0 None +1 30.6 kB developit
npm/object-hash@2.2.0 None 0 59 kB addaleax
npm/opener@1.5.2 shell 0 6.21 kB domenic
npm/prettier@2.8.8 environment, filesystem, unsafe 0 11.2 MB prettier-bot

🚮 Removed packages: npm/is-regex@1.1.4, npm/js-sha256@0.9.0, npm/js-yaml@4.1.0, npm/mime-types@2.1.35, npm/mobx@6.12.3, npm/parse-json@5.2.0, npm/prettier@2.3.2, npm/slugify@1.6.6, npm/threads@1.6.5, npm/tiny-worker@2.3.0

View full report↗︎

Copy link

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSource
Install scripts npm/@arkweid/lefthook@0.7.7
  • Install script: postinstall
  • Source: node postinstall.js
Install scripts npm/canvas@2.8.0
  • Install script: install
  • Source: node-pre-gyp install --fallback-to-build
Potential typo squat npm/github-url-parse@0.1.0

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/@arkweid/lefthook@0.7.7
  • @SocketSecurity ignore npm/canvas@2.8.0
  • @SocketSecurity ignore npm/github-url-parse@0.1.0

Copy link

github-actions bot commented May 3, 2024

Thanks for opening an issue! Make sure you've followed CONTRIBUTING.md.

Copy link

github-actions bot commented May 3, 2024

Hello from PR Helper

Is your PR ready for review and processing? Mark the PR ready by including #pr-ready in a comment.

If you still have work to do, even after marking this ready. Put the PR on hold by including #pr-onhold in a comment.

Copy link

github-actions bot commented May 3, 2024

Thanks for the PR!

This section of the codebase is owner by https://github.com/AlexRogalskiy/ - if they write a comment saying "LGTM" then it will be merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants