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.0	0.28.1
sass	1.99.0	1.101.7

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.0 to 0.28.1

Release notes

Sourced from esbuild's releases.

v0.28.1

• Disallow \ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

  This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \ are no longer allowed.

  Thanks to @​dellalibera for reporting this issue.

• Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

  The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

  Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

  Thanks to @​sondt99 for reporting this issue.

• Avoid inlining using and await using declarations (#4482)

  Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:

  // Original code
  {
    using x = new Resource()
    x.activate()
  }
  // Old output (with --minify)
  new Resource().activate();
  // New output (with --minify)
  {using e=new Resource;e.activate()}

• Fix module evaluation when an error is thrown (#4461, #4467)

  If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.

• Fix some edge cases around the new operator (#4477)

  Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:

  // Original code
  new (foo()`bar`)()
  new (foo()?.bar)()
  // Old output
  new foo()bar();
  new (foo())?.bar();

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.28.1

• Disallow \ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

  This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \ are no longer allowed.

  Thanks to @​dellalibera for reporting this issue.

• Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

  The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

  Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

  Thanks to @​sondt99 for reporting this issue.

• Avoid inlining using and await using declarations (#4482)

  Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:

  // Original code
  {
    using x = new Resource()
    x.activate()
  }
  // Old output (with --minify)
  new Resource().activate();
  // New output (with --minify)
  {using e=new Resource;e.activate()}

• Fix module evaluation when an error is thrown (#4461, #4467)

  If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.

• Fix some edge cases around the new operator (#4477)

  Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:

  // Original code
  new (foo()`bar`)()
  new (foo()?.bar)()
  // Old output
  new foo()bar();
  new (foo())?.bar();

... (truncated)

Commits

• bb9db84 publish 0.28.1 to npm
• 9ff053e security: add integrity checks to the Deno API
• 0a9bf21 enforce non-negative size in gzip parser
• e2a1a71 security: forbid \\ in local dev server requests
• 83a2cbf fix #4482: don't inline using declarations
• 308ad74 fix #4471: renaming of nested var declarations
• f013f5f fix some typos
• aafd6e4 chore: fix some minor issues in comments (#4462)
• 15300c3 follow up: cjs evaluation fixes
• 1bda0c3 fix #4461, fix #4467: esm evaluation fixes
• Additional commits viewable in compare view

Updates sass from 1.99.0 to 1.101.7

Release notes

Sourced from sass's 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.

Changes

• 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.

See the full changelog for changes in earlier releases.

... (truncated)

Changelog

Sourced from sass's changelog.

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

• --watch mode now handles atomically-written files more gracefully.

1.101.0

... (truncated)

Commits

• 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
• b443ffe Use function type syntax
• Additional commits viewable in compare view