-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump the metalsmith group with 2 updates #2966
Bump the metalsmith group with 2 updates #2966
Conversation
b5d5e67
to
6489583
Compare
✅ You can preview this change here:
To edit notification comments on pull requests, go to your Netlify site configuration. |
@domoscargin Mind if I ask you to review this? Remember we renamed The plugin It means we can:
|
Bumps the metalsmith group with 2 updates: [@metalsmith/in-place](https://github.com/metalsmith/in-place) and [jstransformer-nunjucks](https://github.com/jstransformers/jstransformer-nunjucks). Updates `@metalsmith/in-place` from 4.6.0 to 5.0.0 - [Release notes](https://github.com/metalsmith/in-place/releases) - [Changelog](https://github.com/metalsmith/in-place/blob/main/CHANGELOG.md) - [Commits](metalsmith/in-place@v4.6.0...v5.0.0) Updates `jstransformer-nunjucks` from 1.1.0 to 1.2.0 - [Release notes](https://github.com/jstransformers/jstransformer-nunjucks/releases) - [Changelog](https://github.com/jstransformers/jstransformer-nunjucks/blob/master/CHANGELOG.md) - [Commits](jstransformers/jstransformer-nunjucks@1.1.0...1.2.0) --- updated-dependencies: - dependency-name: "@metalsmith/in-place" dependency-type: direct:development update-type: version-update:semver-major dependency-group: metalsmith - dependency-name: jstransformer-nunjucks dependency-type: direct:development update-type: version-update:semver-minor dependency-group: metalsmith ... Signed-off-by: dependabot[bot] <[email protected]>
8222db1
to
11f4bad
Compare
Rebased, still no build output changes 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I've left a comment on a pre-existing "thing to keep in mind", but I don't think it causes any problems right now.
renderer: new DesignSystemRenderer() // Markdown renderer | ||
|
||
// Custom markdown renderer | ||
renderer: new DesignSystemRenderer() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Our custom renderer uses a separate marked
install - we had some issues in the past around keeping that in sync with jstransformer-marked
. Right now, that's using v4.3.0 of marked
, whereas the custom renderer is using v5.0.2.
Though I guess metalsmith-markdown
also uses an internal version of marked
(v4.3.0 at the mo), so it's probably not a problem since the dependencies are the same. The explicit transform
option in inPlace
is really helpful in explaining what's using what here, so hopefully any issues would be easier to debug in the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@domoscargin Good point. Shall I drop that last commit, one for another day?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nah, keep it - it's the same issue but we drop a dependency, so an improvement in that sense!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Brill, will do
For reference, the dependencies are still the same (which helps)
Before
├─┬ @metalsmith/[email protected]
│ └── [email protected]
└── [email protected]
After
├─┬ [email protected]
│ └── [email protected]
└── [email protected]
const permalinks = require('@metalsmith/permalinks') // apply a permalink pattern to files | ||
const postcss = require('@metalsmith/postcss') | ||
const sass = require('@metalsmith/sass') // convert Sass files to CSS using Dart Sass | ||
const { glob } = require('glob') // Match files using glob patterns | ||
const Metalsmith = require('metalsmith') // static site generator | ||
const canonical = require('metalsmith-canonical') // add a canonical url property to pages | ||
const renamer = require('metalsmith-renamer') // rename files |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
Bumps the metalsmith group with 2 updates: @metalsmith/in-place and jstransformer-nunjucks.
Updates
@metalsmith/in-place
from 4.6.0 to 5.0.0Release notes
Sourced from
@metalsmith/in-place
's releases.Changelog
Sourced from
@metalsmith/in-place
's changelog.Commits
0e456e2
Release 5.0.053d8036
chore: update devDependenciesa87f265
Renames default export to inPlace for better intellisense287dda6
refactor: moves utils to own file & makes them privatee99cdc5
ci: fix tests on Windows22cff02
Updates README (aligned with other core plugins)8788f47
Closes #179: adds extname option & reworks multiple transform-per-file feature7400b27
Adds Typescript typesa9f7ac2
chore: correct & fix transform option test13f7fff
Updates README.md & documents transform optionUpdates
jstransformer-nunjucks
from 1.1.0 to 1.2.0Release notes
Sourced from jstransformer-nunjucks's releases.
Changelog
Sourced from jstransformer-nunjucks's changelog.
Commits
5d612f4
chore: prepare CHANGELOG.md, package.json for release 1.2.0ed75c52
Refactors filter, extension & globals resolution & addresses lint issues3ff0075
test: add a simple test for nunjucks globals3a14b98
Fixes security vulnerabilities, upgrades xo 0.47 -> 0.5577bf0d1
Replaces legacy extend-shallow with Object.assign90f7fb2
Updates Nunjucks from 3.2.3 -> 3.2.4bee26b2
ci: upgrade GH actions & Node versions8585074
Fix typo in readme CI badgef0e83da
chore: rename xo posttest to lint, fails on old Node versions27e5858
chore: try fixing CI Node version failureDependabot 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