Update actions/setup-node to v4.4.0 (development) - autoclosed

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/setup-node	action	minor	v4.2.0 → v4.4.0

---

Release Notes

actions/setup-node (actions/setup-node)

v4.4.0

Compare Source

What's Changed

Bug fixes:

• Make eslint-compact matcher compatible with Stylelint by @​FloEdelmann in #​98
• Add support for indented eslint output by @​fregante in #​1245

Enhancement:

• Support private mirrors by @​marco-ippolito in #​1240

Dependency update:

• Upgrade @​action/cache from 4.0.2 to 4.0.3 by @​aparnajyothi-y in #​1262

New Contributors

• @​FloEdelmann made their first contribution in #​98
• @​fregante made their first contribution in #​1245
• @​marco-ippolito made their first contribution in #​1240

Full Changelog: actions/setup-node@v4...v4.4.0

v4.3.0

Compare Source

What's Changed

Dependency updates

• Upgrade @​actions/glob from 0.4.0 to 0.5.0 by @​dependabot in #​1200
• Upgrade @​action/cache from 4.0.0 to 4.0.2 by @​gowridurgad in #​1251
• Upgrade @​vercel/ncc from 0.38.1 to 0.38.3 by @​dependabot in #​1203
• Upgrade @​actions/tool-cache from 2.0.1 to 2.0.2 by @​dependabot in #​1220

New Contributors

• @​gowridurgad made their first contribution in #​1251

Full Changelog: actions/setup-node@v4...v4.3.0

---

Configuration

📅 Schedule: (in timezone America/Toronto)

• Branch creation
  • Between 07:00 PM and 11:59 PM, only on Sunday (* 19-23 * * 0)
  • Between 12:00 AM and 02:59 AM, only on Monday (* 0-2 * * 1)
• 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.

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

[gabemontero]

yeah @thepetk @johnmcollier @michael-valdron @JslYoon the e2e's have failed now on multiple retries

someone is going to have to try this locally and sort out whatever additional changes are needed

[HusneShabbir]

Hey @gabemontero, this is a valid failure. I can see the MCP enhancements are already included in the cluster,

but the tests haven’t been updated accordingly. I’ll need the Rolling Demo to fix the existing test flow and align it with our MCP enhancements.

I’m currently stuck with a login issue on the Rolling Demo—it’s returning a 503 API error. Once I have access, I can fix the test flow.

[gabemontero]

Hey @gabemontero, this is a valid failure. I can see the MCP enhancements are already included in the cluster,

but the tests haven’t been updated accordingly. I’ll need the Rolling Demo to fix the existing test flow and align it with our MCP enhancements.

I’m currently stuck with a login issue on the Rolling Demo—it’s returning a 503 API error. Once I have access, I can fix the test flow.

understood / thanks for looking into this @HusneShabbir

I've assigned you this PR to remind us that you are tracking this down

thanks again