abe65dc410
Every CI run currently emits "Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24" runner annotations (visible on every job of the main build and the Windows build). These come from the runner at execution time, so the actionlint gate added in #8912 can't catch them: actionlint checks workflow files statically and has no knowledge of which Node runtime an action's implementation targets. This bumps every runner-flagged action to its latest major, all of which target node24: | Action | From | To | |---|---|---| | actions/checkout | v4 | v7 | | actions/setup-node | v4 | v7 | | actions/upload-artifact | v4 | v7 | | actions/download-artifact | v4 | v8 | | actions/setup-python | v5 | v7 | | actions/labeler | v5 | v6 | | actions/github-script | v7 | v9 | | github/codeql-action | v3 | v4 | | peter-evans/create-pull-request | v6 | v8 | | cypress-io/github-action | v6 | v7 | | browser-actions/setup-chrome | v1 | v2 | | codecov/codecov-action | v5 | v7 | | astral-sh/setup-uv | v6 | v8.3.2 (exact pin; from v8 they publish immutable releases only, no floating major tags) | The last three rows came from iterating: this branch's own push builds run the full workflow (including the real deploy path), and scanning their annotations after each round caught what the first sweep missed — our github-script uses, codecov-action (whose v5 pins a node20 github-script by SHA internally; their v6 fixed that), and setup-uv. codeql-action v3 additionally carries its own deprecation warning (sunset December 2026). **Behaviour changes checked against our usage:** - create-pull-request v7 renamed `git-token` to `branch-token` and removed the `PULL_REQUEST_NUMBER` env output: browserslist.yml uses neither. - setup-python v7 removed the `pip-install` input: check-infra-settings.yml doesn't use it. - github-script v9: `require('@actions/github')` no longer works inside scripts; neither of ours does that (one calls `github.rest.git.createRef`, the other requires only the core `fs` module). - setup-uv v7/v8 removed the `server-url` input and changed the manifest-file format: we pass no inputs. - setup-chrome v2 installs Chrome for Testing by default: fine (arguably better) for the Cypress frontend tests. - download-artifact v8 now errors on hash mismatch by default: a fix we want. - checkout v7 blocks fork-PR checkout under `pull_request_target`/`workflow_run` unless opted in: our only such workflows (label.yml, check-infra-settings-comment.yml) don't use checkout at all. - codecov-action v6 is their node24 bump; v7 only rotates their signing account. Our `token`/`verbose` usage is unaffected. **Deliberately left alone:** - `browser-actions/setup-firefox@v1`: latest release is still v1 (1.7.x, node24). - `wow-actions/potential-duplicates@v1`: upstream is unmaintained (last release 2022); no node24 version exists. Its warning will remain on duplicate-detection runs until we replace or drop it. - `jakejarvis/s3-sync-action@master`: a Docker action, unaffected by the Node runtime deprecation. **Validation:** - actionlint 1.7.12 (the pinned CI version) passes clean. - All PR checks green across two full rounds, including Cypress on Chrome for Testing and CodeQL v4. - Because pushes to any branch run the real deploy job, the complete chain (dist build → download-artifact v8 → sentry → S3 sync → github-script v9 tagging → post_deploy_check on admin-node) ran green for real. - Runner compatibility: these majors require Actions Runner >= 2.327.1; the self-hosted admin-node and ce fleet runners are all on 2.335.1 (confirmed from job logs). 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: mattgodbolt-molty <mattgodbolt-molty@users.noreply.github.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Compiler Explorer
Compiler Explorer is an interactive compiler exploration website. Edit code in C, C++, C#, F#, Rust, Go, D, Haskell, Swift, Pascal, ispc, Python, Java, or any of the other 30+ supported languages, and see how that code looks after being compiled in real time.
Bug Report · Compiler Request · Feature Request · Language Request · Library Request · Report Vulnerability
Overview
Multiple compilers are supported for each language, many different tools and visualizations are available, and the UI layout is configurable (thanks to GoldenLayout).
Try out at godbolt.org, or run your own local instance. An overview of what the site lets you achieve, why it's useful, and how to use it is available here, or in this talk.
Compiler Explorer follows a Code of Conduct which aims to foster an open and welcoming environment.
Compiler Explorer was started in 2012 to show how C++ constructs are translated to assembly code. It started as a
tmux session with vi running in one pane and watch gcc -S foo.cc -o - running in the other.
Since then, it has become a public website serving over 3,000,000 compilations per week.
You can financially support this project on Patreon, GitHub, Paypal, or by buying cool gear on the Compiler Explorer store.
Using Compiler Explorer
FAQ
There is now a FAQ section in the repository wiki. If your question is not present, please contact us as described below, so we can help you. If you find that the FAQ is lacking some important point, please feel free to contribute to it and/or ask us to clarify it.
Videos
Several videos showcase some features of Compiler Explorer:
- Compiler Explorer 2023: What's New?: Presentation for CppNorth 2023.
- Presentation for CppCon 2019 about the project
- Older 2 part series of videos which go into a bit more detail into the more obscure features.
- Just Enough Assembly for Compiler Explorer: Practical introduction to Assembly with a focus on the usage of Compiler Explorer, from CppCon 2021.
- Playlist: Compiler Explorer: A collection of videos discussing Compiler Explorer; using it, installing it, what it's for, etc.
A Road map is available which gives a little insight into the future plans for Compiler Explorer.
Developing
Compiler Explorer is written in TypeScript, on Node.js.
Assuming you have a compatible version of node installed, on Linux simply running make ought to get you up and
running with an Explorer running on port 10240 on your local machine:
http://localhost:10240/. If this doesn't work for you, please contact us, as we consider it
important you can quickly and easily get running. Compiler Explorer requires at least the
node version pinned in .node-version (anything newer is fine). We look for it on your PATH, which covers a
system install as well as any version manager with shell integration (fnm, asdf, nodenv, volta, or an
active nvm). If your PATH node is missing or too old we also try to resolve the version pinned in
.node-version via nvm/fnm/nodenv/asdf directly. To force a specific install, point NODE_DIR at it (an
environment variable or make parameter); we then use $NODE_DIR/bin/node.
Running with make EXTRA_ARGS='--language LANG' will allow you to load LANG exclusively, where LANG is one for the
language ids/aliases defined in lib/languages.ts. For example, to only run Compiler Explorer with C++ support,
you'd run make EXTRA_ARGS='--language c++'. You can supply multiple --language arguments to restrict to more than
one language. The Makefile will automatically install all the third-party libraries needed to run; using npm to
install server-side and client-side components.
For development, we suggest using make dev to enable some useful features, such as automatic reloading on file changes
and shorter startup times.
You can also use npm run dev to run if make dev doesn't work on your machine.
When making UI changes, we recommend following the UI Testing Checklist to ensure all components work correctly.
Some languages need extra tools to demangle them, e.g. rust, d, or haskell. Such tools are kept separately in the
tools repo.
Configuring compiler explorer is achieved via configuration files in the etc/config directory. Values are key=value.
Options in a {type}.local.properties file (where {type} is c++ or similar) override anything in the
{type}.defaults.properties file. There is a .gitignore file to ignore *.local.* files, so these won't be checked
into git, and you won't find yourself fighting with updated versions when you git pull. For more information see
Adding a Compiler.
Check CONTRIBUTING.md for detailed information about how you can contribute to Compiler Explorer, and the docs folder for specific details regarding various things you might want to do, such as how to add new compilers or languages to the site.
Running a local instance
If you want to point it at your own GCC or similar binaries, either edit the etc/config/LANG.defaults.properties or
else make a new one with the name LANG.local.properties, substituting LANG as needed. *.local.properties files
have the highest priority when loading properties.
For a quick and easy way to add local compilers, use the CE Properties Wizard which automatically detects and configures compilers for 30+ languages. See Adding a Compiler for more details.
If you want to support multiple compilers and languages like godbolt.org, you can use the
bin/ce_install install compilers command in the infra project to install
all or some of the compilers. Compilers installed in this way can be loaded through the configuration in
etc/config/*.amazon.properties. If you need to deploy in a completely offline environment, you may need to remove some
parts of the configuration that are pulled from www.godbolt.ms@443.
When running in a corporate setting the URL shortening service can be replaced by an internal one if the default storage
driver isn't appropriate for your environment. To do this, add a new module in lib/shortener/myservice.js and set the
urlShortenService variable in configuration. This module should export a single function, see the
tinyurl module for an example.
RESTful API
There's a simple restful API that can be used to do compiles to asm and to list compilers.
You can find the API documentation here.
Contact us
We run a Compiler Explorer Discord, which is a place to discuss using or developing
Compiler Explorer. We also have a presence on the cpplang Slack channel
#compiler_explorer and we have
a public mailing list.
There's a development channel on the discord, and also a development mailing list.
Feel free to raise an issue on github or email Matt directly for more help.
Official domains
Following are the official domains for Compiler Explorer:
The domains allow arbitrary subdomains, e.g., https://foo.godbolt.org/, which is convenient since each subdomain has an independent local state. Also, language subdomains such as https://rust.compiler-explorer.com/ will load with that language already selected.
Credits
Compiler Explorer is maintained by the awesome people listed in the AUTHORS file.
We would like to thank the contributors listed in the CONTRIBUTORS file, who have helped shape Compiler Explorer.
We would also like to especially thank these people for their contributions to Compiler Explorer:
- Gabriel Devillers (while working for Kalray)
- Johan Engelen
- Joshua Sheard
- Andrew Pardoe
Many amazing sponsors, both individuals and companies, have helped fund and promote Compiler Explorer.