Bump shakacode/react_on_rails/.github/workflows/demo-fleet-smoke.yml from 613c6c2a251a782328b26d68e7f23daa9b677497 to 01826618914c6db92dc8a799d8b983b4512a5aa5

[dependabot]

Bumps shakacode/react_on_rails/.github/workflows/demo-fleet-smoke.yml from 613c6c2a251a782328b26d68e7f23daa9b677497 to 01826618914c6db92dc8a799d8b983b4512a5aa5.

Changelog

Sourced from shakacode/react_on_rails/.github/workflows/demo-fleet-smoke.yml's changelog.

Change Log

All notable changes to this project's source code will be documented in this file. Items under Unreleased is upcoming features that will be out in the next version.

This is the unified changelog for both React on Rails (open source) and React on Rails Pro. Pro-specific changes are tagged inline with [Pro]. For pre-monorepo Pro history (versions 4.0.0-rc.15 and earlier), see the archived Pro CHANGELOG.

Migration instructions for the major updates can be found here. Some smaller migration information can be found here.

Want to Save Time Updating?

If you need help upgrading react_on_rails, webpacker to shakapacker, or JS packages, contact justin@shakacode.com. We can upgrade your project and improve your development and customer experiences, allowing you to focus on building new features or fixing bugs instead.

For an overview of working with us, see our Client Engagement Model article and how we bill for time.

If you think ShakaCode can help your project, click here to book a call with Justin Gordon, the creator of React on Rails and Shakapacker.

Contributors

Please follow the recommendations outlined at keepachangelog.com. Please use the existing headings and styling as a guide. After a release, run /update-changelog in Claude Code to analyze commits, write entries, and create a PR. Alternatively, run bundle exec rake update_changelog to add version headers only (you must write entries manually).

Versions

[Unreleased]

Fixed

• [Pro] Bounded Node Renderer VM retention now avoids old/new RSC rebuild thrash during rolling deploys: The default per-worker VM hard cap now retains four contexts, enough for the server and RSC bundles from one draining and one current revision. Successful bundle sets remain reusable through a configurable, timer-driven drain window, while inactive contexts, generation metadata, and pressure logs stay bounded. Pre-seeding now emits an immutable revision-scoped current-generation declaration; each configured renderer worker validates and compiles that complete server/RSC set before listening, pins it across old-only traffic gaps, and reports ready only after the compile barrier. Symlink-mode cache paths reuse the validated immutable snapshot VM identity without rebuilding on the first request. Doctor now requires valid renderer JavaScript before launcher-derived capacity can prove a warm pass, and reports observed/unverified declaration evidence rather than claiming success from invalid syntax, loopback, or Rails-process configuration. Upgrade memory impact: the default maxVMPoolSize doubles from 2 to 4 per worker, and total VM retention scales with renderer workers and replicas, so operators should re-check deployment memory requests and limits. Invalid MAX_VM_POOL_SIZE values that previously fell back to the default now fail fast during renderer startup. Fixes Issue 4810. PR 4811 by justin808.

• Routine startup diagnostics no longer appear in default INFO logs: Successful package validation, valid Pro license checks, non-production missing-license notices, and Node renderer connection setup now log at DEBUG instead of INFO. Package validation still runs, while expired or invalid configured licenses remain visible outside production, and production license warnings and renderer failures remain actionable. Fixes Issue 4848.

... (truncated)

Commits

• 0182661 Pin the prewarmed renderer generation across rolling deploys (#4811)
• 4ea98a7 Preserve merge queue submission policy (#4872)
• 059fc1a PPR: define settle criterion for all three prerender abort points (#4855)
• b442e90 Benchmarks: discover v2 Node Renderer bundles (#4858)
• f4a1bde Internal: add isolated credential broker for Pro app evals (#4854)
• 65a8269 Benchmarks: support license-free Pro preflight (#4853)
• 39399e9 Silence routine startup diagnostics for Rails commands (#4849)
• cd04013 Docs: move agent coordination to the HTTP backend (#4764)
• 9d2f878 Detect unnoticed changes across generated webpack/Rspack configs (#4839)
• 9780839 Fix durable ShakaPerf release evidence reuse (#4833)
• Additional commits viewable 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)

[github-actions]

🚀 Quick Review App Commands

Welcome! Here are the commands you can use in this PR:
They require the repository to have cpflow review apps configured, including the CPLN_TOKEN_STAGING secret.

+review-app-deploy

Deploy your PR branch for testing.

+review-app-delete

Remove the review app when done.

+review-app-help

Show detailed instructions, environment setup, and configuration options.

Comment +review-app-help for full setup details.