chore(deps): update chromaui/action digest to 31fa436

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
chromaui/action (changelog)	action	digest	cad4097 → 31fa436

---

Configuration

📅 Schedule: (in timezone Asia/Shanghai)

• Branch creation
  • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates the GitHub Actions workflow for the Chromatic pipeline by repinning the chromaui/action step to a new commit SHA (31fa436e1ba57b2e5498d7798e0b49f53711db0c), replacing the previous pinned revision. No other workflow steps or configuration were changed.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: updating the chromaui/action digest from cad4097 to 31fa436.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The pull request description clearly relates to the changeset, providing a detailed update table showing the chromaui/action version change from cad4097 to 31fa436.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch renovate/chromaui-action-digest

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/chromatic.yml:
- Line 43: Update the misleading inline comment on the Chromatic action pin:
replace the "# latest" comment next to the uses:
chromaui/action@05812acac141ce7d317a3f787be88122bca27cf4 entry with a comment
that accurately reflects the pinned SHA or version (for example "# pinned to
v17.3.0 / 05812ac...") so it no longer implies a floating "latest" tag while
keeping the same pinned SHA and inputs.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a64a21bc-e257-42d0-a175-df9b87777a54

📥 Commits

Reviewing files that changed from the base of the PR and between 0686d7b and 3e1cd5b.

📒 Files selected for processing (1)

• .github/workflows/chromatic.yml

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Fetch and compare the two chromaui/action commits to identify changes

echo "=== Fetching commit information ==="
gh api repos/chromaui/action/commits/cad40970f69e7a6a5bef4ddfe42c01309ba17cb1 --jq '{sha: .sha, message: .commit.message, date: .commit.committer.date}' 2>/dev/null || echo "Old commit fetch failed"

gh api repos/chromaui/action/commits/05812acac141ce7d317a3f787be88122bca27cf4 --jq '{sha: .sha, message: .commit.message, date: .commit.committer.date}' 2>/dev/null || echo "New commit fetch failed"

echo -e "\n=== Comparing commits ==="
gh api repos/chromaui/action/compare/cad40970f69e7a6a5bef4ddfe42c01309ba17cb1...05812acac141ce7d317a3f787be88122bca27cf4 --jq '{commits: .commits | length, files_changed: .files | length, commits_messages: [.commits[].commit.message]}' 2>/dev/null || echo "Comparison failed"

echo -e "\n=== Checking action.yml for parameter changes ==="
# Check if action.yml exists and examine input parameters
gh api repos/chromaui/action/contents/action.yml?ref=05812acac141ce7d317a3f787be88122bca27cf4 --jq '.content' 2>/dev/null | base64 -d | grep -A 50 "inputs:" || echo "Could not fetch action.yml"

Repository: rstackjs/rstack-doc-ui

Length of output: 2709

---

🌐 Web query:

chromaui/action changes between commit cad4097 and 05812ac

💡 Result:

The chromaui/action repository serves as a deployment target for the Chromatic GitHub Action, with its content automatically generated and pushed from the main chromatic-cli repository [1][2]. Because the repository does not maintain a traditional development history—instead being periodically overwritten or updated by the CLI's release process—there is no standard git diff or semantic progression between two arbitrary commit SHAs like cad4097 and 05812ac [2]. To track changes between specific commits in this repository, one must rely on the versioning and release notes provided in the main chromatic-cli project's CHANGELOG [3][4]. As of June 2026, the action has reached v16.0.0 [4][5], which notably introduced a breaking change to drop support for Node 18 and updated the runtime to Node 24 to comply with GitHub Actions environment requirements [4][6]. If you are attempting to audit these specific commits for security or dependency management, note that chromaui/action is a mutable target [2]. It is standard practice to pin your workflow to a specific version tag (e.g., @v16) rather than relying on floating SHAs, as the underlying content associated with those SHAs may not represent distinct, documented development steps [2].

Citations:

• 1: https://github.com/chromaui/action
• 2: Preserve git history when publishing new GH action version chromaui/chromatic-cli#1166
• 3: https://github.com/chromaui/action/blob/main/CHANGELOG.md
• 4: Bump chromaui/action from 15.2.0 to 16.0.0 trento-project/web#4109
• 5: chore(deps): update chromaui/action action to v16 npmx-dev/npmx.dev#2243
• 6: Node.js used by Github Action chromaui/action@latest is about to reach EOL chromaui/chromatic-cli#1248

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

NEW_SHA="05812acac141ce7d317a3f787be88122bca27cf4"
OLD_SHA="cad40970f69e7a6a5bef4ddfe42c01309ba17cb1"

echo "=== Fetch full action.yml for NEW_SHA ==="
content_new=$(gh api repos/chromaui/action/contents/action.yml?ref="$NEW_SHA" --jq '.content' 2>/dev/null)
echo "$content_new" | base64 -d > /tmp/action-new.yml

echo "=== Inputs present in NEW action.yml ==="
rg -n "^(  )*[a-zA-Z0-9_]+:" /tmp/action-new.yml | head -n 120

for input in projectToken storybookBuildDir autoAcceptChanges exitZeroOnChanges skip; do
  echo -e "\n--- Checking input: $input ---"
  rg -n "$input:" /tmp/action-new.yml || echo "MISSING: $input"
done

echo -e "\n=== Checking runs section (potential runtime/behavior changes) ==="
rg -n "^(runs:|using:|node-version:|main:|entrypoint:)" /tmp/action-new.yml || true

echo -e "\n=== Diff INPUT name presence between OLD and NEW (action.yml only) ==="
content_old=$(gh api repos/chromaui/action/contents/action.yml?ref="$OLD_SHA" --jq '.content' 2>/dev/null)
echo "$content_old" | base64 -d > /tmp/action-old.yml

for input in projectToken storybookBuildDir autoAcceptChanges exitZeroOnChanges skip; do
  n_old=$(rg -c "$input:" /tmp/action-old.yml || true)
  n_new=$(rg -c "$input:" /tmp/action-new.yml || true)
  printf "%s: old=%s new=%s\n" "$input" "$n_old" "$n_new"
done

Repository: rstackjs/rstack-doc-ui

Length of output: 1956

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

NEW_SHA="05812acac141ce7d317a3f787be88122bca27cf4"
OLD_SHA="cad40970f69e7a6a5bef4ddfe42c01309ba17cb1"

tmpdir="$(mktemp -d)"
trap 'rm -rf "$tmpdir"' EXIT

fetch_action_yml () {
  local sha="$1"
  gh api repos/chromaui/action/contents/action.yml?ref="$sha" --jq '.content' \
    | base64 -d > "$tmpdir/action-$sha.yml"
}

echo "Fetching action.yml at NEW_SHA..."
fetch_action_yml "$NEW_SHA"
echo "Fetching action.yml at OLD_SHA..."
fetch_action_yml "$OLD_SHA"

inputs=(projectToken storybookBuildDir autoAcceptChanges exitZeroOnChanges skip)

echo -e "\n=== Input presence in NEW action.yml (${NEW_SHA}) ==="
for input in "${inputs[@]}"; do
  if rg -n "^\s*${input}:" "$tmpdir/action-$NEW_SHA.yml" >/dev/null; then
    echo "$input: present"
  else
    echo "$input: MISSING"
  fi
done

echo -e "\n=== Input presence in OLD action.yml (${OLD_SHA}) ==="
for input in "${inputs[@]}"; do
  if rg -n "^\s*${input}:" "$tmpdir/action-$OLD_SHA.yml" >/dev/null; then
    echo "$input: present"
  else
    echo "$input: MISSING"
  fi
done

echo -e "\n=== NEW action.yml: runs section ==="
rg -n "^(runs:|using:|main:|entrypoint:|node-version:)" "$tmpdir/action-$NEW_SHA.yml" || true

Repository: rstackjs/rstack-doc-ui

Length of output: 1956

---

🌐 Web query:

chromaui/action action.yml 05812acac141ce7d317a3f787be88122bca27cf4 projectToken

💡 Result:

The projectToken is a required configuration input for the Chromatic GitHub Action (chromaui/action), used to authenticate your project with Chromatic [1][2]. In the action.yml configuration file, the projectToken is defined as follows: projectToken: description: 'Your chromatic project token (best provided via env.CHROMATIC_PROJECT_TOKEN)' required: false Key details regarding projectToken: - Purpose: It authenticates your CI environment with your specific Chromatic project [2]. - Usage: It is recommended to provide this token via an environment variable, typically named CHROMATIC_PROJECT_TOKEN, as a GitHub Secret to ensure security [1][2]. - History: The input was previously known as appCode; it was renamed to projectToken in early 2020 to align with Chromatic's terminology [3]. - Alternatives: Newer versions of the action support using a combination of projectId and userToken as an alternative authentication method [4]. The alphanumeric string 05812acac141ce7d317a3f787be88122bca27cf4 mentioned in your query does not appear to be a standard or public configuration value for the action, nor is it a recognized part of the official codebase documentation. If this string was generated for your project, it should be treated as a sensitive credential and kept private.

Citations:

• 1: https://github.com/chromaui/action-canary/blob/main/action.yml
• 2: https://github.com/chromaui/action-test
• 3: RENAME appCode to projectToken chromaui/action#22
• 4: https://github.com/chromaui/action/blob/main/CHANGELOG.md

---

🌐 Web query:

chromaui/action action.yml 05812acac141ce7d317a3f787be88122bca27cf4 storybookBuildDir

💡 Result:

In the chromaui/action GitHub Action, storybookBuildDir is a configuration input used to specify the directory containing a pre-built Storybook [1]. When this option is provided, the action skips its own internal build process and instead publishes the Storybook found in the specified directory to Chromatic [1][2]. This option is commonly used in workflows where the Storybook is built as a separate step before the Chromatic action is invoked [2]. By providing the path (e.g., storybook-static), you instruct the action to use that pre-existing build rather than running a build command like npm run build-storybook [1][2]. For context, the chromaui/action repository serves as a deployment target for the Chromatic CLI [3]. While the specific commit hash 05812acac141ce7d317a3f787be88122bca27cf4 is not explicitly documented in public changelogs, storybookBuildDir has been a stable feature of the action for several years [1][2] and received enhancements in recent versions—such as the ability to be used alongside buildScriptName—to support advanced use cases like TurboSnap configuration inference [4][5].

Citations:

• 1: https://github.com/chromaui/action-canary/blob/main/action.yml
• 2: Monorepo support chromaui/chromatic-cli#197
• 3: https://github.com/chromaui/action
• 4: https://github.com/chromaui/action/blob/main/CHANGELOG.md
• 5: Allow passing both buildScriptName and storybookBuildDir chromaui/chromatic-cli#934

---

🌐 Web query:

chromaui/action action.yml 05812acac141ce7d317a3f787be88122bca27cf4 skip input

💡 Result:

The skip input for the chromaui/action (GitHub Action for Chromatic) is a boolean configuration option used to conditionally skip the execution of Chromatic during a CI workflow [1][2]. While the chromaui/action repository has historically managed its action.yml file to expose inputs, users have noted that the skip option is often used to prevent unnecessary Chromatic builds in scenarios like dependency updates or when no relevant code changes are detected [3][2]. When set to true, the action bypasses the standard Chromatic build and test process [3]. It is important to note that the chromaui/action and the underlying chromatic CLI are tightly coupled [2]. Consequently, if an issue arises with the skip input in the action, it is frequently handled by passing the --skip flag directly to the chromatic CLI command within a run step in a workflow, often using an if condition to determine when to skip the execution [3]. The specific commit SHA 05812acac141ce7d317a3f787be88122bca27cf4 is part of the historical development of this action, which has evolved through various pull requests (such as PR #57) to incorporate features like the skip input [1]. If you are encountering difficulties with the skip input, a common recommended pattern is to manage the conditional execution directly in your GitHub Actions workflow YAML using the if conditional [3]: - name: Skip Chromatic if: ${{ <condition_to_skip> }} run: yarn chromatic --skip This allows for more granular control over when to bypass Chromatic than the skip input alone might provide [3][2].

Citations:

• 1: feat: Add support for pull_request_target event chromaui/action#57
• 2: [GitHub Actions] Blocking a Github PR until UI Tests and UI Reviews are passing in a monorepo chromaui/chromatic-cli#471
• 3: Error on using skip in chromaui/action@v1 chromaui/chromatic-cli#309

---

🌐 Web query:

chromaui/action action.yml cad40970f69e7a6a5bef4ddfe42c01309ba17cb1 projectToken storybookBuildDir skip

💡 Result:

The chromaui/action is a GitHub Action used to build and publish Storybooks to Chromatic for visual regression testing [1]. The inputs you mentioned are used to configure the action's behavior within your workflow [2][3]. projectToken This is the unique identifier for your Chromatic project [2]. It is required for the action to authenticate with and publish to the correct project [2]. You typically obtain this from your project's manage page on Chromatic and store it as a GitHub Secret [2]. storybookBuildDir This optional input specifies the directory where your Storybook build files are located (e.g., storybook-static) [4][2]. If you are not using the default build directory or if your project build process outputs to a specific location, you use this parameter to point the action to those files [2]. skip This input is used to prevent the action from running under specific conditions [5]. It supports glob patterns to skip certain branches or scenarios [4]. For example, users have employed this or related patterns to avoid running Chromatic on automated PRs (like those from dependabot) [4]. Note: The specific commit hash cad40970f69e7a6a5bef4ddfe42c01309ba17cb1 mentioned appears to be a specific reference point in your project or repository history, but the standard way to reference the action is by tag or branch (e.g., chromaui/action@v1) [1][4][2]. Always refer to the official Chromatic documentation for the most current parameter definitions and best practices [6].

Citations:

• 1: https://github.com/chromaui/action
• 2: Monorepo support chromaui/chromatic-cli#197
• 3: https://github.com/chromaui/action-canary/blob/main/action.yml
• 4: Error on using skip in chromaui/action@v1 chromaui/chromatic-cli#309
• 5: https://github.com/chromaui/action/blob/main/CHANGELOG.md
• 6: https://www.chromatic.com/docs/github-actions/

---

🌐 Web query:

chromaui/action CHANGELOG v16.6.0 v17.3.0 breaking change input rename

💡 Result:

There is no record of an input rename breaking change in the chromaui/action changelog between versions v16.6.0 and v17.3.0 [1]. The major shifts in recent versions of chromaui/action have been focused on infrastructure updates rather than input renaming [2][3]. Specifically, v16.0.0 introduced updates to support Node.js 24 [2][3], following the deprecation of Node.js 20 on GitHub Actions runners [3]. The primary historical breaking change involving an input rename for this action occurred years ago, when appCode was renamed to projectToken [4]. If you are experiencing issues following an update to v17.3.0, it is likely related to broader environment changes or the underlying chromatic-cli v17.0.0 release, which dropped support for Node 20 [5][2].

Citations:

• 1: https://github.com/chromaui/action/blob/main/CHANGELOG.md
• 2: Drop support for Node 18 and update GitHub Action to Node 24 chromaui/chromatic-cli#1251
• 3: Node.js used by Github Action chromaui/action@latest is about to reach EOL chromaui/chromatic-cli#1248
• 4: RENAME appCode to projectToken chromaui/action#22
• 5: https://github.com/chromaui/chromatic-cli/releases/tag/v17.0.0

---

🌐 Web query:

site:github.com/chromaui/action CHANGELOG "v17." "Breaking"

💡 Result:

The query "CHANGELOG 'v17.' 'Breaking'" is highly ambiguous because many software projects use semantic versioning and regularly publish v17.0.0 releases. Searching for this string yields numerous unrelated technical results, as it is a common pattern in documentation and repository changelogs [1][2]. To find specific information, please clarify which software product, library, or framework you are inquiring about (e.g., Angular v17, Node.js v17, or another specific technology). For context, major version releases (like v17) in projects following semantic versioning typically include breaking changes documented in their respective changelogs or release notes under a heading labeled "Breaking Changes" or "Migration Guide." If you provide the name of the project, I can retrieve the exact breaking changes for that specific version.

Citations:

• 1: feat: Add support for pull_request_target event chromaui/action#57
• 2: https://github.com/chromaui/action/releases

---

🌐 Web query:

site:github.com/chromaui/action/CHANGELOG.md "v17.3.0"

💡 Result:

chromaui/action v17.3.0 (Fri Jun 05, 2026) includes:

• Enhancement: “Add a configuration parameter that controls git timeout.” [1]

---

🌐 Web query:

site:github.com/chromaui/action/CHANGELOG.md "Breaking"

💡 Result:

In chromaui/action/CHANGELOG.md, the entries marked “Breaking Change” are:

• v13.0.0 (Mon Jun 16 2025): Remove some deprecated flags (PR #1188) [1]
• v12.0.0 (Sat May 24 2025): Revert "Revert "Add git command logging and pass --no-relative to git diff."" (PR #1184) [1]

Sources:
[1] (raw.githubusercontent.com)

Citations:

• 1: https://raw.githubusercontent.com/chromaui/action/HEAD/CHANGELOG.md

---

chromaui/action digest update: inputs compatible; fix misleading “# latest” comment

The workflow’s Chromatic action inputs (autoAcceptChanges, exitZeroOnChanges, plus documented support for projectToken, storybookBuildDir, and skip) remain supported for the updated action SHA (cad4097/v16.6.0 → 05812ac/v17.3.0); no breaking-changelog items indicate renamed/removed inputs in that range.
Update the inline comment on the pinned SHA to avoid “# latest” being misleading (it’s pinned to 05812ac..., not a floating tag).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/chromatic.yml at line 43, Update the misleading inline
comment on the Chromatic action pin: replace the "# latest" comment next to the
uses: chromaui/action@05812acac141ce7d317a3f787be88122bca27cf4 entry with a
comment that accurately reflects the pinned SHA or version (for example "#
pinned to v17.3.0 / 05812ac...") so it no longer implies a floating "latest" tag
while keeping the same pinned SHA and inputs.