arthur/website-old
1
0
Fork 0
mirror of https://github.com/ArthurDanjou/website-old.git synced 2026-01-14 20:19:35 +01:00
Code Issues 31 Packages Projects Releases Wiki Activity

[PR #260] [CLOSED] fix(deps): bump core-js from 3.20.2 to 3.22.6 #270

New Issue
Closed
opened 2025-12-01 17:06:33 +01:00 by arthur · 0 comments
arthur commented 2025-12-01 17:06:33 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ArthurDanjou/website-old/pull/260
Author: @dependabot[bot]
Created: 5/23/2022
Status: ❌ Closed

Base: master ← Head: dependabot/npm_and_yarn/core-js-3.22.6

📝 Commits (1)

  • 3520cb1 fix(deps): bump core-js from 3.20.2 to 3.22.6

📊 Changes

2 files changed (+5 additions, -5 deletions)

View changed files

📝 package.json (+1 -1)
📝 yarn.lock (+4 -4)

📄 Description

Bumps core-js from 3.20.2 to 3.22.6.

Changelog

Sourced from core-js's changelog.

3.22.6 - 2022.05.23
  • Fixed possible double call of ToNumber conversion on arguments of Math.{ fround, trunc } polyfills
  • Array.prototype.includes marked as fixed in FF102
3.22.5 - 2022.05.10
  • Ensured that polyfilled constructors .prototype is non-writable
  • Ensured that polyfilled methods .prototype is not defined
  • Added detection and fix of a V8 ~ Chrome <103 bug of struturedClone that returns null if cloned object contains multiple references to one error
3.22.4 - 2022.05.03
  • Ensured proper .length of polyfilled functions even in compressed code (excepting some ancient engines)
  • Ensured proper .name of polyfilled accessors (excepting some ancient engines)
  • Ensured proper source / ToString conversion of polyfilled accessors
  • Actualized Rhino compat data
  • Refactoring
3.22.3 - 2022.04.28
  • Added a fix for FF99+ Array.prototype.includes broken on sparse arrays
3.22.2 - 2022.04.21
  • Fixed URLSearchParams in IE8- that was broken in the previous release
  • Fixed __lookupGetter__ entries
3.22.1 - 2022.04.20
  • Improved some cases of RegExp flags handling
  • Prevented experimental warning in NodeJS ~ 18.0 on detection fetch API
  • Added NodeJS 18.0 compat data
3.22.0 - 2022.04.15
  • Change Array by copy proposal:
    • Moved to Stage 3, March TC39 meeting
    • Disabled forced replacement and added /actual/ entry points for methods from this proposal
    • Array.prototype.toSpliced throws a TypeError instead of RangeError if the result length is more than MAX_SAFE_INTEGER, proposal-change-array-by-copy/70
  • Added some more atob / btoa fixes:
    • NodeJS <17.9 atob does not ignore spaces, node/42530
    • Actual NodeJS atob does not validate encoding, node/42646
    • FF26- implementation does not properly convert argument to string
    • IE / Edge <16 implementation have wrong arity
  • Added /full/ namespace as the replacement for /features/ since it's more descriptive in context of the rest namespaces (/es/ ⊆ /stable/ ⊆ /actual/ ⊆ /full/)
  • Avoided propagation of removed parts of proposals to upper stages. For example, %TypedArray%.prototype.groupBy was removed from the Array grouping proposal a long time ago. We can't completely remove this method since it's a breaking change. But this proposal has been promoted to stage 3 - so the proposal should be promoted without this method, this method should not be available in /actual/ entries - but it should be available in early-stage entries to avoid breakage.
  • Significant internal refactoring and splitting of modules (but without exposing to public API since it will be a breaking change - it will be exposed in the next major version)
  • Bug fixes:
    • Fixed work of non-standard V8 Error features with wrapped Error constructors, #1061
    • null and undefined allowed as the second argument of structuredClone, #1056
  • Tooling:
    • Stabilized proposals are filtered out from the core-js-compat -> core-js-builder -> core-js-bundle output. That mean that if the output contains, for example, es.object.has-own, the legacy reference to it, esnext.object.has-own, no longer added.
    • Aligned modules filters of core-js-builder and core-js-compat, now it's modules and exclude options
    • Added support of entry points, modules, regexes, and arrays of them to those filters
    • Missed targets option of core-js-compat means that the targets filter just will not be applied, so the result will contain modules required for all possible engines
  • Compat data:

... (truncated)

Commits

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)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/ArthurDanjou/website-old/pull/260 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 5/23/2022 **Status:** ❌ Closed **Base:** `master` ← **Head:** `dependabot/npm_and_yarn/core-js-3.22.6` --- ### 📝 Commits (1) - [`3520cb1`](https://github.com/ArthurDanjou/website-old/commit/3520cb1b48d3d2803d44467990b36a72c8a1aece) fix(deps): bump core-js from 3.20.2 to 3.22.6 ### 📊 Changes **2 files changed** (+5 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `package.json` (+1 -1) 📝 `yarn.lock` (+4 -4) </details> ### 📄 Description Bumps [core-js](https://github.com/zloirock/core-js) from 3.20.2 to 3.22.6. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/zloirock/core-js/blob/master/CHANGELOG.md">core-js's changelog</a>.</em></p> <blockquote> <h5><a href="https://github.com/zloirock/core-js/releases/tag/v3.22.6">3.22.6 - 2022.05.23</a></h5> <ul> <li>Fixed possible double call of <code>ToNumber</code> conversion on arguments of <code>Math.{ fround, trunc }</code> polyfills</li> <li><code>Array.prototype.includes</code> marked as <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1767541">fixed</a> in FF102</li> </ul> <h5><a href="https://github.com/zloirock/core-js/releases/tag/v3.22.5">3.22.5 - 2022.05.10</a></h5> <ul> <li>Ensured that polyfilled constructors <code>.prototype</code> is non-writable</li> <li>Ensured that polyfilled methods <code>.prototype</code> is not defined</li> <li>Added detection and fix of a V8 ~ Chrome &lt;103 <a href="https://bugs.chromium.org/p/v8/issues/detail?id=12542">bug</a> of <code>struturedClone</code> that returns <code>null</code> if cloned object contains multiple references to one error</li> </ul> <h5><a href="https://github.com/zloirock/core-js/releases/tag/v3.22.4">3.22.4 - 2022.05.03</a></h5> <ul> <li>Ensured proper <code>.length</code> of polyfilled functions even in compressed code (excepting some ancient engines)</li> <li>Ensured proper <code>.name</code> of polyfilled accessors (excepting some ancient engines)</li> <li>Ensured proper source / <code>ToString</code> conversion of polyfilled accessors</li> <li>Actualized Rhino compat data</li> <li>Refactoring</li> </ul> <h5><a href="https://github.com/zloirock/core-js/releases/tag/v3.22.3">3.22.3 - 2022.04.28</a></h5> <ul> <li>Added a fix for FF99+ <code>Array.prototype.includes</code> broken on sparse arrays</li> </ul> <h5><a href="https://github.com/zloirock/core-js/releases/tag/v3.22.2">3.22.2 - 2022.04.21</a></h5> <ul> <li>Fixed <code>URLSearchParams</code> in IE8- that was broken in the previous release</li> <li>Fixed <code>__lookupGetter__</code> entries</li> </ul> <h5><a href="https://github.com/zloirock/core-js/releases/tag/v3.22.1">3.22.1 - 2022.04.20</a></h5> <ul> <li>Improved some cases of <code>RegExp</code> flags handling</li> <li>Prevented experimental warning in NodeJS ~ 18.0 on detection <code>fetch</code> API</li> <li>Added NodeJS 18.0 compat data</li> </ul> <h5><a href="https://github.com/zloirock/core-js/releases/tag/v3.22.0">3.22.0 - 2022.04.15</a></h5> <ul> <li><a href="https://github.com/tc39/proposal-change-array-by-copy">Change <code>Array</code> by copy proposal</a>: <ul> <li>Moved to Stage 3, <a href="https://github-redirect.dependabot.com/babel/proposals/issues/81#issuecomment-1083449843">March TC39 meeting</a></li> <li>Disabled forced replacement and added <code>/actual/</code> entry points for methods from this proposal</li> <li><code>Array.prototype.toSpliced</code> throws a <code>TypeError</code> instead of <code>RangeError</code> if the result length is more than <code>MAX_SAFE_INTEGER</code>, <a href="https://github-redirect.dependabot.com/tc39/proposal-change-array-by-copy/pull/70">proposal-change-array-by-copy/70</a></li> </ul> </li> <li>Added some more <code>atob</code> / <code>btoa</code> fixes: <ul> <li>NodeJS &lt;17.9 <code>atob</code> does not ignore spaces, <a href="https://github-redirect.dependabot.com/nodejs/node/issues/42530">node/42530</a></li> <li>Actual NodeJS <code>atob</code> does not validate encoding, <a href="https://github-redirect.dependabot.com/nodejs/node/issues/42646">node/42646</a></li> <li>FF26- implementation does not properly convert argument to string</li> <li>IE / Edge &lt;16 implementation have wrong arity</li> </ul> </li> <li>Added <code>/full/</code> namespace as the replacement for <code>/features/</code> since it's more descriptive in context of the rest namespaces (<code>/es/</code> ⊆ <code>/stable/</code> ⊆ <code>/actual/</code> ⊆ <code>/full/</code>)</li> <li>Avoided propagation of removed parts of proposals to upper stages. For example, <code>%TypedArray%.prototype.groupBy</code> was removed from the <code>Array</code> grouping proposal a long time ago. We can't completely remove this method since it's a breaking change. But this proposal has been promoted to stage 3 - so the proposal should be promoted without this method, this method should not be available in <code>/actual/</code> entries - but it should be available in early-stage entries to avoid breakage.</li> <li>Significant internal refactoring and splitting of modules (but without exposing to public API since it will be a breaking change - it will be exposed in the next major version)</li> <li>Bug fixes: <ul> <li>Fixed work of non-standard V8 <code>Error</code> features with wrapped <code>Error</code> constructors, <a href="https://github-redirect.dependabot.com/zloirock/core-js/issues/1061">#1061</a></li> <li><code>null</code> and <code>undefined</code> allowed as the second argument of <code>structuredClone</code>, <a href="https://github-redirect.dependabot.com/zloirock/core-js/issues/1056">#1056</a></li> </ul> </li> <li>Tooling: <ul> <li>Stabilized proposals are filtered out from the <code>core-js-compat</code> -&gt; <code>core-js-builder</code> -&gt; <code>core-js-bundle</code> output. That mean that if the output contains, for example, <code>es.object.has-own</code>, the legacy reference to it, <code>esnext.object.has-own</code>, no longer added.</li> <li>Aligned modules filters of <a href="https://github.com/zloirock/core-js/tree/master/packages/core-js-builder"><code>core-js-builder</code></a> and <a href="https://github.com/zloirock/core-js/tree/master/packages/core-js-compat"><code>core-js-compat</code></a>, now it's <code>modules</code> and <code>exclude</code> options</li> <li>Added support of entry points, modules, regexes, and arrays of them to those filters</li> <li>Missed <code>targets</code> option of <code>core-js-compat</code> means that the <code>targets</code> filter just will not be applied, so the result will contain modules required for all possible engines</li> </ul> </li> <li>Compat data:</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/zloirock/core-js/commit/d3d49a279c44a3759d9b060672a8799c3090e17a"><code>d3d49a2</code></a> 3.22.6</li> <li><a href="https://github.com/zloirock/core-js/commit/69842a47d17b5921eb688cb9d585015ff1fe27d7"><code>69842a4</code></a> mark <code>Array.prototype.includes</code> as fixed in FF102</li> <li><a href="https://github.com/zloirock/core-js/commit/f6dfcc865697f037c822e6bc5dff9a6c8ba44fef"><code>f6dfcc8</code></a> update dependencies</li> <li><a href="https://github.com/zloirock/core-js/commit/9abdd1e323656808189660f48972d34d1df4d1f0"><code>9abdd1e</code></a> update dependencies</li> <li><a href="https://github.com/zloirock/core-js/commit/572201e2263aa13c4769f053f78e801823ec3540"><code>572201e</code></a> update dependencies</li> <li><a href="https://github.com/zloirock/core-js/commit/389a10a4113f308663e0ad4835d1d7842d9940c3"><code>389a10a</code></a> improve CONTRIBUTING.md</li> <li><a href="https://github.com/zloirock/core-js/commit/a8563256a0b8e8e4e5cb318d74a210ab9147f1b0"><code>a856325</code></a> update dependencies</li> <li><a href="https://github.com/zloirock/core-js/commit/12be48b51dae8ad54e233bc57a4c334ea450e65f"><code>12be48b</code></a> fix typos</li> <li><a href="https://github.com/zloirock/core-js/commit/3002ba461dd30e9dcecc48fdec6a20b18bf05a89"><code>3002ba4</code></a> add some conversion tests</li> <li><a href="https://github.com/zloirock/core-js/commit/90a57dd0be3052cdc57b6613d7f5ce2b48d1ce27"><code>90a57dd</code></a> minor stylistic change</li> <li>Additional commits viewable in <a href="https://github.com/zloirock/core-js/compare/v3.20.2...v3.22.6">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=core-js&package-manager=npm_and_yarn&previous-version=3.20.2&new-version=3.22.6)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
arthur added the pull-request label 2025-12-01 17:06:33 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
arthur
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: arthur/website-old#270
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?