chore(deps): bump chromaui/action from 17 to 18

[dependabot]

Bumps chromaui/action from 17 to 18.

Commits

• 14cfaef v18.1.0
• 94713c5 v18.0.1
• b5b5751 v18.0.0
• See full diff 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 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)

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[pkg-pr-new]

Open in StackBlitz

@faststore/api

npm i https://pkg.pr.new/vtex/faststore/@faststore/api@32cf6c5

@faststore/cli

npm i https://pkg.pr.new/vtex/faststore/@faststore/cli@32cf6c5

@faststore/components

npm i https://pkg.pr.new/vtex/faststore/@faststore/components@32cf6c5

@faststore/core

npm i https://pkg.pr.new/vtex/faststore/@faststore/core@32cf6c5

@faststore/diagnostics

npm i https://pkg.pr.new/vtex/faststore/@faststore/diagnostics@32cf6c5

@faststore/lighthouse

npm i https://pkg.pr.new/vtex/faststore/@faststore/lighthouse@32cf6c5

@faststore/sdk

npm i https://pkg.pr.new/vtex/faststore/@faststore/sdk@32cf6c5

@faststore/ui

npm i https://pkg.pr.new/vtex/faststore/@faststore/ui@32cf6c5

commit: 32cf6c5

[sonar-workflows]

Quality Gate passed

Issues

• 0 New Issues
• 0 Fixed Issues
• 0 Accepted Issues

Measures

• 0 Security Hotspots
• No data about coverage (28.60% Estimated after merge)
• No data about duplications (1.60% Estimated after merge)

Project ID: vtex_faststore_f0a862d5-9557-49f9-8d09-de40caa76622

View in SonarQube

[renatomaurovtex]

Reviewing as part of the daily PR sweep. One-line CI bump: chromaui/action v17 → v18 on the Chromatic publish step.

Compatibility checks out on paper: chromatic 18.x requires node >=22 and the step runs after setup-node with 24.13.0 ✓; the repo's Storybook is v10.2.3, which the v18 CLI line supports ✓. Existing inputs (projectToken, workingDir, onlyChanged, etc.) are unchanged in v18.

🟡 This is the one bump the PR's own CI cannot validate. The failing "Publish to Chromatic" step here is the usual missing-CHROMATIC_PROJECT_TOKEN-on-dependabot pattern (#3361) — meaning the exact step this PR changes never actually executes with v18 before merge. Worst case is a broken Chromatic publish on dev discovered after the fact. Suggest either (a) a maintainer pushes any trivial commit to this branch so secrets become available and the step runs for real, or (b) whoever merges watches the first post-merge Chromatic run on dev and is ready to revert this one-liner.

💬 Same-day sibling #3427 (setup-node v7) touches the same ci.yml; merge order doesn't matter, just expect a rebase on whichever lands second.

Verdict: Approved with comments

Blocking (🔴/🟠):

• None.

Non-blocking (🟡/💬):

• 🟡 v18 is unverifiable on this PR (Chromatic step skipped by missing dependabot token) — validate via maintainer commit on the branch, or watch the first post-merge run on dev.

Checks to confirm before merge: first Chromatic run with v18 (on-branch via maintainer push, or immediately post-merge on dev).