Update dependency micromark-extension-gfm-strikethrough to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
micromark-extension-gfm-strikethrough	0.6.5 → 2.1.0

---

Release Notes

micromark/micromark-extension-gfm-strikethrough (micromark-extension-gfm-strikethrough)

v2.1.0

Compare Source

• 2354da5 Add name
  by @​shlroland in #​4
• 874f0ac Refactor to use @imports

Full Changelog: micromark/micromark-extension-gfm-strikethrough@2.0.0...2.1.0

v2.0.0

Compare Source

• c6c9efd Change to require Node.js 16
  migrate: update Node
• 75b799b Change to expose functions
  migrate: gfmStrikethroughHtml -> gfmStrikethroughHtml()
• 78fe632 Update micromark

Full Changelog: micromark/micromark-extension-gfm-strikethrough@1.0.7...2.0.0

v1.0.7

Compare Source

Fix

• d519655 Fix missing exposed type

Full Changelog: micromark/micromark-extension-gfm-strikethrough@1.0.6...1.0.7

v1.0.6

Compare Source

Types

• 36a6b6d Update types for changes in micromark-util-types

Full Changelog: micromark/micromark-extension-gfm-strikethrough@1.0.5...1.0.6

v1.0.5

Compare Source

• 66bc119 98f4251 Add improved docs
• c1c0075 Add improved JSDoc
• 8be9d7f Fix types for TS 4.9

Full Changelog: micromark/micromark-extension-gfm-strikethrough@1.0.4...1.0.5

v1.0.4

Compare Source

• fb527fd Update docs

Full Changelog: micromark/micromark-extension-gfm-strikethrough@1.0.3...1.0.4

v1.0.3

Compare Source

• f342310 Use uvu/assert in development build

Full Changelog: micromark/micromark-extension-gfm-strikethrough@1.0.2...1.0.3

v1.0.2

Compare Source

• 2d26b1d Use power-assert in development build

Full Changelog: micromark/micromark-extension-gfm-strikethrough@1.0.1...1.0.2

v1.0.1

Compare Source

• acabf4a Fix nested attention, strikethrough

v1.0.0

Compare Source

• b60f9f8 Update micromark
• effb4ec Add better docs
• 502d813 Add JSDoc based types
• eadde8a Use ESM

---

Configuration

📅 Schedule: (in timezone Australia/Sydney)

• Branch creation
  • "before 7am on Tuesday,before 7am on Wednesday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	uuid@​8.3.2 ⏵ 9.0.1	+1		+1
	@​types/​uuid@​9.0.8
	@​types/​resolve@​1.20.6
	@​types/​tough-cookie@​4.0.5
	lodash.debounce@​4.0.8
	pluralize@​8.0.0
	image-size@​2.0.2
	date-fns@​4.1.0
	decimal.js@​10.6.0
	js-yaml@​4.1.1
	dataloader@​2.2.3
	execa@​5.1.1
	typescript@​6.0.3
	zod@​4.3.6
	pretty-format@​29.7.0
	jest-diff@​29.7.0

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/entities@6.0.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: 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@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@6.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report