# builds

Builds are software compilation or testing processes that update resources or create artifacts from source code.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Keeping your databases up to date: From upstream release to you

DevFeed: [Keeping your databases up to date: From upstream release to you](<https://devfeed.tech/articles/keeping-your-databases-up-to-date-from-upstream-release-to-you-144299.md>)

Original publisher: [Read original article](<https://blog.ovhcloud.com/en/posts/managed-database-image-updates/>)

Author: Elena Luoto

Published: 2026-11-19T06:00:00Z

Content type: article

Language: en

Sources: [OVHcloud Blog](<https://devfeed.tech/sources/ovhcloud-blog.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous Delivery (CD)](<https://devfeed.tech/topics/continuous-delivery.md>), [release engineering](<https://devfeed.tech/topics/release-engineering.md>), [staging](<https://devfeed.tech/topics/staging.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [builds](<https://devfeed.tech/topics/builds.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [version](<https://devfeed.tech/topics/version.md>)

Tags: [ansible](<https://devfeed.tech/tags/ansible.md>), [api](<https://devfeed.tech/tags/api.md>), [apt](<https://devfeed.tech/tags/apt.md>), [automated](<https://devfeed.tech/tags/automated.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [automation](<https://devfeed.tech/tags/automation.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [builds](<https://devfeed.tech/tags/builds.md>), [databases](<https://devfeed.tech/tags/databases.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [image](<https://devfeed.tech/tags/image.md>), [pre-production](<https://devfeed.tech/tags/pre-production.md>), [production](<https://devfeed.tech/tags/production.md>), [release](<https://devfeed.tech/tags/release.md>), [sign-off](<https://devfeed.tech/tags/sign-off.md>), [tests](<https://devfeed.tech/tags/tests.md>), [upstream](<https://devfeed.tech/tags/upstream.md>), [upstream-release](<https://devfeed.tech/tags/upstream-release.md>), [version](<https://devfeed.tech/tags/version.md>), [weekly](<https://devfeed.tech/tags/weekly.md>)

### AI overview

Emile checks 15 engine/version pairs weekly and skips rebuilding when the current production tag matches the newest upstream package; for Valkey, it checks GitHub, and accepts a version only once release notes appear. When a rebuild is needed, it starts from clean Debian using shared Packer and Ansible recipes. New images go to a snapshot registry and must pass pre-production checks, including upgrades from current and earlier major versions. A team member manually approves promotion from the master branch; afterward, 5% of the production fleet moves to the image daily in randomized customer order. Builds also fail when vendor defaults have changed, prompting human review. If no version is new, a manual rebuild remains available for base-image fixes and follows the same tests and approval gate.

### Source excerpt

Learn how we keep databases up to date: a weekly version check, clean image builds, pre-production tests, and a human sign-off before release.

## Jenkins CI Bottlenecks: How Harness Helps Teams Scale CI

DevFeed: [Jenkins CI Bottlenecks: How Harness Helps Teams Scale CI](<https://devfeed.tech/articles/jenkins-ci-bottlenecks-how-harness-helps-teams-scale-ci-139651.md>)

Original publisher: [Read original article](<https://www.harness.io/blog/is-your-jenkins-pipeline-ready-for-what-cursor-just-handed-you>)

Author: Lavakush Biyani

Published: 2026-11-18T00:00:00Z

Content type: article

Language: en

Sources: [Harness](<https://devfeed.tech/sources/harness-blog.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Jenkins](<https://devfeed.tech/topics/jenkins.md>), [builds](<https://devfeed.tech/topics/builds.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [AI tools for developers](<https://devfeed.tech/topics/ai-tools-for-developers.md>), [coding assistant](<https://devfeed.tech/topics/coding-assistant.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [accelerate](<https://devfeed.tech/tags/accelerate.md>), [access-controls](<https://devfeed.tech/tags/access-controls.md>), [ai](<https://devfeed.tech/tags/ai.md>), [builds](<https://devfeed.tech/tags/builds.md>), [caching](<https://devfeed.tech/tags/caching.md>), [cd](<https://devfeed.tech/tags/cd.md>), [ci](<https://devfeed.tech/tags/ci.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [faster](<https://devfeed.tech/tags/faster.md>), [harness](<https://devfeed.tech/tags/harness.md>), [helps](<https://devfeed.tech/tags/helps.md>), [jenkins](<https://devfeed.tech/tags/jenkins.md>), [learn](<https://devfeed.tech/tags/learn.md>), [scale](<https://devfeed.tech/tags/scale.md>), [teams](<https://devfeed.tech/tags/teams.md>), [testing](<https://devfeed.tech/tags/testing.md>), [with](<https://devfeed.tech/tags/with.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

Harness Software Delivery Agent aims to ease Jenkins CI bottlenecks as pull request volumes grow by offering managed Harness Cloud builders, with self-managed and Kubernetes execution options for specific infrastructure or compliance needs. It provides Cache Intelligence, Build Intelligence, and Docker Layer Caching to reduce repeated downloads, compilation, and image builds; Test Intelligence selects tests associated with code changes, while parallel execution and matrix strategies distribute workloads. Reusable templates, centralized secrets and connectors, access controls, and governance policies address pipeline consistency. With configured permissions, Harness MCP lets supported assistants including Cursor, Windsurf, and Claude Code create, trigger, inspect, and troubleshoot pipelines. The excerpt reports Qrvey cut average builds from 90 minutes to several hours down to about 12 minutes using over 30 parallel threads, after a migration of about three months. Jenkins remains capable, but scaling it can require more infrastructure and ongoing controller, agent, plugin, and pipeline administration. Migration involves mapping existing configurations and dependencies; Harness AI or

### Source excerpt

Learn how Harness helps teams overcome Jenkins CI bottlenecks with faster builds, intelligent caching, optimized testing, and AI-powered CI/CD workflows. | Blog

## Standard builds move to usage-based billing for new teams

DevFeed: [Standard builds move to usage-based billing for new teams](<https://devfeed.tech/articles/standard-builds-move-to-usage-based-billing-for-new-teams-138554.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/standard-build-billing-new-teams>)

Author: Pranav Kanchi

Published: 2026-11-17T20:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [builds](<https://devfeed.tech/topics/builds.md>)

Tags: [billing](<https://devfeed.tech/tags/billing.md>), [builds](<https://devfeed.tech/tags/builds.md>), [cost](<https://devfeed.tech/tags/cost.md>), [elastic](<https://devfeed.tech/tags/elastic.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [machine](<https://devfeed.tech/tags/machine.md>), [machines](<https://devfeed.tech/tags/machines.md>), [model](<https://devfeed.tech/tags/model.md>), [monthly](<https://devfeed.tech/tags/monthly.md>), [pro](<https://devfeed.tech/tags/pro.md>), [project](<https://devfeed.tech/tags/project.md>), [settings](<https://devfeed.tech/tags/settings.md>), [standard](<https://devfeed.tech/tags/standard.md>), [switching](<https://devfeed.tech/tags/switching.md>), [team](<https://devfeed.tech/tags/team.md>), [teams](<https://devfeed.tech/tags/teams.md>), [usage-based-billing](<https://devfeed.tech/tags/usage-based-billing.md>)

### AI overview

New Pro and Enterprise teams no longer receive an included Standard build slot; Standard builds use the same usage-based billing model as other build machines. Pro Standard builds cost $0.014 per build minute, with monthly usage credit applying to build usage. Enterprise rates follow each team's contract. For teams covered by the change, Standard builds remain billable after switching from Elastic. Build machines can be selected in team or project settings.

### Source excerpt

Starting today, new Pro and Enterprise teams no longer include a Standard build slot. This brings Standard builds under the same usage-based billing model as other build machines. On Pro, Standard builds cost $0.014 per build minute, and your monthly usage credit applies to build usage. Enterprise rates follow your contract. Standard builds remain billable after switching from Elastic to Standard for teams covered by this change. Select a build machine in team settings or project settings, or read more about managing your builds. Read more

## The Unity CLI 1.0 is here!

DevFeed: [The Unity CLI 1.0 is here!](<https://devfeed.tech/articles/the-unity-cli-1-0-is-here-138167.md>)

Original publisher: [Read original article](<https://unity.com/the-unity-cli-1.0-is-here>)

Author: Christopher Addison

Published: 2026-11-17T00:00:00Z

Content type: release

Language: en

Sources: [Unity](<https://devfeed.tech/sources/unity.md>)

Topics: [Unity](<https://devfeed.tech/topics/unity.md>), [Terminal](<https://devfeed.tech/topics/terminal.md>), [builds](<https://devfeed.tech/topics/builds.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [codex](<https://devfeed.tech/topics/codex.md>), [google-antigravity](<https://devfeed.tech/topics/google-antigravity.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [versioning](<https://devfeed.tech/topics/versioning.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Visual Studio Code](<https://devfeed.tech/topics/visual-studio-code.md>)

Tags: [17](<https://devfeed.tech/tags/17.md>), [2026](<https://devfeed.tech/tags/2026.md>), [about](<https://devfeed.tech/tags/about.md>), [agent](<https://devfeed.tech/tags/agent.md>), [antigravity](<https://devfeed.tech/tags/antigravity.md>), [automate](<https://devfeed.tech/tags/automate.md>), [beta](<https://devfeed.tech/tags/beta.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [cli](<https://devfeed.tech/tags/cli.md>), [code](<https://devfeed.tech/tags/code.md>), [codex](<https://devfeed.tech/tags/codex.md>), [grok](<https://devfeed.tech/tags/grok.md>), [grok-build](<https://devfeed.tech/tags/grok-build.md>), [here](<https://devfeed.tech/tags/here.md>), [project](<https://devfeed.tech/tags/project.md>), [terminal](<https://devfeed.tech/tags/terminal.md>), [unity](<https://devfeed.tech/tags/unity.md>)

### AI overview

Unity CLI 1.0 is out of beta and provides terminal-based project setup and control of a live Unity Editor for agents, scripts, tests, and CI. `unity setup` installs official plugins for Claude Code, Codex, Grok Build, or Google Antigravity; Unity skills can also be installed for other agents. The release adds dialog handling, Editor-based builds, version control summaries, project audits, consistent JSON output and exit codes, CI-safe noninteractive behavior, and per-project CLI version ranges. It runs on macOS, Linux, and Windows, and `unity self-update` retains three versions for rollback. Unity says commands, flags, and output will remain compatible through 1.x, with warnings and time to update before removals. Build Server licensing now covers agents and automation; a supported Linux containerized Editor is described as coming soon.

### Source excerpt

Unity CLI 1.0 is out of beta. Connect Claude Code, Codex, Grok Build or Antigravity to your Unity project, and automate builds and tests from the terminal.

## Run AI Agents in TeamCity

DevFeed: [Run AI Agents in TeamCity](<https://devfeed.tech/articles/run-ai-agents-in-teamcity-135367.md>)

Original publisher: [Read original article](<https://blog.jetbrains.com/teamcity/2026/11/run-ai-agents-in-teamcity/>)

Author: Olga Bedrina

Published: 2026-11-16T09:28:51Z

Content type: tutorial

Language: en

Sources: [JetBrains](<https://devfeed.tech/sources/the-jetbrains-blog.md>), [TeamCity](<https://devfeed.tech/sources/teamcity-powerful-ci-cd-for-devops-centric-teams-the-jetbrains-blog.md>)

Topics: [teamcity](<https://devfeed.tech/topics/teamcity.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [codex](<https://devfeed.tech/topics/codex.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [builds](<https://devfeed.tech/topics/builds.md>), [least privilege](<https://devfeed.tech/topics/least-privilege.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [ci-cd-workflows](<https://devfeed.tech/tags/ci-cd-workflows.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [codex](<https://devfeed.tech/tags/codex.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [repository](<https://devfeed.tech/tags/repository.md>), [review](<https://devfeed.tech/tags/review.md>), [tasks](<https://devfeed.tech/tags/tasks.md>), [teamcity](<https://devfeed.tech/tags/teamcity.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

TeamCity's experimental AI Agents plugin lets builds run Codex or Claude Code, installing the selected client when needed and providing provider credentials only for the build's duration. Configure a supported connection--JetBrains Air, OpenAI, Anthropic, LiteLLM, or OpenRouter--add the AI Agent build feature, then invoke `codex` or `claude` in a Command Line step. The plugin publishes token usage statistics and agent trajectories as hidden build artifacts, with HTML for review and JSON for programmatic analysis. These records can help inspect individual runs or compare runs to refine prompts. Artifacts may contain prompts, source code, and model output, so access should be restricted. The plugin is experimental and may change.

### Source excerpt

AI coding agents don't have to run only on a developer's machine. You can also make them part of your CI/CD workflows to review code, investigate failed builds, update documentation, or handle other repository tasks. The new experimental AI Agents plugin for TeamCity lets you run Codex and Claude Code directly in TeamCity builds and [...]

## How Mitts Makes Parallel Rust Builds Faster Than Cargo

DevFeed: [How Mitts Makes Parallel Rust Builds Faster Than Cargo](<https://devfeed.tech/articles/how-mitts-makes-parallel-rust-builds-faster-than-cargo-135516.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-mitts-makes-parallel-rust-builds-faster-than-cargo?source=rss>)

Author: Alexander Panasenko

Published: 2026-11-16T05:00:02Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Cache](<https://devfeed.tech/topics/cache.md>), [Rust](<https://devfeed.tech/topics/rust.md>), [builds](<https://devfeed.tech/topics/builds.md>), [developer-productivity](<https://devfeed.tech/topics/developer-productivity.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [build-systems](<https://devfeed.tech/tags/build-systems.md>), [builds](<https://devfeed.tech/tags/builds.md>), [cache](<https://devfeed.tech/tags/cache.md>), [cargo](<https://devfeed.tech/tags/cargo.md>), [cargo-alternatives](<https://devfeed.tech/tags/cargo-alternatives.md>), [compilation](<https://devfeed.tech/tags/compilation.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [content-addressed-caching](<https://devfeed.tech/tags/content-addressed-caching.md>), [distributed-build-caching](<https://devfeed.tech/tags/distributed-build-caching.md>), [parallel](<https://devfeed.tech/tags/parallel.md>), [reuse](<https://devfeed.tech/tags/reuse.md>), [rust](<https://devfeed.tech/tags/rust.md>), [rust-build-isolation](<https://devfeed.tech/tags/rust-build-isolation.md>), [rust-worktrees](<https://devfeed.tech/tags/rust-worktrees.md>), [rustls](<https://devfeed.tech/tags/rustls.md>), [worktrees](<https://devfeed.tech/tags/worktrees.md>), [x86-64](<https://devfeed.tech/tags/x86-64.md>)

### AI overview

In a study of twelve `rustls` worktrees on Linux x86_64, Mitts completed the batch in 9.3 seconds, compared with 3 min 42 s for plain Cargo and 3 min 59 s for warm sccache; shared-cache priming was excluded. Mitts reuses eligible completed compilation results across separate worktrees using action keys based on tracked inputs, while keeping each workspace's outputs separate. The reported gains vary by workload: Cargo often wins a single cold build and can be faster for edits within a large crate, where incremental compilation helps. A shared `CARGO_TARGET_DIR` failed a correctness check involving a deliberately failing test. Mitts is pre-release, supports Linux and macOS, and does not yet support Windows, cross-compilation beyond the host target, or remote/team caches. The excerpt reports three-repeat medians and cautions that build-script staging is not an OS sandbox.

### Source excerpt

12 rustls worktrees on Linux x86_64: Cargo 3 min 42 s, Mitts 9.3 s. How shared caches reuse build work, and where Cargo still wins.

## Migrate BuildConfigs to builds for Red Hat OpenShift with one plug-in install

DevFeed: [Migrate BuildConfigs to builds for Red Hat OpenShift with one plug-in install](<https://devfeed.tech/articles/migrate-buildconfigs-to-builds-for-red-hat-openshift-with-one-plug-in-install-133233.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/13/migrate-buildconfigs-builds-openshift-crane-plugin>)

Author: Prateek Singh Rathore

Published: 2026-11-13T13:02:10Z

Content type: tutorial

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [builds](<https://devfeed.tech/topics/builds.md>), [redhat](<https://devfeed.tech/topics/redhat.md>), [Buildah](<https://devfeed.tech/topics/buildah.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [buildah](<https://devfeed.tech/tags/buildah.md>), [builds](<https://devfeed.tech/tags/builds.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [docker](<https://devfeed.tech/tags/docker.md>), [dockerfile](<https://devfeed.tech/tags/dockerfile.md>), [install](<https://devfeed.tech/tags/install.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-native](<https://devfeed.tech/tags/kubernetes-native.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>)

### AI overview

The Crane BuildConfigToBuildsPlugin v0.11.0 converts supported OpenShift BuildConfigs into Shipwright Builds as part of Crane's export, transform and apply workflow. It handles Git, image and binary sources and carries over several settings, including build arguments, environment variables, volumes, builder image and resource limits. The excerpt's Docker example maps the Docker strategy to Buildah and redirects an ImageStream output to a registry. Conversion warnings identify manual follow-up: triggers are dropped, serial build ordering is lost, and redirected images no longer update the source ImageStream. The plugin works on local files and does not contact clusters; operators apply the reviewed output separately. Custom and JenkinsPipeline strategies are skipped, and the source notes other limitations. It requires Crane v0.11.0 or newer and the Builds for Red Hat OpenShift operator on the target.

### Source excerpt

Red Hat OpenShift has built container images with BuildConfigs for years. Builds for Red Hat OpenShift is the Kubernetes-native way to do the same work. Based on Shipwright, it runs builds without root privileges, and supports Buildah and source-to-image (S2I) strategies. Moving many BuildConfigs by hand is slow and easy to get wrong. The post Migrate BuildConfigs to builds for Red Hat OpenShift with one plug-in install appeared first on Red Hat Developer.

## From HTTP to SSH: Finding a Host-Level Attack Path in OpenPLC v3

DevFeed: [From HTTP to SSH: Finding a Host-Level Attack Path in OpenPLC v3](<https://devfeed.tech/articles/from-http-to-ssh-finding-a-host-level-attack-path-in-openplc-v3-128446.md>)

Original publisher: [Read original article](<https://hackernoon.com/from-http-to-ssh-finding-a-host-level-attack-path-in-openplc-v3?source=rss>)

Author: RUGERO Tesla

Published: 2026-11-11T07:42:27Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [ssh](<https://devfeed.tech/topics/ssh.md>), [Security](<https://devfeed.tech/topics/security.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [builds](<https://devfeed.tech/topics/builds.md>), [HTTP](<https://devfeed.tech/topics/http.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [22](<https://devfeed.tech/tags/22.md>), [3](<https://devfeed.tech/tags/3.md>), [7-4](<https://devfeed.tech/tags/7-4.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [account](<https://devfeed.tech/tags/account.md>), [acquisition](<https://devfeed.tech/tags/acquisition.md>), [actuator](<https://devfeed.tech/tags/actuator.md>), [attack](<https://devfeed.tech/tags/attack.md>), [can](<https://devfeed.tech/tags/can.md>), [compilation](<https://devfeed.tech/tags/compilation.md>), [control](<https://devfeed.tech/tags/control.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [execution](<https://devfeed.tech/tags/execution.md>), [experiment](<https://devfeed.tech/tags/experiment.md>), [http](<https://devfeed.tech/tags/http.md>), [ics-ot-security](<https://devfeed.tech/tags/ics-ot-security.md>), [ics-security](<https://devfeed.tech/tags/ics-security.md>), [industrial-control-systems](<https://devfeed.tech/tags/industrial-control-systems.md>), [industrial-cyber-security](<https://devfeed.tech/tags/industrial-cyber-security.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [logic](<https://devfeed.tech/tags/logic.md>), [plc](<https://devfeed.tech/tags/plc.md>), [plc-security](<https://devfeed.tech/tags/plc-security.md>), [replacement](<https://devfeed.tech/tags/replacement.md>), [security](<https://devfeed.tech/tags/security.md>), [ssh](<https://devfeed.tech/tags/ssh.md>), [v3](<https://devfeed.tech/tags/v3.md>)

### AI overview

In an isolated OpenPLC v3 lab, an attacker with valid SSH credentials and sufficient host privileges replaced the active Structured Text project, compiled it, stopped the running process, and started the new runtime. A payload toggling `%MW0` produced alternating zero and one values at holding register 1024 over Modbus TCP, supporting that the replacement logic was executing. This required a runtime restart; it did not demonstrate credential theft, authentication bypass, live updates, or a physical process response. The attempted HTTP automation was unreliable due to session interruptions, whose cause was not established. The demonstrated path depended on host access and privileges, not a management dashboard flaw.

### Source excerpt

An OpenPLC v3 security experiment demonstrating how SSH access can enable unauthorized control logic replacement, compilation, and execution.

## C++ language server now auto-configures MSBuild builds

DevFeed: [C++ language server now auto-configures MSBuild builds](<https://devfeed.tech/articles/c-language-server-now-auto-configures-msbuild-builds-127308.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-11-10-c-language-server-now-auto-configures-msbuild-builds>)

Author: Allison

Published: 2026-11-10T17:04:10Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [GitHub Copilot CLI](<https://devfeed.tech/topics/github-copilot-cli.md>), [MSVC](<https://devfeed.tech/topics/msvc.md>), [builds](<https://devfeed.tech/topics/builds.md>)

Tags: [automatically](<https://devfeed.tech/tags/automatically.md>), [c-plus-plus](<https://devfeed.tech/tags/c-plus-plus.md>), [cmake](<https://devfeed.tech/tags/cmake.md>), [code-intelligence](<https://devfeed.tech/tags/code-intelligence.md>), [compilation](<https://devfeed.tech/tags/compilation.md>), [compile](<https://devfeed.tech/tags/compile.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [custom](<https://devfeed.tech/tags/custom.md>), [database](<https://devfeed.tech/tags/database.md>), [definition](<https://devfeed.tech/tags/definition.md>), [generate](<https://devfeed.tech/tags/generate.md>), [generation](<https://devfeed.tech/tags/generation.md>), [github](<https://devfeed.tech/tags/github.md>), [github-copilot-cli](<https://devfeed.tech/tags/github-copilot-cli.md>), [improvement](<https://devfeed.tech/tags/improvement.md>), [install](<https://devfeed.tech/tags/install.md>), [msbuild](<https://devfeed.tech/tags/msbuild.md>), [project](<https://devfeed.tech/tags/project.md>), [quick-start](<https://devfeed.tech/tags/quick-start.md>), [server](<https://devfeed.tech/tags/server.md>), [subscription](<https://devfeed.tech/tags/subscription.md>)

### AI overview

For MSBuild-based C++ projects, the Microsoft C++ Language Server for GitHub Copilot CLI now bundles and automatically runs its compile commands extractor when the language server starts, generating the compilation database used for code intelligence without a separate setup skill. Previously, users had to provide `compile_commands.json` or have Copilot find and run a configuration skill. The excerpt says generation is deterministic and reduces setup token use. Other build systems still require a supplied compilation database or a skill: CMake has a generate compile commands skill, while custom systems can use a custom build extractor skill. Installation requires accepting the EULA, and an active GitHub Copilot subscription is required.

### Source excerpt

The Microsoft C++ Language Server for GitHub Copilot CLI now bundles its MSBuild compile commands extractor and invokes it automatically. An agent no longer needs to discover and run a... The post C++ language server now auto-configures MSBuild builds appeared first on The GitHub Blog.

## Keeping Fuzzers on Duty: Repairing Fuzzing Build Breakages in Continuous Open-Source Fuzzing

DevFeed: [Keeping Fuzzers on Duty: Repairing Fuzzing Build Breakages in Continuous Open-Source Fuzzing](<https://devfeed.tech/articles/keeping-fuzzers-on-duty-repairing-fuzzing-build-breakages-in-continuous-open-source-fuzzing-118075.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.06358>)

Author: Zhuang Zhao, Jiongchi Yu, Yao Zhang, Dongge Liu, Qiang Hu, Xiaohong Li, Yang Liu

Published: 2026-11-05T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Fuzzing/Fuzz testing](<https://devfeed.tech/topics/fuzzing.md>), [patches](<https://devfeed.tech/topics/patches.md>), [builds](<https://devfeed.tech/topics/builds.md>), [open source maintenance](<https://devfeed.tech/topics/open-source-maintenance.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [build](<https://devfeed.tech/tags/build.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [fuzzing](<https://devfeed.tech/tags/fuzzing.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [repair](<https://devfeed.tech/tags/repair.md>), [security-testing](<https://devfeed.tech/tags/security-testing.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

FuzzMedic repairs OSS-Fuzz build breakages through evidence-guided diagnosis across project and fuzzing-infrastructure artifacts. It tracks workspace changes and build feedback in a repair-state graph, using branching and rollback to recover from unproductive repair paths. Candidate patches must restore executable fuzz targets, not just silence build failures. On 128 reproducible failures drawn from 1,820 real-world failures, it achieved a 48.44% repair rate and outperformed three program-repair baselines. In real-world use, 29 patches were merged upstream or into OSS-Fuzz, including fixes for three failures unresolved for over a year and two that had never built successfully.

### Source excerpt

arXiv:2611.06358v1 Announce Type: new Abstract: Continuous fuzzing platforms such as OSS-Fuzz provide sustained security testing for open-source projects, but long-term build breakages reduce security coverage and waste infrastructure resources. In OSS-Fuzz, around 20% of integrated projects remain in build-failure states, leaving their fuzzers off duty. These failures expose a maintenance gap between platform maintainers, who lack project-specific context, and project maintainers, who often lack fuzzing and infrastructure expertise. Existing program-repair techniques cannot be directly applied because fuzz build breakages span evolving project and infrastructure artifacts and require repeated infrastructure-aware diagnosis. We present FuzzMedic, an automated agent for fuzz build repair. FuzzMedic performs evidence-guided diagnosis across project and fuzzing-infrastructure artifacts. It explores repairs over a repair-state graph (RSG) that records the evolving workspace and build feedback. Branching and rollback enable FuzzMedic to recover from unproductive repair paths during long-horizon debugging. Candidate patches are validated to restore executable fuzz targets rather than merely suppress build failures. We evaluate FuzzMedic on 128 reproducible OSS-Fuzz build failures extracted from 1,820 real-world failures. FuzzMedic achieves a 48.44% repair rate and outperforms three representative program-repair baselines. In real-world use, it produces 29 patches merged into upstream or OSS-Fuzz main branches, including repairs for three failures that had remained unresolved for more than one year and two cases that had never built successfully.

## Building Windows C# Tools and Payloads from Kali Linux

DevFeed: [Building Windows C# Tools and Payloads from Kali Linux](<https://devfeed.tech/articles/building-windows-c-tools-and-payloads-from-kali-linux-118957.md>)

Original publisher: [Read original article](<https://www.kali.org/blog/windows-csharp-payloads/>)

Published: 2026-11-04T00:00:00Z

Content type: tutorial

Language: en

Sources: [Kali Linux](<https://devfeed.tech/sources/kali-linux.md>)

Topics: [Cross-Compilation](<https://devfeed.tech/topics/cross-compilation.md>), [builds](<https://devfeed.tech/topics/builds.md>), [Windows](<https://devfeed.tech/topics/windows.md>), [WINE](<https://devfeed.tech/topics/wine.md>), [.NET Framework](<https://devfeed.tech/topics/net-framework.md>), [console](<https://devfeed.tech/topics/console.md>), [Process](<https://devfeed.tech/topics/process.md>)

Tags: [advanced](<https://devfeed.tech/tags/advanced.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [clm](<https://devfeed.tech/tags/clm.md>), [compile](<https://devfeed.tech/tags/compile.md>), [distribution](<https://devfeed.tech/tags/distribution.md>), [kali](<https://devfeed.tech/tags/kali.md>), [kali-linux](<https://devfeed.tech/tags/kali-linux.md>), [kalilinux](<https://devfeed.tech/tags/kalilinux.md>), [linux](<https://devfeed.tech/tags/linux.md>), [penetration](<https://devfeed.tech/tags/penetration.md>), [penetration-testing](<https://devfeed.tech/tags/penetration-testing.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tools](<https://devfeed.tech/tags/tools.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

The article shows how Kali Linux can build and run Windows C# artifacts for penetration-testing exercises. Install `mono-devel` and use `mcs` to compile C# into a Windows executable or DLL; `wine` with `wine-mono` can run ordinary binaries on Kali. A Constrained Language Mode bypass example additionally requires Microsoft PowerShell and installer DLLs, which the article locates in files downloaded by configuring `powershell-empire`. It also describes using the `csharp` interpreter with a shell function to transform `msfvenom` output, and compiling Rubeus with `dotnet publish` using a patch for a self-contained build. For DotNetToJScript, the authors use repository binaries because they could not compile them; that workflow requires `wine` and `dotnet35`, since `wine-mono` alone did not work. These are article-specific procedures; the supplied text does not establish broader compatibility or current package availability.

### Source excerpt

One of our team members recently took (and passed!) OffSec's advanced penetration testing course & exam, PEN-300/OSEP. Whilst it focuses a lot on Microsoft Windows, there were a few extra places where Linux could be used to complete the same task... just quicker! Compiling C# code in Kali In general, what you need for compiling CSharp (C#) code in Kali is mono-devel : kali@kali:~$ sudo apt install mono-devel Now we need some code to compile. Here's a very basic way of executing a program (process): using System; using System.Diagnostics; namespace Exec { class Program { static void Main() { Process proc = new Process(); ProcessStartInfo procInfo = new ProcessStartInfo("cmd.exe", "/T:09 /K systeminfo"); procInfo.CreateNoWindow = false; procInfo.UseShellExecute = false; proc.StartInfo = procInfo; proc.Start(); } } } If you would like some more examples to get you going, try a Shellcode Launcher or a Simple Reverse Shell. All that is left is to compile: kali@kali:~$ TERM=linux mcs -out:exec.exe exec.cs kali@kali:~$ kali@kali:~$ file exec.* exec.cs: C++ source, ASCII text exec.exe: PE32 executable for MS Windows 4.00 (console), Intel i386 Mono/.Net assembly, 3 sections kali@kali:~$ How to run these binaries from Kali Linux Simple: just install wine and wine-mono. It's really handy, as you can test your Windows binaries (even reverse shells) directly from Kali: kali@kali:~$ sudo dpkg --add-architecture i386 kali@kali:~$ sudo apt update [...] kali@kali:~$ sudo apt -y install wine32 [...] kali@kali:~$ # Install wine-mono kali@kali:~$ wget https://dl.winehq.org/wine/wine-mono/11.3.0/wine-mono-11.3.0-x86.msi [...] kali@kali:~$ kali@kali:~$ wine msiexec /i wine-mono-11.3.0-x86.msi [...] kali@kali:~$ And now, to run your freshly built .exe binary, just use: kali@kali:~$ wine exec.exe Constrained Language Mode Bypass It's not always that easy -- sometimes things get a bit trickier. For example, for compiling the Constrained Language Mode (CLM) bypass section, we need some DLL libr

## Your Compose Code, on More Screens and Less CPU

DevFeed: [Your Compose Code, on More Screens and Less CPU](<https://devfeed.tech/articles/your-compose-code-on-more-screens-and-less-cpu-109731.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/compose-on-more-screens/>)

Author: Shai Almog

Published: 2026-10-31T00:00:00Z

Content type: opinion

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [builds](<https://devfeed.tech/topics/builds.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [battery](<https://devfeed.tech/tags/battery.md>), [battery-life](<https://devfeed.tech/tags/battery-life.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [button](<https://devfeed.tech/tags/button.md>), [bytecode](<https://devfeed.tech/tags/bytecode.md>), [card](<https://devfeed.tech/tags/card.md>), [class](<https://devfeed.tech/tags/class.md>), [code](<https://devfeed.tech/tags/code.md>), [codename](<https://devfeed.tech/tags/codename.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [components](<https://devfeed.tech/tags/components.md>), [compose](<https://devfeed.tech/tags/compose.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [screen](<https://devfeed.tech/tags/screen.md>)

### AI overview

Codename One can build Kotlin Multiplatform Compose code from the same `commonMain` sources: Kotlin compiles to JVM bytecode with the Compose compiler plugin, uses upstream Compose runtime and coroutines, and maps the UI layer to Codename One components before ParparVM creates native binaries. In the Keynote app benchmark, all three release builds reached the same frame rate, while Compose on Codename One used about 4 ms of CPU per frame versus about 17 ms for Compose Multiplatform. The measurements used an iPhone 17 Pro simulator, programmatic scrolling, and five runs; startup comparisons are limited because the Compose Multiplatform marker precedes drawing and most startup time came from iOS. The article reports a 16.8 MB executable versus 22.9 MB for Compose Multiplatform, and says imperative Java on Codename One was faster and about half the size of its Compose version. Teams can mix Compose and Codename One components per screen. The port is incomplete: `LazyColumn(reverseLayout = true)` is unsupported, and its build targets JVM 11.

### Source excerpt

Kotlin Multiplatform code with Compose now builds as a Codename One app, with about a quarter of the CPU work per frame on our benchmark screen.

## Flutter Better in Java

DevFeed: [Flutter Better in Java](<https://devfeed.tech/articles/flutter-better-in-java-109732.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/flutter-better-in-java/>)

Author: Shai Almog

Published: 2026-10-30T00:00:00Z

Content type: comparison

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [builds](<https://devfeed.tech/topics/builds.md>), [Android](<https://devfeed.tech/topics/android.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [mobile devops](<https://devfeed.tech/topics/mobile-devops.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [JavaFX](<https://devfeed.tech/topics/javafx.md>), [Swing](<https://devfeed.tech/topics/swing.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [maven-plugin](<https://devfeed.tech/topics/maven-plugin.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-apps](<https://devfeed.tech/tags/android-apps.md>), [build](<https://devfeed.tech/tags/build.md>), [code](<https://devfeed.tech/tags/code.md>), [dart](<https://devfeed.tech/tags/dart.md>), [faster](<https://devfeed.tech/tags/faster.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [java](<https://devfeed.tech/tags/java.md>), [javafx](<https://devfeed.tech/tags/javafx.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [memory](<https://devfeed.tech/tags/memory.md>)

### AI overview

Codename One can import Flutter apps from their original Dart source and build them as Codename One apps. In the October 29 CI comparison of Flutter Gallery release builds, Codename One led on all 26 measured metrics; on Android it used 4.7 MB of executable code versus 20.6 MB and started in about a third of the time. The importer copies app code and assets, adds a Dart runtime implemented through Java transpilation, and builds with Maven without requiring the Dart or Flutter SDK. The result is not pixel-identical: some text wrapping and avatar shapes differ, Dart support is experimental, some callbacks or parameters are ignored, and only one large app has been verified. The author advises testing every relied-on interaction. Android timings use an emulator; iOS start-up and memory and web start-up were not measured. The post attributes the smaller native builds partly to ahead-of-time Java compilation and dead-code elimination, while noting the compatibility layer itself adds overhead.

### Source excerpt

Codename One now builds Flutter apps from their Dart source, and the result starts faster, uses less memory and ships less code than Flutter's own release build. This week also covers KMP, Swing and JavaFX, Android apps and more.

## Nim version 2.4.0 released

DevFeed: [Nim version 2.4.0 released](<https://devfeed.tech/articles/nim-version-2-4-0-released-105423.md>)

Original publisher: [Read original article](<https://nim-lang.org//blog/2026/10/28/nim-240.html>)

Published: 2026-10-28T00:00:00Z

Content type: release

Language: en

Sources: [Nim Programming Language](<https://devfeed.tech/sources/nim-programming-language.md>)

Topics: [Nim](<https://devfeed.tech/topics/nim.md>), [version](<https://devfeed.tech/topics/version.md>), [builds](<https://devfeed.tech/topics/builds.md>)

Tags: [algorithm](<https://devfeed.tech/tags/algorithm.md>), [api](<https://devfeed.tech/tags/api.md>), [convenient](<https://devfeed.tech/tags/convenient.md>), [cycles](<https://devfeed.tech/tags/cycles.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [efficiency](<https://devfeed.tech/tags/efficiency.md>), [features](<https://devfeed.tech/tags/features.md>), [incremental](<https://devfeed.tech/tags/incremental.md>), [low-level](<https://devfeed.tech/tags/low-level.md>), [new-features](<https://devfeed.tech/tags/new-features.md>), [nim](<https://devfeed.tech/tags/nim.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [parallel](<https://devfeed.tech/tags/parallel.md>), [porting](<https://devfeed.tech/tags/porting.md>), [rebuilds](<https://devfeed.tech/tags/rebuilds.md>), [release](<https://devfeed.tech/tags/release.md>), [release-highlights](<https://devfeed.tech/tags/release-highlights.md>), [small](<https://devfeed.tech/tags/small.md>), [sso](<https://devfeed.tech/tags/sso.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

Nim 2.4.0 adds SSO strings, parallel incremental compilation, thread-safe cycle collection, concise sum types, and explicitly declared cyclic imports. SSO requires porting raw string pointer access to intent-specific helpers such as `readRawData` and `beginStore`/`endStore`; this API works across string backends, though SSO may not improve every program. Incremental compilation uses multiprocessing, and compile-time macros that rely on global state may need changes. YRC supports cycles shared across threads with ORC's API, at a reported cost of about twice the runtime and memory in `orcbench`. Sum types remove the explicit discriminator declaration and restrict field access through pattern matching. Cyclic imports use `{.cyclic.}` to enable phase-by-phase checking. The release also describes experimental `owned` references, which require `--experimental:ownedRefs` and may change incompatibly. Nim 2.2.14 is available for users who want to stay on that series.

### Source excerpt

The Nim Team is happy to announce version 2.4.0, our new stable release. After a way-too-long period of development, Nim 2.4 has finally become a reality. This is a major update shipping major new features: --strings:sso for improved string processing efficiency. --ic:on for parallel, incremental rebuilds. --mm:yrc, a new cycle collection algorithm that supports cycles spanning multiple threads. More convenient sum types. Cyclic module dependencies: still not encouraged, but fair game once you declare them with {.cyclic.}. If you're still on Nim 1.6, take a look at the version 2.0 release article to see all the features you're missing. If you've been using Nim 2.0, the version 2.2 release article shows the improvements available in Nim 2.2. If you want to stay on Nim 2.2 for now, we also released version 2.2.14 today, a patch release with many bugfixes and security fixes. Installing Nim 2.4.0 Check out if the package manager of your OS already ships version 2.4.0 or install it as described here. If you have installed a previous version of Nim using choosenim, getting Nim 2.4.0 is as easy as: $ choosenim update self $ choosenim update stable NOTE: We recommend that you install and use the latest version of choosenim, v0.8.16, available in our choosenim repo. Alternatively, you can download Nim 2.4.0 from our nightlies builds. Release highlights Strings based on the small-string optimization (SSO) SSO-based strings come with a new low-level strings API that you have to use in order to use this switch effectively. Nim's new strings API is compatible with Nimony's, so porting is always beneficial, even if --strings:sso might not improve the performance of your code. See it as a worthwhile, future-proof refactoring in its own right. The general idea behind this API is to deprecate the operation addr myString[offset] and to replace it with operations that clarify the intent. Reading is distinguished from writing. Here is our porting guide: Purpose Use Notes Read-only raw

## Warm builds. Introducing Avrea persistent disks

DevFeed: [Warm builds. Introducing Avrea persistent disks](<https://devfeed.tech/articles/warm-builds-introducing-avrea-persistent-disks-122859.md>)

Original publisher: [Read original article](<https://avrea.com/blog/persistent-disks>)

Author: Hannu Valtonen

Published: 2026-10-27T10:00:00Z

Content type: release

Language: en

Sources: [Avrea Blog](<https://devfeed.tech/sources/avrea-blog.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Filesystems](<https://devfeed.tech/topics/filesystems.md>), [build performance](<https://devfeed.tech/topics/build-performance.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [builds](<https://devfeed.tech/topics/builds.md>)

Tags: [also](<https://devfeed.tech/tags/also.md>), [application](<https://devfeed.tech/tags/application.md>), [archive](<https://devfeed.tech/tags/archive.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [avoid](<https://devfeed.tech/tags/avoid.md>), [away](<https://devfeed.tech/tags/away.md>), [based](<https://devfeed.tech/tags/based.md>), [benefit](<https://devfeed.tech/tags/benefit.md>), [best](<https://devfeed.tech/tags/best.md>), [branch](<https://devfeed.tech/tags/branch.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [ci](<https://devfeed.tech/tags/ci.md>), [docker](<https://devfeed.tech/tags/docker.md>), [jobs](<https://devfeed.tech/tags/jobs.md>), [keep](<https://devfeed.tech/tags/keep.md>), [layers](<https://devfeed.tech/tags/layers.md>), [reuse](<https://devfeed.tech/tags/reuse.md>), [with](<https://devfeed.tech/tags/with.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

Avrea persistent disks keep selected cache files across fresh CI VMs, letting tools reuse files in place instead of restoring and uploading archives. Teams choose cache paths and writer branches; jobs use separate copies, and pull requests can read saved state while their changes are discarded. Concurrent writers do not merge: the first to finish publishes, while stale writers are discarded. Normally completed writer jobs publish even after a step fails; cancelled or crashed jobs do not. Linux Docker caching can preserve images, build cache and volumes; container-based Buildx builders require a stable name and `keep-state: true`. Disks are best effort, may be unavailable in some datacenters, and jobs must work with an empty cache. Provisioned capacity is billed by OS and datacenter at $0.50/GB/month, whether full or not; the Docker cache uses the Linux disk at no extra charge.

### Source excerpt

Keep build caches and Docker layers between CI jobs with Avrea persistent disks. Reuse the work already done between your jobs.

## NativePHP Mobile Security Advisories: Update to 4.6.1

DevFeed: [NativePHP Mobile Security Advisories: Update to 4.6.1](<https://devfeed.tech/articles/nativephp-mobile-security-advisories-update-to-4-6-1-100505.md>)

Original publisher: [Read original article](<https://laravel-news.com/nativephp-mobile-security-advisories>)

Author: Yannick Lyn Fatt

Published: 2026-10-26T02:31:21Z

Content type: news

Language: en

Sources: [Laravel](<https://devfeed.tech/sources/laravel.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Mobile Security](<https://devfeed.tech/topics/mobile-security.md>), [NativePHP](<https://devfeed.tech/topics/nativephp.md>), [mobile devops](<https://devfeed.tech/topics/mobile-devops.md>), [builds](<https://devfeed.tech/topics/builds.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [app-store](<https://devfeed.tech/tags/app-store.md>), [async](<https://devfeed.tech/tags/async.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [binaries](<https://devfeed.tech/tags/binaries.md>), [bridge](<https://devfeed.tech/tags/bridge.md>), [bug](<https://devfeed.tech/tags/bug.md>), [build](<https://devfeed.tech/tags/build.md>), [but](<https://devfeed.tech/tags/but.md>), [cves](<https://devfeed.tech/tags/cves.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mobile-security](<https://devfeed.tech/tags/mobile-security.md>), [nativephp](<https://devfeed.tech/tags/nativephp.md>), [news](<https://devfeed.tech/tags/news.md>), [php](<https://devfeed.tech/tags/php.md>), [rebuild](<https://devfeed.tech/tags/rebuild.md>), [security](<https://devfeed.tech/tags/security.md>), [security-advisories](<https://devfeed.tech/tags/security-advisories.md>), [update](<https://devfeed.tech/tags/update.md>)

### AI overview

NativePHP fixed seven security issues in `nativephp/mobile` 4.6.1 and 3.3.11, and `nativephp/mobile-file` 1.0.3. Updating the package alone does not protect users: regenerate the native project with `php artisan native:install --force`, rebuild, and release the app. On 4.x, uninstall the file plugin because it can override patched core functions; on 3.x, update it to 1.0.3. The fixes also require events sent through the native endpoint to implement `DispatchableFromNative`; async tasks now require an app key. Most issues required JavaScript already running in the app web view. Versions 1.x and 2.x are end-of-life. Separately, NativePHP rebuilt its distributed binaries with PHP 8.5.12, 8.4.27, and 8.3.36 fixes. Hash and signature checking is available in Desktop 2.4.0 and Mobile 3.3.11, with Mobile 4.7.0 planned; apps must still be rebuilt and released to deliver the patched PHP.

### Source excerpt

NativePHP published seven security advisories for its mobile package, plus rebuilt PHP binaries for this week's PHP CVEs. Update to 4.6.1 or 3.3.11 and rebuild. The post NativePHP Mobile Security Advisories: Update to 4.6.1 appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

## Who wrote this byte?

DevFeed: [Who wrote this byte?](<https://devfeed.tech/articles/who-wrote-this-byte-98446.md>)

Original publisher: [Read original article](<https://fzakaria.com/2026/10/23/who-wrote-this-byte>)

Published: 2026-10-23T17:00:00Z

Content type: article

Language: en

Sources: [Farid Zakaria's Blog](<https://devfeed.tech/sources/farid-zakaria-s-blog.md>)

Topics: [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [reproducibility](<https://devfeed.tech/topics/reproducibility.md>), [Nix](<https://devfeed.tech/topics/nix.md>), [builds](<https://devfeed.tech/topics/builds.md>), [Data integrity in software engineering](<https://devfeed.tech/topics/data-integrity-in-software-engineering.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [GPU instancing](<https://devfeed.tech/topics/gpu-instancing.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [git](<https://devfeed.tech/tags/git.md>), [hash](<https://devfeed.tech/tags/hash.md>), [input](<https://devfeed.tech/tags/input.md>), [nix](<https://devfeed.tech/tags/nix.md>), [package](<https://devfeed.tech/tags/package.md>), [reproducibility](<https://devfeed.tech/tags/reproducibility.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

Rewind VM's `rewind blame` traces the first program that wrote a differing byte between two build runs. In the `tiles` example, varying Python's random hash seed changes the order of dependencies written to a pkg-config file; blame traces the difference through `install` to `python3`, and sorting the dependencies fixes it. Rewind records file writes and opens in the guest kernel, then reads those traces to identify byte provenance without replaying both runs. Its checks can vary random seeds, thread schedules, and directory-entry order, each of which can expose different sources of non-reproducibility. The excerpt also describes a visual comparison in the Rewind app and says recording overhead was measured as small enough to keep enabled in every run.

### Source excerpt

git blame for your build's bytes. 🔍 A build is bit reproducible when the same inputs give the same bytes. Why does reproducibility matter? They provide certainty that software is genuine and has not been tampered with. See reproducible-builds.org. Nix is infamously not bit reproducible, but rather input-addressed: the hash of a package is calculated from the inputs rather than the output.

## How an iOS Update Broke Chinese Text in War Robots (And How We Fixed It)

DevFeed: [How an iOS Update Broke Chinese Text in War Robots (And How We Fixed It)](<https://devfeed.tech/articles/how-an-ios-update-broke-chinese-text-in-war-robots-and-how-we-fixed-it-97765.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-an-ios-update-broke-chinese-text-in-war-robots-and-how-we-fixed-it?source=rss>)

Author: Sergey Madekin

Published: 2026-10-23T13:32:56Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Font](<https://devfeed.tech/topics/font.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [builds](<https://devfeed.tech/topics/builds.md>)

Tags: [automated](<https://devfeed.tech/tags/automated.md>), [bug](<https://devfeed.tech/tags/bug.md>), [build](<https://devfeed.tech/tags/build.md>), [chinese-character-rendering](<https://devfeed.tech/tags/chinese-character-rendering.md>), [font](<https://devfeed.tech/tags/font.md>), [font-subsetting](<https://devfeed.tech/tags/font-subsetting.md>), [fonts](<https://devfeed.tech/tags/fonts.md>), [game-development](<https://devfeed.tech/tags/game-development.md>), [ios](<https://devfeed.tech/tags/ios.md>), [ios-18-font-bug](<https://devfeed.tech/tags/ios-18-font-bug.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [robots](<https://devfeed.tech/tags/robots.md>), [text](<https://devfeed.tech/tags/text.md>), [unicode-surrogate-pairs](<https://devfeed.tech/tags/unicode-surrogate-pairs.md>), [unity](<https://devfeed.tech/tags/unity.md>), [unity-build-size-optimization](<https://devfeed.tech/tags/unity-build-size-optimization.md>), [unity-font-rendering](<https://devfeed.tech/tags/unity-font-rendering.md>), [unity-legacy-text](<https://devfeed.tech/tags/unity-legacy-text.md>), [update](<https://devfeed.tech/tags/update.md>)

### AI overview

After iOS 18, War Robots players saw missing or inconsistent Chinese glyphs because Unity's dynamic Legacy Text could fall back to different system fonts across devices. Bundling Noto Sans SC fixed rendering, but its roughly 10 MB TTF added 37 MB to the build. The team used pyftsubset with unique characters extracted from localization resources, reducing the font to about 900 KB and the build increase to 1.24 MB. Rare characters in configuration strings and player names required a supplementary list; obscure future usernames may still need reported characters added. A custom Unity Editor tool downloads upcoming translations, gathers and validates glyphs, merges supplements, optionally preserves prior release coverage, then generates the subset. The workflow also handles supplementary Unicode characters as full surrogate pairs, avoiding corruption from deduplicating UTF-16 char units; this issue is separate from the original font fallback bug.

### Source excerpt

See how War Robots fixed missing Chinese characters after an iOS update, shrinking font assets by 90% (from 10MB to 900KB) with a custom Unity pipeline.

## pnpm 11.28.8

DevFeed: [pnpm 11.28.8](<https://devfeed.tech/articles/pnpm-11-28-8-96391.md>)

Original publisher: [Read original article](<https://pnpm.io/blog/releases/11.28.8>)

Author: Zoltan Kochan

Published: 2026-10-22T00:00:00Z

Content type: release

Language: en

Sources: [pnpm](<https://devfeed.tech/sources/pnpm-blog.md>)

Topics: [pnpm](<https://devfeed.tech/topics/pnpm.md>), [builds](<https://devfeed.tech/topics/builds.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [trust](<https://devfeed.tech/topics/trust.md>)

Tags: [builds](<https://devfeed.tech/tags/builds.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [certificate-authority](<https://devfeed.tech/tags/certificate-authority.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [embedded](<https://devfeed.tech/tags/embedded.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [october](<https://devfeed.tech/tags/october.md>), [october-2026](<https://devfeed.tech/tags/october-2026.md>), [patch](<https://devfeed.tech/tags/patch.md>), [pnpm](<https://devfeed.tech/tags/pnpm.md>)

### AI overview

pnpm 11.28.8 updates standalone `@pnpm/exe` builds to embed Node.js 26.12.1. The prior Node.js 26.0.0 build still trusted certificate authority intermediates that Node.js distrusted in October 2026, allowing it to accept TLS certificates issued under those intermediates.

### Source excerpt

# pnpm 11.28.8 ## Patch Changes# - The standalone `@pnpm/exe` builds now embed Node.js 26.12.1. The previously embedded Node.js 26.0.0 still trusted the certificate authority intermediates that Node.js distrusted in October 2026, so a standalone pnpm accepted TLS certificates issued under them.

## RELAY: Scaling Historical Build Restoration through Rule Reuse and Agentic Repair

DevFeed: [RELAY: Scaling Historical Build Restoration through Rule Reuse and Agentic Repair](<https://devfeed.tech/articles/relay-scaling-historical-build-restoration-through-rule-reuse-and-agentic-repair-93705.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.27784>)

Author: Olivier Nourry, Yoshiki Higo

Published: 2026-10-21T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [builds](<https://devfeed.tech/topics/builds.md>), [rule-engine](<https://devfeed.tech/topics/rule-engine.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [approach](<https://devfeed.tech/tags/approach.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [automated](<https://devfeed.tech/tags/automated.md>), [base](<https://devfeed.tech/tags/base.md>), [base-images](<https://devfeed.tech/tags/base-images.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [can](<https://devfeed.tech/tags/can.md>), [cases](<https://devfeed.tech/tags/cases.md>), [change](<https://devfeed.tech/tags/change.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [relay](<https://devfeed.tech/tags/relay.md>), [repair](<https://devfeed.tech/tags/repair.md>), [restoration](<https://devfeed.tech/tags/restoration.md>), [reuse](<https://devfeed.tech/tags/reuse.md>), [scaling](<https://devfeed.tech/tags/scaling.md>)

### AI overview

Across 14,159 OSS-Fuzz cases, 69.7% no longer complete reconstruction and verification as external build resources change. Relay uses an LLM to derive and validate deterministic repair rules from representative failures, then reuses those rules without further model calls; unresolved cases go to a per-case agent. The abstract reports that rule derivation can be fully automated and rules restore as many builds as per-case agents with fewer build executions, while agents can repair cases rules cannot. Applying rules first and escalating the remainder restores more builds than either method alone, at lower cost than using agents alone.

### Source excerpt

arXiv:2610.27784v1 Announce Type: new Abstract: Vulnerability benchmarks and software engineering research depend on rebuilding historical software. Yet builds rely on external resources, such as base images and packages, that change independently of the source code. In this study, we examine this environment decay on 14,159 OSS-Fuzz cases. We find that 69.7% no longer complete reconstruction and verification, and that most failures share a small number of recurring failure symptoms. A recurring failure can therefore be diagnosed once and its repair reused. We present Relay, a hybrid framework that uses an LLM to derive and validate deterministic repair rules from representative failures, reuses them without model calls, and escalates cases unresolved by rules to a per-case agent. We evaluate Relay in human-guided and fully automated rule-derivation campaigns and compare it with a per-case agent approach. We find that rule derivation can be fully automated, and that reusable rules restore as many builds as per-case agents with fewer build executions. However, agents restore cases that the rules cannot. Our results show that a hybrid approach that applies rules first and escalates the remaining cases to an agent restores more builds than either approach alone and at a lower cost than using agents alone.

## What to Do When Your Constants Are Someone Else's Law

DevFeed: [What to Do When Your Constants Are Someone Else's Law](<https://devfeed.tech/articles/what-to-do-when-your-constants-are-someone-else-s-law-85019.md>)

Original publisher: [Read original article](<https://www.freecodecamp.org/news/what-to-do-when-your-constants-are-someone-else-s-law/>)

Author: Javeed Shaik

Published: 2026-10-11T14:05:40Z

Content type: tutorial

Language: en

Sources: [Free Code Camp](<https://devfeed.tech/sources/freecodecamp-programming-tutorials-python-javascript-git-more.md>)

Topics: [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [builds](<https://devfeed.tech/topics/builds.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [bug](<https://devfeed.tech/tags/bug.md>), [code](<https://devfeed.tech/tags/code.md>), [code-quality](<https://devfeed.tech/tags/code-quality.md>), [fintech](<https://devfeed.tech/tags/fintech.md>), [go-language](<https://devfeed.tech/tags/go-language.md>), [law](<https://devfeed.tech/tags/law.md>), [regulatory-compliance](<https://devfeed.tech/tags/regulatory-compliance.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

A tutorial on writing software that encodes external rules, using finance and tax calculators as examples. It recommends documenting the governing authority and meaning of inputs, exposing changeable statutory values as configurable defaults, and moving validation into library functions so callers cannot trigger unbounded work.

### Source excerpt

A colleague once asked me why a number in my code had a comment three lines long. The number was 18. The comment said which rule it came from, which section notified it, and that it could change witho

## pnpm 12.12.0

DevFeed: [pnpm 12.12.0](<https://devfeed.tech/articles/pnpm-12-12-0-84572.md>)

Original publisher: [Read original article](<https://pnpm.io/blog/releases/12.12.0>)

Author: Zoltan Kochan

Published: 2026-10-10T00:00:00Z

Content type: release

Language: en

Sources: [pnpm](<https://devfeed.tech/sources/pnpm-blog.md>)

Topics: [pnpm](<https://devfeed.tech/topics/pnpm.md>), [builds](<https://devfeed.tech/topics/builds.md>)

Tags: [cache](<https://devfeed.tech/tags/cache.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

pnpm 12.12.0 adds remote caching for task results and dependency builds, introduces addMissingPeerTypes for peer dependency type resolution, and improves configuration dependency management. It also fixes build permission handling, workspace deployment and peer resolution issues, and improves some installation and workspace discovery performance.

### Source excerpt

This release shares task results and dependency builds through a remote cache, adds the addMissingPeerTypes setting, and lets pnpm add --config and pnpm update manage configuration dependencies. It also fixes dangerouslyAllowAllBuilds running the build scripts of packages that allowBuilds denies.

## Adopting Pyrefly as the Python type checker at Google

DevFeed: [Adopting Pyrefly as the Python type checker at Google](<https://devfeed.tech/articles/adopting-pyrefly-as-the-python-type-checker-at-google-66435.md>)

Original publisher: [Read original article](<http://opensource.googleblog.com/2026/10/adopting-pyrefly-as-the-python-type-checker-at-google.html>)

Author: Google Open Source (noreply@blogger.com)

Published: 2026-10-06T18:30:00Z

Content type: article

Language: en

Sources: [Google Open Source Blog](<https://devfeed.tech/sources/google-open-source-blog.md>)

Topics: [Python](<https://devfeed.tech/topics/python.md>), [typesafety](<https://devfeed.tech/topics/typesafety.md>), [builds](<https://devfeed.tech/topics/builds.md>), [Google](<https://devfeed.tech/topics/google.md>)

Tags: [addition](<https://devfeed.tech/tags/addition.md>), [adopting](<https://devfeed.tech/tags/adopting.md>), [agents](<https://devfeed.tech/tags/agents.md>), [alternatives](<https://devfeed.tech/tags/alternatives.md>), [away](<https://devfeed.tech/tags/away.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [build](<https://devfeed.tech/tags/build.md>), [build-system](<https://devfeed.tech/tags/build-system.md>), [bytecode](<https://devfeed.tech/tags/bytecode.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [code](<https://devfeed.tech/tags/code.md>), [collective](<https://devfeed.tech/tags/collective.md>), [community](<https://devfeed.tech/tags/community.md>), [compute](<https://devfeed.tech/tags/compute.md>), [compute-resources](<https://devfeed.tech/tags/compute-resources.md>), [data](<https://devfeed.tech/tags/data.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [google](<https://devfeed.tech/tags/google.md>), [meta](<https://devfeed.tech/tags/meta.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [pyrefly](<https://devfeed.tech/tags/pyrefly.md>), [python](<https://devfeed.tech/tags/python.md>), [type](<https://devfeed.tech/tags/type.md>)

### AI overview

Google adopted Meta's open source Pyrefly as its Python type checker after deciding Pytype would stop supporting versions after Python 3.12. Google says Pytype's bytecode-based design made it harder to keep up with typing changes and deliver fast feedback. In internal benchmarks, Rust-based Pyrefly was about ten times faster, scored roughly 97% on the typing conformance suite, and reduced warm incremental rebuild latency by up to 98%. Cold-cache builds saw a 90-99% reduction in type checking's share of the critical path, while peak compute occupancy fell by more than 80%. Pyrefly also enforces sound union checks that Pytype historically allowed through, and provides inline diagnostics with occasional suggested fixes.

### Source excerpt

by Amer Elsheikh, Python Team Python is one of the primary languages at Google, powering everything from machine learning research to developer infrastructure and data pipelines. Across hundreds of thousands of files in our monorepo, fast and reliable static type checking is essential for maintaining code safety and developer velocity. Today, Pyrefly--an open source type checker developed by Meta--is the Python type checker at Google. Replacing our previous type-checking infrastructure with Pyrefly provided significant speedups for engineers and agents alike, while substantially reducing build-system compute resources. Moving away from Pytype For more than a decade, Google relied on Pytype, an internally developed type checker that pioneered Python type checking and collaborated with the open source community to create typeshed. However, as Python's typing system evolved rapidly, Pytype faced fundamental challenges. Because it operated by analyzing compiled bytecode rather than source ASTs, keeping pace with modern typing PEPs became an increasing maintenance burden due to bytecode instability across Python releases. In addition, it struggled to deliver the fast turnaround times required for modern development loops. As detailed in the Pytype update, we decided that Python 3.12 would be the final supported version for Pytype, leading us to evaluate and adopt modern open source alternatives. Why Pyrefly? Pyrefly incorporates years of collective lessons from earlier tools across the Python typing ecosystem. When evaluating candidates to succeed Pytype, Pyrefly quickly stood out across three key areas: Performance Written in Rust, Pyrefly is designed for high throughput and lazy, parallel evaluation. In our internal benchmarks across various Google projects, it proved to be an order of magnitude faster than Pytype, while scaling smoothly across large dependency graphs. Typing spec conformance Pyrefly achieves strong conformance--scoring roughly 97% on the official typing

## Siemens Abruptly Takes Down OpenRadioss, But a Fork is Already Live

DevFeed: [Siemens Abruptly Takes Down OpenRadioss, But a Fork is Already Live](<https://devfeed.tech/articles/siemens-abruptly-takes-down-openradioss-but-a-fork-is-already-live-65214.md>)

Original publisher: [Read original article](<https://feed.itsfoss.com/link/24361/17489673/siemens-openradioss-fork>)

Author: Sourav Rudra

Published: 2026-10-05T15:00:15Z

Content type: news

Language: en

Sources: [It's FOSS](<https://devfeed.tech/sources/it-s-foss.md>)

Topics: [Open Source](<https://devfeed.tech/topics/open-source.md>), [Maintainers](<https://devfeed.tech/topics/maintainers.md>), [builds](<https://devfeed.tech/topics/builds.md>)

Tags: [2022](<https://devfeed.tech/tags/2022.md>), [acquisition](<https://devfeed.tech/tags/acquisition.md>), [allows](<https://devfeed.tech/tags/allows.md>), [also](<https://devfeed.tech/tags/also.md>), [altair](<https://devfeed.tech/tags/altair.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [animation](<https://devfeed.tech/tags/animation.md>), [applying](<https://devfeed.tech/tags/applying.md>), [archive](<https://devfeed.tech/tags/archive.md>), [arm64](<https://devfeed.tech/tags/arm64.md>), [big-tech](<https://devfeed.tech/tags/big-tech.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [but](<https://devfeed.tech/tags/but.md>), [fork](<https://devfeed.tech/tags/fork.md>), [news](<https://devfeed.tech/tags/news.md>), [open](<https://devfeed.tech/tags/open.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [siemens](<https://devfeed.tech/tags/siemens.md>), [software](<https://devfeed.tech/tags/software.md>), [source](<https://devfeed.tech/tags/source.md>)

### AI overview

Siemens removed the OpenRadioss repository after acquiring Altair, redirecting visitors to a Simcenter Radioss transition page. An independent community fork, OpenCourant, preserves the commit history under the same GNU AGPLv3 license, which permits others to fork and build on the code. The project rebuilt its build pipeline after losing access to Siemens infrastructure and now distributes Linux and Windows x86_64 packages, including the previously uncommitted hm_reader binary, which a community member had saved and the team verified. ARM64 support and broader platform compatibility remain works in progress; the team is seeking specific release archives. The excerpt notes that INSTALL.md is still the OpenRadioss version and has not yet been updated for OpenCourant.

### Source excerpt

Another reminder of why open source saves software from being lost forever.

[Next page](<https://devfeed.tech/topics/builds.md?cursor=WyIyMDI2LTEwLTA1VDE1OjAwOjE1KzAwOjAwIiwgImE0NWZkMTEwLTJlOWUtNDFmZi1hMmI2LTlhMWY5YzUxMzU2NiJd>)