We’ve been busy this month with improvements to our GitHub integration, static buildpack, expanded authentication options, and UI refreshes. Here’s what we shipped in July, 2025.
Our setup-runway GitHub action now supports private/public key setup directly from secrets. Please use them and let us take care of the setup!
We renamed the old private-key/public-key inputs to private-key-location/public-key-location when you set up keys yourself. There’s also a new application parameter that creates and attaches your Runway application to the repo automatically.
These changes make working with the action shorter easier (less yaml!) and more reliable.
With additions, building preview applications has become even easier! Check out one of our own repositories with the full integration:
APP_NAME)APP_NAME)We deliberately decided to double down on our Github Action rather than implementing a flow where you offer up access to your GitHub organization and repositories. We can’t disclose or leak your code if we don’t have it! And we don’t need to reinvent workflows when you get the full power of GitHub Actions and can build the workflow to your liking.
Runway supports static sites with Hugo or mdBook, first-class! Last month, we expanded our support to include the Node.js/npm toolchain for both.
One of our users came to us with an idea: they use a CSS framework and a little JavaScript on their static website. So instead of checking in the build artifacts locally, Runway now builds the assets for them!
Quick example to enable it:
# project.toml
[build]
[[build.env]]
name="BP_NODE_RUN_SCRIPTS"
value="build-tw,build-js"
[[build.env]]
name="BP_KEEP_FILES"
value="themes/site/assets/css/main.css:themes/site/assets/js/main.js"
(And runway app deploy!)
The second large update to our static toolchain is that we now support Hugo Modules, which are like Go modules.
Hugo uses Modules manage dependencies on themes and other components. Now gone are the days of git submodules! Runway supports Hugo Modules out of the box with zero configuration.
Building on last month’s work, we rolled out OIDC support in the CLI. You can now log in with:
runway login -t oidc
If you already know which provider you want to use (we support GitHub and GitLab):
runway login -t oidc --provider github
We updated the design again. The table showing your collaborators has a fresh new look:
… and the configuration table got a nice facelift too:
More updates are coming soon, including avatars (gravatars).
We made lots of internal changes and updates as usual. We’re reworking our release process to ship updates to the stack and build packs more frequently.
We’ve made some progress on our API docs. Last but not least we’re also (still) working hard on our first integration, which should be ready soon after this post goes out.