search

vscode-elements / elements

Web component library for developing Visual Studio Code extensions
https://vscode-elements.github.io
MIT License
157 stars 28 forks source link

build(deps): bump liquidjs and @11ty/eleventy #46

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps liquidjs to 10.5.0 and updates ancestor dependency @11ty/eleventy. These dependencies need to be updated together.

Updates liquidjs from 9.42.1 to 10.5.0

Release notes

Sourced from liquidjs's releases.

v10.5.0

10.5.0 (2023-02-14)

Bug Fixes

  • "ownPropertyOnly" not respected when passed via "renderOptions" (d489916)

Features

  • Adds support for options to CLI and improves usability (#586) (24c8a1e)

v10.4.0

10.4.0 (2023-01-02)

Features

v10.3.3

10.3.3 (2022-12-18)

Bug Fixes

  • type compatible with v9 tag definition, support Context as scope in various render APIs, #570 (fb6a9f8)

v10.3.2

10.3.2 (2022-12-13)

Bug Fixes

v10.3.1

10.3.1 (2022-12-12)

Bug Fixes

  • support Context as evalValue parameter, #568 (0f4916b)

v10.3.0

10.3.0 (2022-12-11)

... (truncated)

Changelog

Sourced from liquidjs's changelog.

10.5.0 (2023-02-14)

Bug Fixes

  • "ownPropertyOnly" not respected when passed via "renderOptions" (d489916)

Features

  • Adds support for options to CLI and improves usability (#586) (24c8a1e)

10.4.0 (2023-01-02)

Features

10.3.3 (2022-12-18)

Bug Fixes

  • type compatible with v9 tag definition, support Context as scope in various render APIs, #570 (fb6a9f8)

10.3.2 (2022-12-13)

Bug Fixes

10.3.1 (2022-12-12)

Bug Fixes

  • support Context as evalValue parameter, #568 (0f4916b)

10.3.0 (2022-12-11)

Features

  • support disable outputEscape for specific filters, #565 (e6db371)

10.2.0 (2022-12-02)

... (truncated)

Commits
  • d9cac4e chore(release): 10.5.0 [skip ci]
  • 8ef9209 docs: add slavivanov and DaRosenberg into contributor list
  • d489916 fix: "ownPropertyOnly" not respected when passed via "renderOptions"
  • 24c8a1e feat: Adds support for options to CLI and improves usability (#586)
  • a661853 docs: update .all-contributorsrc [skip ci]
  • c0c3c07 docs: update README.md [skip ci]
  • a55f44f Added documentation for date ordinals support in date filter via %q (#581)
  • 7f76e13 docs: list sponsors & backers separately on liquidjs.com
  • 3120003 chore(release): 10.4.0 [skip ci]
  • 3f21382 feat: support not operator, #575
  • Additional commits viewable in compare view


Updates @11ty/eleventy from 1.0.2 to 2.0.0

Release notes

Sourced from @​11ty/eleventy's releases.

Eleventy v2.0.0: Now with twice as many Possums

🚨 The full release notes are available on The Eleventy Blog: Eleventy v2.0.0 or you can watch me talk about v2.0 on YouTube.

Eleventy v2.0.0 is now available! You can try it out now:

# Local project
npm install @11ty/eleventy@latest

Global install


npm install @​11ty/eleventy@​latest -g

New to Eleventy?

Eleventy is a flexible and production-ready site generator known for its zero-client JavaScript footprint, speedy sites, speedy builds, and full control over the output. Watch The State of Eleventy in Two Minutes or read more about Eleventy’s project goals.

The Big Features

Smaller, More Secure

Faster Builds

Plugins

... (truncated)

Changelog

Sourced from @​11ty/eleventy's changelog.

Dependency notes

List of dependencies that went ESM

  • @sindresorhus/slugify ESM at 2.x
  • multimatch is ESM at 6
  • bcp-47-normalize at 1.x

Release Procedure

  1. (Optional) Update minor dependencies in package.json
    • npx npm-check-updates
    • or npm outdated + npm update --save
  2. If the minimum Node version changed, make sure you update package.json engines property.
    • Make sure the error message works correctly for Node versions less than 10.
      • 0.12.x+ requires Node 10+
      • 1.x+ requires Node 12+
      • 2.x+ requires Node 14+
  3. rm -rf node_modules && rm -f package-lock.json && npm install
  4. npm audit
  5. Make sure npx ava runs okay
  6. Update version in package.json
    • (Canary) Use -canary.1 suffix
    • (Beta) Use -beta.1 suffix
  7. Run npm run coverage
  8. Check it all in and commit
  9. Tag new version
  10. Release
    • (Canary) npm publish --access=public --tag=canary
    • (Beta) npm publish --access=public --tag=beta
      • NOTE: When releasing a beta, make sure to also release a canary to mitigate 11ty/eleventy#2758.
    • (Main) npm publish --access=public
  11. (Optional) Build and commit a new the eleventy-edge-cdn project to generate a new Eleventy Edge lib.

Unfortunate note about npm canary tag: if you push a 1.0.0-canary.x to canary after a 2.0.0-canary.x, it will use the last pushed tag when you npm install from canary (not the highest version number)

Docs/Website (Main releases only)

  1. Maybe search for 2.0.0-canary. or 2.0.0-beta. in the docs copy to update to the stable release, if applicable.
  2. Check in a new 11ty-website site with updated package.json version.
  3. Add version to 11ty-website versions.json
  4. Commit it
  5. Create a new branch for branched version
  6. (Main) Check out the previous version git branch and add outdated: true to _data/config.json and commit/push.
  7. Go to https://app.netlify.com/sites/11ty/settings/domain and set up a subdomain for it.

Release Notes on GitHub (Main releases only)

... (truncated)

Commits


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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/bendera/vscode-webview-elements/network/alerts).