Update dependencies (patch)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence	Type	Update
@thejaredwilcurt/csslop	^0.0.16 → ^0.0.17			devDependencies	patch
actions/checkout	v7.0.0 → v7.0.1			action	patch
eslint-plugin-jsdoc	63.2.0 → 63.2.2			devDependencies	patch
jdx/mise-action	v4.2.0 → v4.2.3			action	patch
postcss (source)	8.5.21 → 8.5.23			devDependencies	patch
sass	1.101.3 → 1.101.7			devDependencies	patch

---

Release Notes

TheJaredWilcurt/csslop (@​thejaredwilcurt/csslop)

v0.0.17: - URL(), HSL(from calc), @​custom-media, & Nesting

Compare Source

Adds 20 new tests.

actions/checkout (actions/checkout)

v7.0.1

Compare Source

• Bump github/codeql-action from 3 to 4 by @​dependabot[bot] in #​2475
• Bump actions/setup-node from 4 to 6 by @​dependabot[bot] in #​2477
• Bump docker/build-push-action from 6.5.0 to 7.2.0 by @​dependabot[bot] in #​2478
• Bump docker/login-action from 3.3.0 to 4.2.0 by @​dependabot[bot] in #​2479
• Bump actions/checkout from 6 to 7 by @​dependabot[bot] in #​2488
• Bump actions/upload-artifact from 4 to 7 by @​dependabot[bot] in #​2476
• eslint 9 by @​dependabot[bot] in #​2474
• Bump the minor-actions-dependencies group with 2 updates by @​dependabot[bot] in #​2499
• skip running unsafe pr check if input is default by @​aiqiaoy in #​2518
• trim only ascii whitespace for branch by @​aiqiaoy in #​2521
• escape values passed to --unset by @​aiqiaoy in #​2530

gajus/eslint-plugin-jsdoc (eslint-plugin-jsdoc)

v63.2.2

Compare Source

v63.2.1

Compare Source

jdx/mise-action (jdx/mise-action)

v4.2.3

Compare Source

v4.2.2

Compare Source

v4.2.1: : Signed checksums and PATH export fix

Compare Source

A small patch release with two user-facing fixes: mise downloads are now verified against minisign-signed release checksums by default, and the env input no longer leaks the runner's PATH into subsequent steps.

Fixed

Verify mise downloads with signed checksums (#​548) by @​jdx

The action now embeds mise's minisign public key and verifies SHASUMS256.txt.minisig before trusting any release checksums, then checks the downloaded mise binary's SHA256 against the verified list. This applies to both GitHub release archives (verified before extraction) and the default mise.jdx.dev CDN path (verified against the signed checksum for the matching release asset). If a CDN download fails verification, the action warns and falls back to the signed GitHub release asset instead of installing an unverified binary.

• The existing sha256 input still works as an explicit override.
• Pinned mise versions older than 2024.12.24 (which predate minisign checksums) get a warning and skip signed verification rather than failing.
• Because tar installs now extract from a verified file on disk, the previous streaming download | tar fast path is replaced with a download-then-verify-then-extract flow.

Thanks to @​potiuk for the detailed threat-model writeup in #​547.

Exclude PATH from environment export (#​556) by @​jdx

The env input has always documented that "PATH modifications are not part of this", but since the switch to mise env --json in #​252 (needed for redaction support), the action was exporting every string value returned by mise — including the computed PATH — into GITHUB_ENV. That effectively snapshotted the runner's entire PATH into subsequent steps and let [env] _.path entries in mise.toml leak past the action's own PATH management.

exportMiseEnv now skips PATH (case-insensitive) when exporting JSON env vars, restoring the documented behavior. Normal mise env vars are still exported, and PATH continues to be managed by the action's own setup (e.g. add_shims_to_path). Fixes #​555.

Full Changelog: jdx/mise-action@v4.2.0...v4.2.1

postcss/postcss (postcss)

v8.5.23

Compare Source

• Do not load source map without opts.from for security reasons.

v8.5.22

Compare Source

• Fixed custom property losing semicolon before a comment (by @​sarathfrancis90).

sass/dart-sass (sass)

v1.101.7

Compare Source

• No user-visible changes.

v1.101.6

Compare Source

• No user-visible changes.

v1.101.5

Compare Source

• No user-visible changes.

v1.101.4

Compare Source

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

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 9am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code EBADDEVENGINES
npm error EBADDEVENGINES The developer of this package has specified the following through devEngines
npm error EBADDEVENGINES Invalid devEngines.runtime
npm error EBADDEVENGINES Invalid semver version "26.5.0" does not match "v24.18.0" for "runtime"
npm error EBADDEVENGINES {
npm error EBADDEVENGINES   current: { name: 'node', version: 'v24.18.0' },
npm error EBADDEVENGINES   required: { name: 'node', version: '26.5.0' }
npm error EBADDEVENGINES }
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-07-25T14_11_23_794Z-debug-0.log