github-starred/awesome-docker
2
0
Fork 0
mirror of https://github.com/veggiemonk/awesome-docker.git synced 2026-03-09 07:25:57 -05:00
Code Issues 5 Packages Projects Releases 1 Wiki Activity

[PR #977] [MERGED] Bump showdown from 1.9.1 to 2.0.0 #991

New Issue
Closed
opened 2025-11-06 12:12:27 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-06 12:12:27 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/veggiemonk/awesome-docker/pull/977
Author: @dependabot[bot]
Created: 2/16/2022
Status: ✅ Merged
Merged: 2/16/2022
Merged by: @mashb1t

Base: master ← Head: dependabot/npm_and_yarn/showdown-2.0.0

📝 Commits (1)

  • 12228cf Bump showdown from 1.9.1 to 2.0.0

📊 Changes

2 files changed (+160 additions, -308 deletions)

View changed files

📝 package-lock.json (+159 -307)
📝 package.json (+1 -1)

📄 Description

Bumps showdown from 1.9.1 to 2.0.0.

Release notes

Sourced from showdown's releases.

2.0.0 (2022-02-15)

2.0.0 (2022-02-15)

2.0.0 is mostly a maintenance release. There are only a few changes beyond 1.9.1 as noted below. The major driver of this update is to update the yargs dependency to a more recent version without security issues.

Breaking Changes

  • Supported Node Versions were set to match the node release schedule which at the time of writing includes Node 12.x, 14.x, 16.x and 17.x
  • The yargs dependency was updated to ^17.2.1 to mitigate a security issue.
  • The Showdown license has been changed from BSD-3-Clause to MIT

Bug Fixes

Features

  • Added ellipsis option to configure if the ellipsis unicode character is used or not. ( Thanks @​VladimirV99 )
  • Added a default security policy. Please report security issues to the issues tab on GitHub.

2.0.0-alpha (2022-02-01)

2.0.0-alpha (2022-02-02)

2.0.0-alpha is mostly a maintenance release. There are only a few changes beyond 1.9.1 as noted below. The major driver of this update is to update the yargs dependency to a more recent version without security issues.

Breaking Changes

  • Supported Node Versions were set to match the node release schedule which at the time of writing includes Node 12.x, 14.x, 16.x and 17.x
  • The yargs dependency was updated to ^17.2.1 to mitigate a security issue.
  • The Showdown license has been changed from BSD-3-Clause to MIT

Bug Fixes

Features

    • Added ellipsis option to configure if the ellipsis unicode character is used or not. ( Thanks @​VladimirV99 )
Changelog

Sourced from showdown's changelog.

2.0.0 (2022-02-15)

Breaking Changes

  • Supported Node Versions were set to match the node release schedule which at the time of writing includes Node 12.x, 14.x, 16.x and 17.x
  • The yargs dependecy was updated to ^17.2.1 to mitigate a security issue.
  • The Showdown Licesnse has been changed from BSD-3-Clause to MIT

Bug Fixes

Features

  • Added ellipsis option to configure if the ellipsis unicode character is used or not. ( Thanks @​VladimirV99 )
  • Added a default security policy. Please report security issues to the issues tab on GitHub.

Commits
  • 32a1aaa chore(build): version 2.0.0
  • 97a7696 doc(security): add a security policy
  • e5f419b build: prep and create a 2.0.0-alpha release
  • 366ef28 fix(extension-registering) removeExtension implementation
  • 6ea6bbf Including QCObjects in "Who uses Showdown"-README (#744)
  • a931cc2 docs: clear ambiguity about CDN usage
  • 62636d0 feature(ellipsis): Add option to disable ellipsis
  • b432da1 fix reference link impostors
  • b03e34a rename test files to match convention
  • 525b65f preserve spaces between inline elements
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by syntaxrules, a new releaser for showdown since your current version.


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)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/veggiemonk/awesome-docker/pull/977 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 2/16/2022 **Status:** ✅ Merged **Merged:** 2/16/2022 **Merged by:** [@mashb1t](https://github.com/mashb1t) **Base:** `master` ← **Head:** `dependabot/npm_and_yarn/showdown-2.0.0` --- ### 📝 Commits (1) - [`12228cf`](https://github.com/veggiemonk/awesome-docker/commit/12228cfcd90cb0637d78043ab4e0109e939d9213) Bump showdown from 1.9.1 to 2.0.0 ### 📊 Changes **2 files changed** (+160 additions, -308 deletions) <details> <summary>View changed files</summary> 📝 `package-lock.json` (+159 -307) 📝 `package.json` (+1 -1) </details> ### 📄 Description Bumps [showdown](https://github.com/showdownjs/showdown) from 1.9.1 to 2.0.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/showdownjs/showdown/releases">showdown's releases</a>.</em></p> <blockquote> <h2>2.0.0 (2022-02-15)</h2> <h1><a href="https://github.com/showdownjs/showdown/compare/1.9.1...2.0.0">2.0.0</a> (2022-02-15)</h1> <p>2.0.0 is mostly a maintenance release. There are only a few changes beyond 1.9.1 as noted below. The major driver of this update is to update the yargs dependency to a more recent version without security issues.</p> <h3>Breaking Changes</h3> <ul> <li>Supported Node Versions were set to match the <a href="https://nodejs.org/en/about/releases/">node release schedule</a> which at the time of writing includes Node 12.x, 14.x, 16.x and 17.x</li> <li>The <code>yargs</code> dependency was updated to <code>^17.2.1</code> to mitigate a security issue.</li> <li>The Showdown license has been changed from BSD-3-Clause to MIT</li> </ul> <h3>Bug Fixes</h3> <ul> <li>allow escaping of colons (<a href="https://github.com/showdownjs/showdown/commit/25c4420">25c4420</a>)</li> <li>reduce npm package size (<a href="https://github.com/showdownjs/showdown/commit/35730b7">35730b7</a>), closes <a href="https://github-redirect.dependabot.com/showdownjs/showdown/issues/619">#619</a></li> </ul> <h3>Features</h3> <ul> <li>Added <code>ellipsis</code> option to configure if the ellipsis unicode character is used or not. ( Thanks <a href="https://github.com/VladimirV99"><code>@​VladimirV99</code></a> )</li> <li>Added a default security policy. Please report security issues to the issues tab on GitHub.</li> </ul> <h2>2.0.0-alpha (2022-02-01)</h2> <h1><a href="https://github.com/showdownjs/showdown/compare/1.9.1...2.0.0-alpha">2.0.0-alpha</a> (2022-02-02)</h1> <p>2.0.0-alpha is mostly a maintenance release. There are only a few changes beyond 1.9.1 as noted below. The major driver of this update is to update the yargs dependency to a more recent version without security issues.</p> <h3>Breaking Changes</h3> <ul> <li>Supported Node Versions were set to match the <a href="https://nodejs.org/en/about/releases/">node release schedule</a> which at the time of writing includes Node 12.x, 14.x, 16.x and 17.x</li> <li>The <code>yargs</code> dependency was updated to <code>^17.2.1</code> to mitigate a security issue.</li> <li>The Showdown license has been changed from BSD-3-Clause to MIT</li> </ul> <h3>Bug Fixes</h3> <ul> <li>allow escaping of colons (<a href="https://github.com/showdownjs/showdown/commit/25c4420">25c4420</a>)</li> <li>reduce npm package size (<a href="https://github.com/showdownjs/showdown/commit/35730b7">35730b7</a>), closes <a href="https://github-redirect.dependabot.com/showdownjs/showdown/issues/619">#619</a></li> </ul> <h3>Features</h3> <ul> <li> <ul> <li>Added <code>ellipsis</code> option to configure if the ellipsis unicode character is used or not. ( Thanks <a href="https://github.com/VladimirV99"><code>@​VladimirV99</code></a> )</li> </ul> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/showdownjs/showdown/blob/2.0.0/CHANGELOG.md">showdown's changelog</a>.</em></p> <blockquote> <h1><a href="https://github.com/showdownjs/showdown/compare/1.9.1...2.0.0">2.0.0</a> (2022-02-15)</h1> <h3>Breaking Changes</h3> <ul> <li>Supported Node Versions were set to match the <a href="https://nodejs.org/en/about/releases/">node release schedule</a> which at the time of writing includes Node 12.x, 14.x, 16.x and 17.x</li> <li>The <code>yargs</code> dependecy was updated to <code>^17.2.1</code> to mitigate a security issue.</li> <li>The Showdown Licesnse has been changed from BSD-3-Clause to MIT</li> </ul> <h3>Bug Fixes</h3> <ul> <li>allow escaping of colons (<a href="https://github.com/showdownjs/showdown/commit/25c4420">25c4420</a>)</li> <li>reduce npm package size (<a href="https://github.com/showdownjs/showdown/commit/35730b7">35730b7</a>), closes <a href="https://github-redirect.dependabot.com/showdownjs/showdown/issues/619">#619</a></li> </ul> <h3>Features</h3> <ul> <li>Added <code>ellipsis</code> option to configure if the ellipsis unicode character is used or not. ( Thanks <a href="https://github.com/VladimirV99"><code>@​VladimirV99</code></a> )</li> <li>Added a default security policy. Please report security issues to the issues tab on GitHub.</li> </ul> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/showdownjs/showdown/commit/32a1aaa39b39cff6d9a85b070d64db6829b79b26"><code>32a1aaa</code></a> chore(build): version 2.0.0</li> <li><a href="https://github.com/showdownjs/showdown/commit/97a7696fc1bac1b4904327226c453861298052f7"><code>97a7696</code></a> doc(security): add a security policy</li> <li><a href="https://github.com/showdownjs/showdown/commit/e5f419baba33774c2387bd0ec7eee769b00743d5"><code>e5f419b</code></a> build: prep and create a 2.0.0-alpha release</li> <li><a href="https://github.com/showdownjs/showdown/commit/366ef28a7a2acb52006738c4866bdf930a5e8b8d"><code>366ef28</code></a> fix(extension-registering) removeExtension implementation</li> <li><a href="https://github.com/showdownjs/showdown/commit/6ea6bbffc5eb1b8beb24d55ad48aa09cec8dd828"><code>6ea6bbf</code></a> Including QCObjects in &quot;Who uses Showdown&quot;-README (<a href="https://github-redirect.dependabot.com/showdownjs/showdown/issues/744">#744</a>)</li> <li><a href="https://github.com/showdownjs/showdown/commit/a931cc21acd79f7d8e205b66011aa79e95aae5f1"><code>a931cc2</code></a> docs: clear ambiguity about CDN usage</li> <li><a href="https://github.com/showdownjs/showdown/commit/62636d085d0b0f336c03f9a3d7c892e5cdacd6dc"><code>62636d0</code></a> feature(ellipsis): Add option to disable ellipsis</li> <li><a href="https://github.com/showdownjs/showdown/commit/b432da1eee90f555ab8cdbbf38a9f545f07ebe93"><code>b432da1</code></a> fix reference link impostors</li> <li><a href="https://github.com/showdownjs/showdown/commit/b03e34ae4e2108159b03a3ef69ea75d3463a47d1"><code>b03e34a</code></a> rename test files to match convention</li> <li><a href="https://github.com/showdownjs/showdown/commit/525b65f6d61566fea904631d1508e92bd955db73"><code>525b65f</code></a> preserve spaces between inline elements</li> <li>Additional commits viewable in <a href="https://github.com/showdownjs/showdown/compare/1.9.1...2.0.0">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~syntaxrules">syntaxrules</a>, a new releaser for showdown since your current version.</p> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=showdown&package-manager=npm_and_yarn&previous-version=1.9.1&new-version=2.0.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-06 12:12:27 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
broken-links
bug
cannot be evaluated
enhancement
health-report
help wanted
maintenance
pending-evaluation
pull-request
Mirrored from GitHub Pull Request
 question
team discussion
weekly-digest
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-docker#991
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?