Skip to content

Bump Markdig.Signed from 0.21.1 to 0.22.0 - #13741

Merged
Ilya (iSazonov) merged 1 commit into
masterfrom
dependabot/nuget/Markdig.Signed-0.22.0
Oct 6, 2020
Merged

Bump Markdig.Signed from 0.21.1 to 0.22.0#13741
Ilya (iSazonov) merged 1 commit into
masterfrom
dependabot/nuget/Markdig.Signed-0.22.0

Conversation

@dependabot-preview

Copy link
Copy Markdown
Contributor

Bumps Markdig.Signed from 0.21.1 to 0.22.0.

Changelog

Sourced from Markdig.Signed's changelog.

0.22.0 (05 Oct 2020)

Commits
  • 751c79f Bump to 0.22.0
  • 4dc8cc3 Bump packages in tests
  • a1891e2 Fix coverlet
  • ff06379 Merge branch 'pr/n471_master'
  • 8b64ce4 Fix quoteblock with setexheading when no lazy continuations are involved
  • a781ae1 Change tests to exe
  • 2e50072 Delay parsing of all specs in the tests itself instead of using static to res...
  • cf6d98b Update tests
  • ccb7e8e add failing test, partial fix for setext headings in blockquotes
  • db25c1d Merge pull request #473 from aloisdg/patch-1
  • Additional commits viewable in compare view

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 badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .github/dependabot.yml file in this repo:

  • Update frequency
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps [Markdig.Signed](https://github.com/lunet-io/markdig) from 0.21.1 to 0.22.0.
- [Release notes](https://github.com/lunet-io/markdig/releases)
- [Changelog](https://github.com/lunet-io/markdig/blob/master/changelog.md)
- [Commits](xoofx/markdig@0.21.1...0.22.0)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview Bot added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Oct 5, 2020
@ghost ghost assigned Ilya (iSazonov) Oct 5, 2020
@iSazonov
Ilya (iSazonov) merged commit f2a3716 into master Oct 6, 2020
@iSazonov
Ilya (iSazonov) deleted the dependabot/nuget/Markdig.Signed-0.22.0 branch October 6, 2020 09:43
@iSazonov

Ilya (iSazonov) commented Oct 6, 2020

Copy link
Copy Markdown
Collaborator

Travis Plunk (@TravisEz13) What is a milestone we should assign? Can we create 7.2.0-preview.1 for new PRs?

@ghost

Copy link
Copy Markdown

🎉v7.2.0-preview.1 has been released which incorporates this pull request.:tada:

Handy links:

Thatgfsj (Thatgfsj) pushed a commit to Thatgfsj/PowerShell that referenced this pull request Aug 6, 2026
Bumps [Markdig.Signed](https://github.com/lunet-io/markdig) from 0.21.1 to 0.22.0.
- [Release notes](https://github.com/lunet-io/markdig/releases)
- [Changelog](https://github.com/lunet-io/markdig/blob/master/changelog.md)
- [Commits](xoofx/markdig@0.21.1...0.22.0)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants