*It appears that the plasmic “Push to GitHub” publish option uses outdated GitHub actions and a version of Node. GitHub states the following warnings after the workflow runs: *
-
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/setup-node@v3, plasmicapp/plasmic-action@master. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
-
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
*To reproduce this, I made a simple change to my Plasmic project in Plasmic Studio, clicked Publish > Push to GitHub > Publish
Then I went over to my GitHub repo, clicked Actions and selected the running workflow titled “plasmic”. After the workflow had completed, the warnings are visible below the output dialog.
Inspecting the autogenerated workflow file under /.github/workflows/plasmic.yml, the following action versions are not updated in the workflow file:*
Old Version Latest Version
actions/checkout@v2 → actions/cache@v6
actions/setup-node@v3 → actions/setup-node@v6
actions/cache@v4 → actions/cache@v5
It also appears that this workflow is using Node version 18, which has since been deprecated.
While I have used the webhook publishing mode with a custom GitHub action workflow with Plasmic in the past, I am building my website for my client who intends to publish their own changes to the site in the future using your intuitive (and frankly awesome) Plasmic studio interface. The webhook syntax is not something that they would be interested in learning, nor how to maintain their own GitHub actions workflow YAML file to include up-to-date actions.
In an ideal world, this pre-defined action workflow would be maintained by Plasmic to keep the UX intuitive for pushing these changes. I completely understand if this is not in the scope of maintenance for Plasmic, but I was wondering if there was a plan to continue to update this workflow file to use the current Node and Actions versions going forward, especially considering all of the Node and GitHub actions security vulnerabilities that have been revealed recently.
Thank you for your time, and I appreciate any insights that the plasmic team (or anyone else may have)
Workflow File: revma-hub/.github/workflows/plasmic.yml at main · AMKE-REVMA/revma-hub · GitHub