Skip to content

[Snyk] Upgrade @tailwindcss/typography from 0.5.10 to 0.5.13 #18

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.

Sign up for GitHub

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

Jump to bottom
Merged
hashim21223445 merged 1 commit into from
Jul 13, 2024
Merged

[Snyk] Upgrade @tailwindcss/typography from 0.5.10 to 0.5.13 #18

hashim21223445 merged 1 commit into from
Jul 13, 2024

Conversation

@hashim21223445
Copy link
Owner

@hashim21223445 hashim21223445 commented Jul 12, 2024

This PR was automatically created by Snyk using the credentials of a real user.


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade @tailwindcss/typography from 0.5.10 to 0.5.13.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

  • The recommended version is 3 versions ahead of your current version.

  • The recommended version was released on 3 months ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Inefficient Regular Expression Complexity
SNYK-JS-MICROMATCH-6838728		 300 No Known Exploit
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-ASYNC-7414156		 300 No Known Exploit
medium severity Cross-site Scripting (XSS)
SNYK-JS-PRISMJS-2404333		 300 No Known Exploit
Release notes
Package name: @tailwindcss/typography
  • 0.5.13 - 2024-04-26

    Fixed

    • Don't apply margins to <br> elements contained in an <li> in FF (#350)
  • 0.5.12 - 2024-03-27

    Added

    • Use logical properties for better RTL support (#323)
  • 0.5.11 - 2024-03-26

    Added

    • Add prose-kbd modifier (#340)

    Fixed

    • Fix space between <figcaption> and <video> (#339)
  • 0.5.10 - 2023-09-05

    Fixed

    • Fix space between <figcaption> and <pre> (#313)
    • Remove typography styles from not-prose elements in addition to their children (#301)
    • Add <picture> styles (#314)
    • Fix prose-invert when used with colors in light mode (#315)
    • Add <kbd> styles (#317)
    • Add description list (<dl>, <dt>, <dd>) styles (#316)
from @tailwindcss/typography GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

@snyk-bot
fix: upgrade @tailwindcss/typography from 0.5.10 to 0.5.13
cd888bd 
Snyk has created this PR to upgrade @tailwindcss/typography from 0.5.10 to 0.5.13.

See this package in npm:
@tailwindcss/typography

See this project in Snyk:
https://app.snyk.io/org/hashim21223445/project/08884ccd-eda2-4379-965b-3badf11ab9a0?utm_source=github&utm_medium=referral&page=upgrade-pr
@hashim21223445 hashim21223445 merged commit b0fdbf2 into main Jul 13, 2024
@hashim21223445 hashim21223445 linked an issue Jul 30, 2024 that may be closed by this pull request
Andoka morni tu hashim21223445/vuepress#34
Closed
@hashim21223445 hashim21223445 self-assigned this Aug 1, 2024
@hashim21223445 hashim21223445 added bug Something isn't working documentation Improvements or additions to documentation duplicate This issue or pull request already exists enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers invalid This doesn't seem right question Further information is requested dependencies Pull requests that update a dependency file merge when passing Merge the PR automatically once all status checks have passed patch version Automatically create a new patch version tag after PR is merged minor version Automatically create a new minor version tag after PR is merged major version Automatically create a new major version tag after PR is merged labels Aug 1, 2024
@hashim21223445 hashim21223445 added this to the A milestone Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@hashim21223445 hashim21223445

Labels

bug Something isn't working dependencies Pull requests that update a dependency file documentation Improvements or additions to documentation duplicate This issue or pull request already exists enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed invalid This doesn't seem right major version Automatically create a new major version tag after PR is merged merge when passing Merge the PR automatically once all status checks have passed minor version Automatically create a new minor version tag after PR is merged patch version Automatically create a new patch version tag after PR is merged question Further information is requested

Projects

None yet

Milestone

A

Development

Successfully merging this pull request may close these issues.

Andoka morni tu

3 participants

@hashim21223445 @snyk-bot