Skip to content

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Jun 12, 2023

Bumps @metalsmith/markdown from 1.4.0 to 1.10.0.

Release notes

Sourced from @​metalsmith/markdown's releases.

@​metalsmith/markdown 1.10.0

@​metalsmith/markdown 1.9.2

  • Fixes missing types and adds source maps to package 78eaefc

@​metalsmith/markdown 1.9.1

  • Updates marked from 4.2.4 -> 4.2.12 c9881d1
  • fix: don't log a warning for undefined key values, only when typeof is not string 53feb48
  • fix: don't crash but gracefully ignore undefined for wildcard keypaths d05e39a

@​metalsmith/markdown 1.9.0

@​metalsmith/markdown 1.8.0

@​metalsmith/markdown 1.7.0

  • Drops node < 12 support, updates devDependencies 0727d81
  • Drop support for Metalsmith < 2.5.0 9654d29
  • Better debug logging c9fc051
  • Use metalsmith.debug instead of debug b745991
  • Updates marked from 4.0.16 -> 4.2.0 1aa53d2

@​metalsmith/markdown 1.6.0

@​metalsmith/markdown 1.5.0

Changelog

Sourced from @​metalsmith/markdown's changelog.

Changelog

All notable changes to this project will be documented in this file. Dates are displayed in UTC.

Generated by auto-changelog.

v1.9.2

8 May 2023

  • Fixes missing types and adds source maps to package 78eaefc

v1.9.1

26 February 2023

  • Updates marked from 4.2.4 -> 4.2.12 c9881d1
  • fix: don't log a warning for undefined key values, only when typeof is not string 53feb48
  • fix: don't crash but gracefully ignore undefined for wildcard keypaths d05e39a

v1.9.0

2 February 2023

v1.8.0

18 December 2022

v1.7.0

4 November 2022

  • Drops node < 12 support, updates devDependencies 0727d81
  • Drop support for Metalsmith < 2.5.0 9654d29
  • Better debug logging c9fc051
  • Use metalsmith.debug instead of debug b745991
  • Updates marked from 4.0.16 -> 4.2.0 1aa53d2

v1.6.0

... (truncated)

Commits
  • 845daa9 Release 1.10.0
  • 2b95606 Resolves #68: adds ability to render targets in metalsmith.metadata()
  • e104d3b chore: move tests from CJS to ESM on src + prettier formatting
  • 67db54d Drops support for Node < 14.14.0 (Node 12 EOL = 2023-04-30)
  • b8872a8 test: update mocha to latest, move from nyc to c8 for test coverage, update N...
  • 1a67966 chore: update devDependencies & fix security vulnerabilities
  • 79a0939 Updates marked 4.2.12 -> 4.3.0
  • faf9e40 Release 1.9.2
  • 78eaefc Fixes missing types and adds source maps to package
  • 61976dc Release 1.9.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 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)

 Mention [stepsize] in a comment if you'd like to report some technical debt. See examples here.

Bumps [@metalsmith/markdown](https://github.com/metalsmith/markdown) from 1.4.0 to 1.10.0.
- [Release notes](https://github.com/metalsmith/markdown/releases)
- [Changelog](https://github.com/metalsmith/markdown/blob/main/CHANGELOG.md)
- [Commits](metalsmith/markdown@v1.4.0...v1.10.0)

---
updated-dependencies:
- dependency-name: "@metalsmith/markdown"
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jun 12, 2023
@aviator-app
Copy link

aviator-app bot commented Jun 12, 2023

Aviator Changeset actions:

@aviator-app
Copy link

aviator-app bot commented Jun 12, 2023

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This pull request is currently open (not queued).

How to merge

To merge this PR, comment /aviator merge or add the mergequeue label.


See the real-time status of this PR on the Aviator webapp.

@pull-request-quantifier-deprecated

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file Extra Small javascript Pull requests that update Javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant