Bump the npm group across 1 directory with 5 updates

[dependabot]

Bumps the npm group with 5 updates in the / directory:

Package	From	To
@activeadmin/activeadmin	3.5.1	3.5.2
@fortawesome/fontawesome-free	7.2.0	7.3.1
arctic_admin	4.3.3	4.4.1
esbuild	0.28.1	0.28.2
sass	1.99.0	1.102.0

Updates @activeadmin/activeadmin from 3.5.1 to 3.5.2

Release notes

Sourced from @​activeadmin/activeadmin's releases.

v3.5.2

What's Changed

Bug Fixes

• Backport PR #7437 to 3-0-stable - run update_resource inside a transaction by @​mgrunberg in activeadmin/activeadmin#9064

Chore

• Use keyword to: in page_routes by @​tagliala in activeadmin/activeadmin#9020

Full Changelog: activeadmin/activeadmin@v3.5.1...v3.5.2

Changelog

Sourced from @​activeadmin/activeadmin's changelog.

3.5.2 ☰

Bug Fixes

• Backport run update_resource inside a transaction to avoid autosaving relationships through assign_attributes when the record is invalid #9064 by [@​mgrunberg] and [@​deivid-rodriguez]

Commits

• d604c94 Release/3.5.2 (#9065)
• 46db435 Backport PR #7437 to 3-0-stable - run update_resource inside a transaction (#...
• 8180d35 Use keyword to: in page_routes (#9020)
• See full diff in compare view

Updates @fortawesome/fontawesome-free from 7.2.0 to 7.3.1

Release notes

Sourced from @​fortawesome/fontawesome-free's releases.

Release 7.3.1

Change log available at https://fontawesome.com/docs/changelog/

Release 7.3.0

Change log available at https://fontawesome.com/docs/changelog/

Commits

• 14c65a3 Release 7.3.1 (#21630)
• 70fb2dd Release 7.3.0 (#21612)
• See full diff in compare view

Maintainer changes

This version was pushed to npm by fortawesome-admin, a new releaser for @​fortawesome/fontawesome-free since your current version.

Updates arctic_admin from 4.3.3 to 4.4.1

Release notes

Sourced from arctic_admin's releases.

v4.4.1

• ✨ Créer une GitHub Release avec les commits depuis le tag précédent

Commits

• f85a904 🔖 Set version 4.4.1
• e6862be ✨ Créer une GitHub Release avec les commits depuis le tag précédent
• f710455 🐛 Ajouter actions/checkout manquant dans gem-push.yml
• d1efe3a 🔖 Set version 4.4.0
• a5d9891 ✨ Ajouter le script de release interactif
• 2947bbe Add null guard to main.js
• 8072f23 Merge pull request #124 from tagliala/bugfix/123-fix-sass-warnings
• f3d4709 Merge branch 'main' into bugfix/123-fix-sass-warnings
• 98c7f8f ♻️
• 7ef0ef1 ♻️ Extract variables borders et box-shadow
• Additional commits viewable in compare view

Updates esbuild from 0.28.1 to 0.28.2

Release notes

Sourced from esbuild's releases.

v0.28.2

• Fix tree shaking bug due to TypeScript import alias (#4507)

  This release fixes a bug that could cause esbuild to incorrectly tree-shake imports that are used in a TypeScript type alias under certain circumstances. Affected code uses a TypeScript-specific import assignment and looks something like this:

  import Base from './dep.js';
  import Alias = Base.SomeType;

• Fix CSS minification bug involving & (#4497)

  This release fixes a bug where esbuild's CSS minifier incorrectly removed a & when it was unsafe to do so. Here is an example:

  /* Original code */
  .a .b {
    & .b:not(& .c) {
      color: red;
    }
  }
  /* Old output (with --minify) */
  .a .b{.b:not(& .c){color:red}}
  /* New output (with --minify) */
  .a .b{& .b:not(& .c){color:red}}

  This should match <span class="a"><span class="b"><span class="b">yes</span></span></span> but not <span class="a"><span class="b">no</span></span>. The old output incorrectly matched both.

• Avoid overwriting input files without --allow-overwrite (#4484)

  For example: esbuild input.js --outfile=input.js tells esbuild to overwrite input.js with the output of running esbuild on it. This was supposed to already be prevented by default, but it accidentally regressed in version 0.17.0 and apparently didn't have any test coverage. The error message was being printed but the input file was still being overwritten. Oops.

  This release puts the original behavior back. With this release, esbuild should now actually avoid overwriting input files unless --allow-overwrite is explicitly present. This is done by not writing out any files when a build error is encountered.

• Fix incorrect code generated when using top-level await (#4498)

  Previously esbuild could generate code containing a syntax error in complex scenarios involving top-level await used in a dependency cycle. The problem was a missing async on one or more module wrapper closures. With this release, esbuild now uses a fixed-point iteration algorithm to correctly annotate all dependencies in the cycle as needing an async module wrapper.

• Fix a minification bug with lowered logical assignment operators (#4508)

  This release fixes a bug that could cause esbuild to generate incorrect code for logical assignment operators when lowering them to an older target environment. Specifically the lowering process requires duplicating the left-hand side, but esbuild incorrectly failed to count the duplicate as a new usage when the left-hand side is an identifier. That then caused the minifier to believe that the left-hand side was only used once and could attempt to incorrectly inline an initializer into the first usage. This bug has now been fixed:

  // Original code
  function foo() {
    let x
    bar(x ||= {})

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.28.2

• Fix tree shaking bug due to TypeScript import alias (#4507)

  This release fixes a bug that could cause esbuild to incorrectly tree-shake imports that are used in a TypeScript type alias under certain circumstances. Affected code uses a TypeScript-specific import assignment and looks something like this:

  import Base from './dep.js';
  import Alias = Base.SomeType;

• Fix CSS minification bug involving & (#4497)

  This release fixes a bug where esbuild's CSS minifier incorrectly removed a & when it was unsafe to do so. Here is an example:

  /* Original code */
  .a .b {
    & .b:not(& .c) {
      color: red;
    }
  }
  /* Old output (with --minify) */
  .a .b{.b:not(& .c){color:red}}
  /* New output (with --minify) */
  .a .b{& .b:not(& .c){color:red}}

  This should match <span class="a"><span class="b"><span class="b">yes</span></span></span> but not <span class="a"><span class="b">no</span></span>. The old output incorrectly matched both.

• Avoid overwriting input files without --allow-overwrite (#4484)

  For example: esbuild input.js --outfile=input.js tells esbuild to overwrite input.js with the output of running esbuild on it. This was supposed to already be prevented by default, but it accidentally regressed in version 0.17.0 and apparently didn't have any test coverage. The error message was being printed but the input file was still being overwritten. Oops.

  This release puts the original behavior back. With this release, esbuild should now actually avoid overwriting input files unless --allow-overwrite is explicitly present. This is done by not writing out any files when a build error is encountered.

• Fix incorrect code generated when using top-level await (#4498)

  Previously esbuild could generate code containing a syntax error in complex scenarios involving top-level await used in a dependency cycle. The problem was a missing async on one or more module wrapper closures. With this release, esbuild now uses a fixed-point iteration algorithm to correctly annotate all dependencies in the cycle as needing an async module wrapper.

• Fix a minification bug with lowered logical assignment operators (#4508)

  This release fixes a bug that could cause esbuild to generate incorrect code for logical assignment operators when lowering them to an older target environment. Specifically the lowering process requires duplicating the left-hand side, but esbuild incorrectly failed to count the duplicate as a new usage when the left-hand side is an identifier. That then caused the minifier to believe that the left-hand side was only used once and could attempt to incorrectly inline an initializer into the first usage. This bug has now been fixed:

  // Original code
  function foo() {
    let x

... (truncated)

Commits

• 609683d publish 0.28.2 to npm
• 11b1fe4 add to release notes
• ab50d91 css: fix green/blue channel swap in oklch gamut mapping (#4488)
• 04627b6 fix #4498: async TLA checks need a worklist
• 5c15177 disable gopls in the go folder
• fc2ee9b css: adjust parser to allow --foo: {...}
• 209db54 release notes for css nesting bugfix
• c625d31 fix #4497: preserve nested ampersands during minification (#4500)
• 34474e2 better isolation of current part in js parser
• 07f6e8c fix #4507: import assignment tree-shaking bug
• Additional commits viewable in compare view

Updates sass from 1.99.0 to 1.102.0

Release notes

Sourced from sass's releases.

Dart Sass 1.102.0

To install Sass 1.102.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

• Use the 2.4 gamma transfer function for rec2020, as specified by the latest draft of CSS Color 4.

See the full changelog for changes in earlier releases.

Dart Sass 1.101.7

To install Sass 1.101.7, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

• No user-visible changes.

See the full changelog for changes in earlier releases.

Dart Sass 1.101.6

To install Sass 1.101.6, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

• No user-visible changes.

See the full changelog for changes in earlier releases.

Dart Sass 1.101.5

To install Sass 1.101.5, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

• No user-visible changes.

See the full changelog for changes in earlier releases.

Dart Sass 1.101.4

To install Sass 1.101.4, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

... (truncated)

Changelog

Sourced from sass's changelog.

1.102.0

• Use the 2.4 gamma transfer function for rec2020, as specified by the latest draft of CSS Color 4.

1.101.7

• No user-visible changes.

1.101.6

• No user-visible changes.

1.101.5

• No user-visible changes.

1.101.4

• Avoid emitting rgb() or rgba() functions with non-percent decimal channels. Older browsers only support integer values or (potentially decimal) percentages for these functions, so in order to preserve backwards-compatibility while retaining full precision for modern browsers, legacy colors that contain at least one non-integer channel will now use percentages for their channels (for example, rgb(0%, 100%, 50%) rather than rgb(0, 255, 127.5)).

• Fix a bug where the values of plain-CSS if() expressions were emitted using their meta.inspect() format rather than their CSS serialization format.

1.101.3

• No user-visible changes.

1.101.2

• Fix a bug where the deprecation warning for vendor-prefixed expression() functions would incorrectly indicate whether or not the function would be invalid Sass in Dart Sass 2.0.0.

1.101.1

• Sass stack trace entries are now always either absolute URLs, absolute paths, or paths relative to the current working directory. Previously, if a stylesheet was loaded using a relative URL (as from a load path), that relative URL was listed even if it couldn't be resolved relative to the current working directory. However, this created potential ambiguities, so this behavior has been removed.

Command Line Interface

... (truncated)

Commits

• 45d1efe Use gamma 2.40 for display-referred rec2020 (#2729)
• 96aa291 Persist credentials on all repos we push to (#2812)
• 5af0b89 Set the Git committer for release tasks (#2811)
• 2cecbbb Fix more issues downstream from Zizmor (#2809)
• a16f014 Emit floating-point rgb() values as percentages (#2800)
• 4ed2c88 Serialize if() values as CSS, not as inspected values (#2808)
• 9dfde3d Fix more post-Zizmor failures (#2806)
• e8c1233 Fix some GitHub actions issues introduced by the Zizmor refactor (#2798)
• d676118 Merge pull request #2797 from sass/lints
• 548e660 Prefer interpolation to compose strings
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions