d-sektionen / medlem

:bust_in_silhouette: New member portal for D-sektionen.
https://d-sektionen.github.io/medlem
MIT License
4 stars 1 forks source link

Bump json5, gatsby, gatsby-plugin-manifest, gatsby-plugin-sass and eslint-plugin-import #30

Closed dependabot[bot] closed 8 months ago

dependabot[bot] commented 1 year ago

Bumps json5 to 2.2.3 and updates ancestor dependencies json5, gatsby, gatsby-plugin-manifest, gatsby-plugin-sass and eslint-plugin-import. These dependencies need to be updated together.

Updates json5 from 1.0.1 to 2.2.3

Release notes

Sourced from json5's releases.

v2.2.3

  • Fix: json5@2.2.3 is now the 'latest' release according to npm instead of v1.0.2. (#299)

v2.2.2

  • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

v2.2.1

  • Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)

v2.2.0

  • New: Accurate and documented TypeScript declarations are now included. There is no need to install @types/json5. (#236, #244)

v2.1.3 [code, diff]

  • Fix: An out of memory bug when parsing numbers has been fixed. (#228, #229)

v2.1.2

  • Fix: Bump minimist to v1.2.5. (#222)

v2.1.1

  • New: package.json and package.json5 include a module property so bundlers like webpack, rollup and parcel can take advantage of the ES Module build. (#208)
  • Fix: stringify outputs \0 as \\x00 when followed by a digit. (#210)
  • Fix: Spelling mistakes have been fixed. (#196)

v2.1.0

  • New: The index.mjs and index.min.mjs browser builds in the dist directory support ES6 modules. (#187)

v2.0.1

  • Fix: The browser builds in the dist directory support ES5. (#182)

v2.0.0

  • Major: JSON5 officially supports Node.js v6 and later. Support for Node.js v4 has been dropped. Since Node.js v6 supports ES5 features, the code has been rewritten in native ES5, and the dependence on Babel has been eliminated.

  • New: Support for Unicode 10 has been added.

  • New: The test framework has been migrated from Mocha to Tap.

  • New: The browser build at dist/index.js is no longer minified by default. A minified version is available at dist/index.min.js. (#181)

  • Fix: The warning has been made clearer when line and paragraph separators are

... (truncated)

Changelog

Sourced from json5's changelog.

v2.2.3 [code, diff]

  • Fix: json5@2.2.3 is now the 'latest' release according to npm instead of v1.0.2. (#299)

v2.2.2 [code, diff]

  • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

v2.2.1 [code, diff]

  • Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)

v2.2.0 [code, diff]

  • New: Accurate and documented TypeScript declarations are now included. There is no need to install @types/json5. (#236, #244)

v2.1.3 [code, diff]

  • Fix: An out of memory bug when parsing numbers has been fixed. (#228, #229)

v2.1.2 [code, diff]

  • Fix: Bump minimist to v1.2.5. (#222)

v2.1.1 [code, [diff][d2.1.1]]

... (truncated)

Commits
  • c3a7524 2.2.3
  • 94fd06d docs: update CHANGELOG for v2.2.3
  • 3b8cebf docs(security): use GitHub security advisories
  • f0fd9e1 docs: publish a security policy
  • 6a91a05 docs(template): bug -> bug report
  • 14f8cb1 2.2.2
  • 10cc7ca docs: update CHANGELOG for v2.2.2
  • 7774c10 fix: add proto to objects and arrays
  • edde30a Readme: slight tweak to intro
  • 97286f8 Improve example in readme
  • Additional commits viewable in compare view


Updates gatsby from 2.32.13 to 5.3.3

Release notes

Sourced from gatsby's releases.

v5.3.0

Welcome to gatsby@5.3.0 release (December 2022 #1)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v5.2.0

Welcome to gatsby@5.2.0 release (November 2022 #3)

This is an out of band release due to the removal of the Potrace library in Gatsby. We'll continue with our biweekly schedule as normal.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

v5.1.0

Welcome to gatsby@5.1.0 release (November 2022 #2)

This is the first minor release after the recent major release of Gatsby 5! We are focused on your feedback and implementing fixes as needed.

If you haven’t migrated yet, please refer to the migration guide. We’ve done our best to make the transition smooth!

Some brief notes about what Gatsby 5 brings to the table:

  • Slices API unlocks up to 90% reduction in build duration for content changes in highly shared components
  • Partial Hydration allows you to ship only the necessary JavaScript to the browser

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

v5.0.0

Welcome to gatsby@5.0.0 release (November 2022 #1)

Key highlights of this release:

Major dependency updates:

... (truncated)

Commits
  • da692c7 chore(release): Publish
  • e333019 fix(gatsby-transformer-remark): Disallow JS frontmatter by default (#37244) (...
  • 3e7e996 fix(gatsby): [rendering engines] use results of exports removal if sourceMap ...
  • f448e12 fix(gatsby): don't output file-loader assets to .cache (#37284) (#37295)
  • 8fc123c chore(release): Publish
  • b7477f4 fix(gatsby-plugin-image): Normalize filename for correct hashing (#37262) (#3...
  • 98cbee1 chore(release): Publish
  • a283319 fix(gatsby): use file:// protocol when importing gatsby-config/node (#37257) ...
  • 287cabd chore(release): Publish
  • e9aafe4 Revert "fix(deps): update dependency lmdb to v2.7.1 (#37160)" (#37255) (#37258)
  • Additional commits viewable in compare view


Updates gatsby-plugin-manifest from 2.12.1 to 5.3.1

Release notes

Sourced from gatsby-plugin-manifest's releases.

v5.3.0

Welcome to gatsby@5.3.0 release (December 2022 #1)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v5.2.0

Welcome to gatsby@5.2.0 release (November 2022 #3)

This is an out of band release due to the removal of the Potrace library in Gatsby. We'll continue with our biweekly schedule as normal.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

v5.1.0

Welcome to gatsby@5.1.0 release (November 2022 #2)

This is the first minor release after the recent major release of Gatsby 5! We are focused on your feedback and implementing fixes as needed.

If you haven’t migrated yet, please refer to the migration guide. We’ve done our best to make the transition smooth!

Some brief notes about what Gatsby 5 brings to the table:

  • Slices API unlocks up to 90% reduction in build duration for content changes in highly shared components
  • Partial Hydration allows you to ship only the necessary JavaScript to the browser

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

v5.0.0

Welcome to gatsby@5.0.0 release (November 2022 #1)

Key highlights of this release:

Major dependency updates:

... (truncated)

Changelog

Sourced from gatsby-plugin-manifest's changelog.

5.3.1 (2022-12-14)

Note: Version bump only for package gatsby-plugin-manifest

5.3.0 (2022-12-13)

🧾 Release notes

Chores

5.2.0 (2022-11-25)

🧾 Release notes

Other Changes

5.1.0 (2022-11-22)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-manifest

5.0.0 (2022-11-08)

🧾 Release notes

Chores

4.24.0 (2022-09-27)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-manifest

4.23.1 (2022-09-22)

Note: Version bump only for package gatsby-plugin-manifest

4.23.0 (2022-09-13)

🧾 Release notes

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by marvinjudehk, a new releaser for gatsby-plugin-manifest since your current version.


Updates gatsby-plugin-sass from 2.8.0 to 6.3.1

Release notes

Sourced from gatsby-plugin-sass's releases.

v5.3.0

Welcome to gatsby@5.3.0 release (December 2022 #1)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v5.2.0

Welcome to gatsby@5.2.0 release (November 2022 #3)

This is an out of band release due to the removal of the Potrace library in Gatsby. We'll continue with our biweekly schedule as normal.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

v5.1.0

Welcome to gatsby@5.1.0 release (November 2022 #2)

This is the first minor release after the recent major release of Gatsby 5! We are focused on your feedback and implementing fixes as needed.

If you haven’t migrated yet, please refer to the migration guide. We’ve done our best to make the transition smooth!

Some brief notes about what Gatsby 5 brings to the table:

  • Slices API unlocks up to 90% reduction in build duration for content changes in highly shared components
  • Partial Hydration allows you to ship only the necessary JavaScript to the browser

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

v5.0.0

Welcome to gatsby@5.0.0 release (November 2022 #1)

Key highlights of this release:

Major dependency updates:

... (truncated)

Changelog

Sourced from gatsby-plugin-sass's changelog.

6.3.1 (2022-12-14)

Note: Version bump only for package gatsby-plugin-sass

6.3.0 (2022-12-13)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-sass

6.2.0 (2022-11-25)

🧾 Release notes

Other Changes

6.1.0 (2022-11-22)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-sass

6.0.0 (2022-11-08)

🧾 Release notes

Chores

5.24.0 (2022-09-27)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-sass

5.23.1 (2022-09-22)

Note: Version bump only for package gatsby-plugin-sass

5.23.0 (2022-09-13)

🧾 Release notes

Chores

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by marvinjudehk, a new releaser for gatsby-plugin-sass since your current version.


Updates eslint-plugin-import from 2.24.2 to 2.26.0

Release notes

Sourced from eslint-plugin-import's releases.

v2.25.2

Full Changelog: https://github.com/import-js/eslint-plugin-import/compare/v2.25.1...v2.25.2

v2.25.1

Full Changelog: https://github.com/import-js/eslint-plugin-import/compare/v2.25.0...v2.25.1

v2.25.0

What's Changed

New Contributors

Full Changelog: https://github.com/import-js/eslint-plugin-import/compare/v2.24.2...v2.25.0

Changelog

Sourced from eslint-plugin-import's changelog.

[2.26.0] - 2022-04-05

Added

  • [no-named-default], [no-default-export], [prefer-default-export], [no-named-export], [export], [named], [namespace], [no-unused-modules]: support arbitrary module namespace names (#2358, thanks [@​sosukesuzuki])
  • [no-dynamic-require]: support dynamic import with espree (#2371, thanks [@​sosukesuzuki])
  • [no-relative-packages]: add fixer (#2381, thanks [@​forivall])

Fixed

  • [default]: typescript-eslint-parser: avoid a crash on exporting as namespace (thanks [@​ljharb])
  • [export]/TypeScript: false positive for typescript namespace merging (#1964, thanks [@​magarcia])
  • [no-duplicates]: ignore duplicate modules in different TypeScript module declarations (#2378, thanks [@​remcohaszing])
  • [no-unused-modules]: avoid a crash when processing re-exports (#2388, thanks [@​ljharb])

Changed

  • [Tests] [no-nodejs-modules]: add tests for node protocol URL (#2367, thanks [@​sosukesuzuki])
  • [Tests] [default], [no-anonymous-default-export], [no-mutable-exports], [no-named-as-default-member], [no-named-as-default]: add tests for arbitrary module namespace names (#2358, thanks [@​sosukesuzuki])
  • [Docs] [no-unresolved]: Fix RegExp escaping in readme (#2332, thanks [@​stephtr])
  • [Refactor] [namespace]: try to improve performance (#2340, thanks [@​ljharb])
  • [Docs] make rule doc titles consistent (#2393, thanks [@​TheJaredWilcurt])
  • [Docs] [order]: TS code examples should use TS code blocks (#2411, thanks [@​MM25Zamanian])
  • [Docs] [no-unresolved]: fix link (#2417, thanks [@​kylemh])

[2.25.4] - 2022-01-02

Fixed

  • importType: avoid crashing on a non-string' (#2305, thanks [@​ljharb])
  • [first]: prevent crash when parsing angular templates (#2210, thanks [@​ljharb])
  • importType: properly resolve @/*-aliased imports as internal (#2334, thanks [@​ombene])
  • [named]/ExportMap: handle named imports from CJS modules that use dynamic import (#2341, thanks [@​ludofischer])

Changed

  • [no-default-import]: report on the token "default" instead of the entire node (#2299, thanks [@​pmcelhaney])
  • [Docs] [order]: Remove duplicate mention of default (#2280, thanks [@​johnthagen])
  • [Deps] update eslint-module-utils

[2.25.3] - 2021-11-09

Fixed

  • [extensions]: ignore unresolveable type-only imports (#2270, #2271, thanks [@​jablko])
  • importType: fix isExternalModule calculation (#2282, thanks [@​mx-bernhard])
  • [no-import-module-exports]: avoid false positives with a shadowed module or exports (#2297, thanks [@​ljharb])

Changed

[2.25.2] - 2021-10-12

... (truncated)

Commits
  • d160285 Bump to 2.26.0
  • 0e80ee3 [Deps] update tsconfig-paths
  • d8633c3 [Docs] no-unresolved: fix link
  • 98bbb2c [Docs] order: TS code examples should use TS code blocks
  • 21304bd [Deps] update tsconfig-paths
  • 8b7000e [Fix] no-unused-modules: avoid a crash when processing re-exports
  • 747d6dc [Docs] make rule doc titles consistent
  • b0e6f7f [Refactor] namespace: try to improve performance
  • 00a4ede [Deps] update minimatch
  • 35bd3a5 [Dev Deps] update @angular-eslint/template-parser, chai
  • Additional commits viewable in compare view


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/d-sektionen/medlem/network/alerts).
dependabot[bot] commented 8 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.