Erlang/OTP 29

Last reviewed Oct 26, 2026

Export as PDF

Prompt Details

Prompt Composition

1prompt
  1. Erlang/OTP 29187 lines · 8.9K tokens

CWE Coverage

  • 20
  • 22
  • 59
  • 78
  • 89
  • 95
  • 116
  • 117
  • 190
  • 208
  • 209
  • 214
  • 250
  • 287
  • 295
  • 296
  • 297
  • 298
  • 299
  • 306
  • 307
  • 319
  • 323
  • 327
  • 338
  • 347
  • 352
  • 362
  • 367
  • 379
  • 407
  • 427
  • 444
  • 470
  • 494
  • 502
  • 532
  • 611
  • 613
  • 639
  • 664
  • 674
  • 732
  • 770
  • 772
  • 789
  • 799
  • 807
  • 834
  • 862
  • 863
  • 916
  • 918
  • 922
  • 942
  • 943
  • 1395

Prompt Preview

Apply these rules to Erlang/OTP 29 applications, releases, distributed nodes, ports, native interfaces, and operational tooling.

Release and dependency integrity

  • Build release images from the newest patch of the latest minor of an OTP major that still receives security fixes; OTP maintains only the latest minor of each supported major. Rebuild and redeploy when security fixes ship. This prompt covers the OTP 29 line.
  • Prefer a line-following base image such as erlang:29 rebuilt with docker build --pull, or a bot-updated digest. Take any exact OTP version a Dockerfile, .tool-versions, mise.toml, or CI matrix needs from the erlang/otp releases page, or leave a build-failing placeholder such as an ARG OTP_VERSION with no default; a remembered version is likely older than the releases these rules name as carrying fixes.
  • In CI, verify the runtime in both the build and deployed release against the current erlang/otp releases page; rebar.lock and mix.lock audits never see it. Fail CI if provenance is unresolved or the verified runtime falls behind the supported release policy above.
  • On an installed development system, read filename:join([code:root_dir(), "releases", erlang:system_info(otp_release), "OTP_VERSION"]); erlang:system_info(otp_release) gives only the major. Treat that file as a clue, not proof: target systems normally omit it, a ** suffix identifies a mixed patched system, and custom patching can leave it stale. Verify the actual ERTS and relevant application versions, including ssl, public_key, ssh, inets, stdlib, and asn1,