Skip to content
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

build(deps-dev): bump eleventy-plugin-vento from 2.6.0 to 3.0.0 #1218

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 23, 2024

Bumps eleventy-plugin-vento from 2.6.0 to 3.0.0.

Release notes

Sourced from eleventy-plugin-vento's releases.

v3.0.0

A massive thank you to @​oscarotero for helping me understand the Vento engine, this release would not have been possible without him. There may be a few latent bugs, so be sure to raise issues as they come up.


Major Changes

  • 668700c: Enforce new minimum version — Eleventy v3.0.0-alpha.15 or later is now required for this plugin to function.

    Although this goes against the backwards compatibility ethos of Eleventy, the addition of the getShortcodes() and getPairedShortcodes() functions that were added in alpha.15 are now utilized in this plugin to bring even more goodness to your templates.

    Thanks @​zachleat for making this possible!

  • 9d8eb8a: Adds complete support for Eleventy shortcodes and filters within Vento. Shortcodes are now loaded by default as Vento tags and will no longer be exposed as functions in your page data.

    The implementation of single shortcodes remains largely similar, just replace function-like calls with Vento tags.

    - {{ nametag('Noel', 'Forte') }}
    + {{ nametag 'Noel', 'Forte' }}

    Of course, the big news is that paired shortcodes are now officially supported by this plugin!! Prior to this release, paired shortcodes were exposed just like regular shortcodes, but were plain JS functions. With this release you can now use paired shortcodes just like any other tag.

    <!-- Before: everything is jammed into the function call :( -->
    {{ blockquote("<p>Call me Ishmael. Some years ago—never mind how long precisely—having little or no money in my purse, and nothing particular to interest me on shore, I thought I would sail about a little and see the watery part of the world.</p>\n<p>It is a way I have of driving off the spleen and regulating the circulation.</p>", "Herman Melville", "1851") }}
    <!-- After: opening and closing tags with arguments separated :) -->
    {{ blockquote 'Herman Melville', '1851' }}
    <p>Call me Ishmael. Some years ago—never mind how long precisely—having little or no money in my purse, and nothing particular to interest me on shore, I thought I would sail about a little and see the watery part of the world.</p>
    <p>It is a way I have of driving off the spleen and regulating the circulation.</p>
    {{ /blockquote }}

    Because these changes removed direct dependence on Eleventy JavaScript functions, the addHelpers option has been replaced with 3 new options: shortcodes, pairedShortcodes and filters. All of them are enabled by default but can be disabled in your plugin config like so.

    eleventyConfig.addPlugin(VentoPlugin, {
    - addHelpers: false,
    + shortcodes: false,
    + pairedShortcodes: false,
    + filters: false,
    });
  • 516cd2f: Modifications to auto_trim functionality

    Starting with this release the way the auto_trim plugin is implemented is a bit different.

... (truncated)

Changelog

Sourced from eleventy-plugin-vento's changelog.

3.0.0

Major Changes

  • 668700c: Enforce new minimum version — Eleventy v3.0.0-alpha.15 or later is now required for this plugin to function.

    Although this goes against the backwards compatibility ethos of Eleventy, the addition of the getShortcodes() and getPairedShortcodes() functions that were added in alpha.15 are now utilized in this plugin to bring even more goodness to your templates.

    Thanks @​zachleat for making this possible!

  • 9d8eb8a: Adds complete support for Eleventy shortcodes and filters within Vento. Shortcodes are now loaded by default as Vento tags and will no longer be exposed as functions in your page data.

    The implementation of single shortcodes remains largely similar, just replace function-like calls with Vento tags.

    - {{ nametag('Noel', 'Forte') }}
    + {{ nametag 'Noel', 'Forte' }}

    Of course, the big news is that paired shortcodes are now officially supported by this plugin!! Prior to this release, paired shortcodes were exposed just like regular shortcodes, but were plain JS functions. With this release you can now use paired shortcodes just like any other tag.

    <!-- Before: everything is jammed into the function call :( -->
    {{ blockquote("<p>Call me Ishmael. Some years ago—never mind how long precisely—having little or no money in my purse, and nothing particular to interest me on shore, I thought I would sail about a little and see the watery part of the world.</p>\n<p>It is a way I have of driving off the spleen and regulating the circulation.</p>", "Herman Melville", "1851") }}
    <!-- After: opening and closing tags with arguments separated :) -->
    {{ blockquote 'Herman Melville', '1851' }}
    <p>Call me Ishmael. Some years ago—never mind how long precisely—having little or no money in my purse, and nothing particular to interest me on shore, I thought I would sail about a little and see the watery part of the world.</p>
    <p>It is a way I have of driving off the spleen and regulating the circulation.</p>
    {{ /blockquote }}

    Because these changes removed direct dependence on Eleventy JavaScript functions, the addHelpers option has been replaced with 3 new options: shortcodes, pairedShortcodes and filters. All of them are enabled by default but can be disabled in your plugin config like so.

    eleventyConfig.addPlugin(VentoPlugin, {
    - addHelpers: false,
    + shortcodes: false,
    + pairedShortcodes: false,
    + filters: false,
    });
  • 516cd2f: Modifications to auto_trim functionality

    Starting with this release the way the auto_trim plugin is implemented is a bit different.

    The plugin option trimTags is now autotrim. Be sure to update your plugin options object accordingly:

... (truncated)

Commits
  • 6d47fd2 [ci] release (#19)
  • e7b3468 fix: test workflow was renamed 'ci'
  • 574f662 rework CI scripts so that tests can be called as a
  • 245a841 switch tinyexec out for zx in generate-changesets script
  • 868cb05 revise autotrim functionality and extends feature to use placeholders for Ven...
  • 77b4906 remove .npmignore in favor of files key in package.json
  • e3ef297 remove changeset generator from version command
  • 5573b4b update synchronization script
  • a099478 Revert "combine packageManager config and node version into mise.toml config"
  • d5e5ac4 update changeset generation script to only look at changes after the latest tag
  • 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)

Bumps [eleventy-plugin-vento](https://github.com/noelforte/eleventy-plugin-vento) from 2.6.0 to 3.0.0.
- [Release notes](https://github.com/noelforte/eleventy-plugin-vento/releases)
- [Changelog](https://github.com/noelforte/eleventy-plugin-vento/blob/main/CHANGELOG.md)
- [Commits](noelforte/eleventy-plugin-vento@v2.6.0...v3.0.0)

---
updated-dependencies:
- dependency-name: eleventy-plugin-vento
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file ship it! Triggers automation for completing PRs for dependencies labels Sep 23, 2024
Copy link

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/[email protected] Transitive: environment, eval, filesystem, network, shell +8 6.29 MB noelforte

🚮 Removed packages: npm/[email protected]

View full report↗︎

@kodiakhq kodiakhq bot merged commit 133e0ef into source Sep 23, 2024
7 checks passed
@kodiakhq kodiakhq bot deleted the dependabot/npm_and_yarn/eleventy-plugin-vento-3.0.0 branch September 23, 2024 07:22
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 ship it! Triggers automation for completing PRs for dependencies
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants