Repository navigation
chore(deps): update akiomik/mado action to v0.4.0 - #21
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/akiomik-mado-0.x
branch
from
October 27, 2026 06:28
fd5209c to
bc3dad1
Compare
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.3.1→v0.4.0Release Notes
akiomik/mado
v0.4.0Compare Source
Changed
Breaking:
respect-gitignoretakes a policy rather than a boolean, sincethere are three behaviours to name rather than two (#447):
respect-gitignore = falserespect-gitignore = "never"respect-gitignore = truerespect-gitignore = "repository-only"respect-gitignore = "always""repository-only"is the default and is what a booleantruedid:.gitignoreapplies inside a repository, as Git does. Note the entry below,which changes what a repository lints in every mode.
"always"stops mado lookingfor a repository at all, for every tree rather than only those without one, so
a source archive or a Docker context copied without
.gitlints the files aclone of it does. It comes on the
ignorecrate's terms, the same onesrg --no-require-githas:.gitignorefiles apply from every parentdirectory, above a clone's own repository root included, and a repository
below the path being linted does not bound the search. The boolean spelling is
not accepted; a configuration that still carries it fails to load rather than
being guessed at
The global Git ignore file and
.git/info/excludeare no longer read. madohad been reading both by inheriting the walker's defaults; neither travels
with the tree being linted, so reading them had one source lint differently on
another machine (#447)
Breaking:
config::lint::Lint::respect_gitignoreis aconfig::lint::GitignorePolicyrather than abool, andservice::walker::WalkParallelBuilder::buildtakes one (#447)Breaking: MD034 no longer reports a URL whose scheme GFM does not
autolink.
http://,https://andftp://are the ones it does, softps://,file://,ssh://and the rest are left alone, none of them beinga link a reader is handed. An email address is matched apart from those and
carries its own two: a
mailto:foo@example.comorxmpp:foo@example.comisstill reported, and from the scheme rather than from the address, that being
where GFM starts the link (#418)
Breaking: MD034 no longer reports a URL inside square brackets — a
shortcut link, or an image's alt text — GFM autolinking nothing inside of
them. This is the report a reversed link
(text)[http://www.example.com/]used to raise, and mado has no rule of its own for that typo, so it now goes
unreported (#418)
Breaking: MD007 no longer compares a bullet with the item above it: a
bullet whose list is directly in another item is compared with that item,
and any other bullet is checked on its own. When measuring indentation, a
tab counts to the next tab stop rather than as one column. Results change in
both directions. With the default
indent, for example,* afollowed by\t* bis no longer reported, while>\t* anow is (#479)Breaking: MD005 measures indentation as CommonMark does, in columns
after any block quote marker, instead of in bytes from the start of the
line. Results change, in both directions, for some lists indented with tabs,
after a byte order mark, or inside blockquotes (#483)
Update the Markdown parser (
comrak) from 0.54.0 to 0.57.0 (#463, #502)Breaking: the Linux arm64 binary needs glibc 2.34 or later, as the x86_64
one already does. It no longer starts on systems with an older glibc, such as
Amazon Linux 2, Ubuntu 20.04 and Debian 11 (#509)
Fixed
were skipped as part of the block, which they are not (#502)
code-blocks = false, stop skipping the blank lines after anindented code block as part of the block. A line there holding only
whitespace, and longer than the limit, is now reported (#502)
code rather than at the blank line after it. No output format prints the end;
it is for a library caller reading
Violation::position()(#502)the first inline reported on it, which an inline spanning two lines leaves
beginning where it closed rather than where the line's content does. Reports
move in both directions:
> **boldfollowed by> span.** tail herewasreported at the text after the strong and is not any more, one space following
both markers, while
> **boldfollowed by> span**went unreported and nowis, the two spaces after its marker having gone unread. A line below the one a
nested quote starts at is measured at each of that quote's own markers rather
than at the innermost alone, so
> > > textwritten there is reported onceper marker, and a line carrying no marker at all is left alone rather than
measured at the first inline on it. Two shapes change answer the other way: a
line reaching its quote through a list item's indentation goes unreported
(#456), and one whose
>is indented far enough for CommonMark to read it astext is reported for the spaces after it (#455). The position a violation
carries runs from the content after the marker to the end of the line, where it
ran to the end of the first inline on it; no output format prints that, so it is
for a library caller reading
Violation::position()(#452)follows a blank quoted line is measured too.
> Quoted textabove a>and a> More quoted textreports the third line, as it already did when that linewas the quote's first block, and a nested quote written there is reported for
the outer marker as well as the inner one. Each block is read on the line it
starts at rather than against the column the quote's first line put its marker
at, so a block whose marker is indented within what CommonMark allows is not
reported for that indentation, one whose marker sits further left than the
quote's first is reported for the spaces after it, and the position a reported
block carries names the line it starts at rather than every line it spans. An
indented code block written anywhere but first is reported with the rest, the
four spaces it needs on top of the marker's own being more than one, which is
#459 rather than anything this release settles. Such a block is reported at the
first character after its spaces rather than at the column the block's content
begins, which moves the column right when it is written with more spaces than
the four it needs. A lazily continued line of a block after the first is
measured as well, which is how the misread #455 describes reaches documents it
did not before (#460)
accepts.
http\://www.example.com/, which is how a URL is written so that itis not autolinked, was reported as one. A
www.host written without ascheme is autolinked by GFM and is now reported, and a URL is reported to
where GFM stops linking it rather than to where a scanner stops reading it
(#418)
v0.3.2Compare Source
Added
versioninput, so a workflow can run a madorelease other than the one the action was published with (#390)
Fixed
numbered 10 or higher are no longer reported when a single space already
follows the marker (#363)
lists nested inside a blockquote are checked (#368)
the start of the line (#369)
arm64release asset on arm64 Linux runners,where it previously asked for an
aarch64one that no release publishes andfailed (#395)
one-backtick one, so spans delimited by two or more backticks — the only way
to write a span containing a backtick — are no longer reported when they hold
no padding. A span whose delimiters sit on different lines is left unjudged
rather than reported, since nothing recorded about it describes what was
written against those delimiters (#391)
cost the report. A
\|written earlier in the same table cell, or earlier onthe same line above a table's header row, moved an inline's reported column
one to the left of the character it named, and one more for each further
escape (#405)
counted off a string CommonMark had already resolved the escapes out of. A
\.written earlier in the same text node moved the reported column one tothe left of the character it named, and one more for each further escape
(#407)
*or_is no longer read as an emphasis marker, so aline whose only emphasis is the one its author escaped to keep is left alone,
and a line that has emphasis besides is reported at it (#407)
than the whitespace itself (#407)
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.