# fork Published articles for fork. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Vercel Sandbox supports forking DevFeed: [Vercel Sandbox supports forking]() Original publisher: [Read original article]() Author: Harpreet Arora Published: 2026-07-28T04:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [SDKs](), [Command-line interface](), [Template]() Tags: [agent](), [cli](), [config](), [documentation](), [fork](), [sdk](), [source](), [upgrade](), [vercel]() ### AI overview Vercel Sandbox now supports forking through Sandbox.fork(), allowing a sandbox to be created from the source's latest saved snapshot while inheriting configuration and environment variables. Forks can be used with the SDK or CLI and support overriding inherited parameters. ### Source excerpt Vercel Sandbox now supports forking with Sandbox.fork(). The fork starts from the source's current snapshot and inherits its config and environment variables. If the source is running, it forks the latest saved state, not the live in-memory state. If the source has no snapshot, it falls back to a fresh create, using the source's runtime and config. Any parameter you pass overrides the inherited value. A fork takes about the same time as creating a sandbox, with the same limits. Use it to branch an agent from a shared base, give each tenant its own copy of a template, or run variations of one setup in parallel. To fork a sandbox with the SDK: To fork a sandbox with the CLI: To get started, upgrade to the latest version: pnpm install @vercel/sandbox@latest # SDK pnpm install -g sandbox@latest # CLI Learn more in the Sandbox documentation. Read more ## OpenCode power user tips DevFeed: [OpenCode power user tips]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2026-06-03T16:00:00Z Content type: tutorial Language: en Sources: [Kaushik Gopal's Site]() Topics: [Agent Harness](), [Tooling](), [Open Source](), [Code]() Tags: [agent-harness](), [claude-code](), [codex](), [commands](), [fork](), [how-to](), [model](), [open-source](), [opencode](), [switching](), [tips]() ### AI overview A practical guide to advanced OpenCode features, including the leader key, session management, session forking, conversation rewind, and model switching. ### Source excerpt In this post, I'd like to talk about some power user tips for OpenCode - an open source, model agnostic harness that more people should be using. Hopefully some of the advanced use cases convince you to give OpenCode (and OpenChamber) a shot. intermediate to advanced tips only I am specifically choosing to talk about some advanced tips in this post. If you've never used an agent harness or are looking to learn how to use OpenCode, this post can be useful but reader beware. Unleash the leader key ## While ⌃p (Ctrl + P) will list out all the possible commands (and is helpful), OpenCode has the concept of a "leader" key (which defaults to ⌃x). The leader key allows you to execute targeted useful commands more quickly and there's a slew of useful ones pre-defined1. ctrl-p shows all commands. notice leader key bound to some Manage multiple sessions - leader l ## People reach for whole terminals and extra tooling to juggle between agent sessions. I too had an overly customized tmux setup that looked like this: Before: agent session listing via tmux OpenCode simplifies this. Just hit leader + l and you view current sessions and can instantly switch to that session by just selecting it from the list. After: leader-l allows quick session switching The ability to quickly rename a session from this view is a godsend for me and what lets me be organized. session directory filtering you can pass a --dir . flag to opencode when launching it, which filters the session list to just this workspace/directory by default. You can alternatively not pass that flag, and the session list will show all sessions. Fork (or Branch) sessions /fork ## Forking takes the session you're in and spawns a new one. You branch off into a separate conversation while the main agent keeps grinding on whatever you left it doing. I love this feature and even cobbled my own version with tmux long before most harnesses shipped it. Claude Code, Codex and other harnesses have caught up and support this feature. ## AI-driven zero-day combinations are challenging software security and open-source consumption DevFeed: [AI-driven zero-day combinations are challenging software security and open-source consumption]() Original publisher: [Read original article]() Published: 2026-05-28T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [Artificial Intelligence](), [open-source-security](), [Security](), [Open Source](), [Machine Learning, Security Attacks](), [Critical Infrastructure](), [openssf](), [sigstore]() Tags: [ai](), [anthropic-mythos](), [chainguard-containers](), [critical-infrastructure](), [fork](), [mfa](), [mythos](), [open-source](), [open-source-security](), [openssf](), [oss](), [project-glasswing](), [rust](), [sast](), [secure-open-source](), [security](), [sigstore]() ### AI overview The article argues that Mythos represents a potential new class of software-security threat: AI-driven combinations of existing issues that can produce more serious attacks than individual scanner findings. It discusses the limits of government regulation and calls for stronger trust infrastructure, coordinated disclosure, and safer open-source consumption. ### Source excerpt Mythos is changing software security fast. AI-driven zero-days demand new trust infrastructure, coordinated disclosure, and secure open source consumption. ## Fixing two minor git irritations in my OSS fork workflow DevFeed: [Fixing two minor git irritations in my OSS fork workflow]() Original publisher: [Read original article]() Author: Rob Published: 2026-05-26T10:00:00Z Content type: tutorial Language: en Sources: [Rob Allen]() Topics: [Git](), [Pull Request]() Tags: [branch](), [development](), [fork](), [git](), [oss](), [project](), [remote](), [repo](), [workflow]() ### AI overview A practical guide to reducing two minor irritations in an open-source Git fork workflow: ensuring the local main branch tracks upstream/main and configuring new branches to push to origin automatically on their first push. ### Source excerpt For OSS work, I work with two git remotes: upstream: the canonical OSS project repository, where main is the default branch and is what gets released. origin: a personal fork. All my feature branches live here. I set up locally like this: Fork the project repo to my account. Clone my fork locally, so the origin remote is my fork. Set an upstream remote using git remote add upstream . and then when working on... continue reading. ## Sandbox persistence is now GA DevFeed: [Sandbox persistence is now GA]() Original publisher: [Read original article]() Author: Harpreet Arora Published: 2026-05-26T00:01:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Persistence](), [Vercel](), [Command-line interface](), [SDKs]() Tags: [cli](), [compute](), [filesystem](), [fork](), [network](), [persistence](), [sandbox](), [sdk](), [snapshots](), [storage](), [upgrade](), [vercel](), [workflow]() ### AI overview Vercel Sandboxes now provide generally available persistence. Filesystem state is automatically saved and restored between sessions, with persistence enabled by default and sandboxes addressable by durable names. Users can opt out for ephemeral workloads, while persistent sandboxes resume from the latest snapshot automatically. ### Source excerpt Vercel Sandboxes now automatically save and restore filesystem state between sessions. Persistence is on by default, meaning no snapshots to manage or state to track manually. Each sandbox has a durable, customizable name that acts as a unique reference in your project. You can create, retrieve, or resume a sandbox by name. Vercel spins sessions up and down automatically, without interrupting your workflow. Create a persistent sandbox When you call Sandbox.create(), persistence is enabled by default: Each automatic snapshot consumes snapshot storage, which is billed separately from compute. For ephemeral workloads, opt out of persistence to minimize storage costs: To opt out of persistence with the CLI, pass --non-persistent to sandbox create. Non-persistent sandboxes discard their filesystem when the session ends. Resume a persistent sandbox Resuming is automatic. Any call on a stopped sandbox, like runCommand() or writeFiles(), starts a new session from the most recent snapshot. Other improvements Sandbox.fork(): Create a new sandbox from an existing one Sandbox.getOrCreate(): Idempotent retrieve-or-create for long-lived sandboxes Sandbox.delete(): Permanently delete a sandbox Richer sandbox.stop(): Returns snapshot metadata plus active-CPU and network-transfer totals Lifecycle hooks: onCreate and onResume hooks for create, get, and getOrCreate Tags: Assign custom properties to sandboxes for multi-tenant tracking Get started Upgrade to the latest version to create persistent sandboxes by default: pnpm install @vercel/sandbox@latest # SDK pnpm install -g sandbox@latest # CLI Learn more about persistent sandboxes in the documentation. Read more ## Endive and the Next Chapter of WebAssembly on the JVM DevFeed: [Endive and the Next Chapter of WebAssembly on the JVM]() Original publisher: [Read original article]() Author: Andrea Peruffo Published: 2026-05-26T00:00:00Z Content type: release Language: en Sources: [Bytecode Alliance]() Topics: [WebAssembly](), [Java](), [Compiler](), [Open Source]() Tags: [announcement](), [compiler](), [fork](), [java](), [jvm](), [open-source](), [webassembly]() ### AI overview Bytecode Alliance announces Endive, a fork of Chicory and a hosted project for running WebAssembly on the JVM. The project aims to let Java developers embed, package, test, and deploy Wasm modules through familiar Java workflows, while integrating the experimental Redline compiler for native machine-code compilation. ### Source excerpt Announcement: Endive begins In September 2023, a small group of contributors set out to answer a simple question: can WebAssembly run on the JVM with zero native dependencies? The project they built, Chicory, proved it could. Within two years it was powering JRuby's Prism parser, a pure-Java SQLite driver, an embedded PostgreSQL, a pure-Java QuickJs runtime, TrinoDB Python UDFs, and many more. What started as an experiment became infrastructure. ## Backdoored node-ipc npm releases steal developer credentials through DNS queries DevFeed: [Backdoored node-ipc npm releases steal developer credentials through DNS queries]() Original publisher: [Read original article]() Author: Nick Frichette Published: 2026-05-14T00:00:00Z Content type: article Language: en Sources: [Datadog Security Labs]() Topics: [Malware](), [npm](), [backdoor](), [payload](), [Amazon Route 53](), [Code](), [Cloud](), [Kubernetes](), [Databases](), [OpenSSH]() Tags: [analysis](), [backdoor](), [cloud](), [code](), [database](), [developer](), [dns](), [fork](), [kubernetes](), [malware](), [npm](), [payload](), [process](), [ssh]() ### AI overview This article analyzes three backdoored node-ipc releases published to npm on May 14, 2026. The malicious CommonJS entrypoint launches a detached process, collects environment, host, developer, cloud, package manager, source control, Kubernetes, database, and SSH credentials, archives the data, and attempts DNS TXT exfiltration. ### Source excerpt An analysis of backdoored node-ipc npm releases that add an obfuscated credential collection and DNS exfiltration payload to the CommonJS entrypoint. ## Git sync & workspace forks: your entire workspace, version controlled DevFeed: [Git sync & workspace forks: your entire workspace, version controlled]() Original publisher: [Read original article]() Author: Tristan Lécuyer Published: 2026-04-02T00:00:00Z Content type: release Language: en Sources: [Windmill Blog]() Topics: [Git](), [version-control](), [CI/CD](), [GitLab](), [GitHub]() Tags: [azure](), [bitbucket](), [ci-cd](), [fork](), [git](), [gitlab](), [launch-week](), [merge](), [pipelines](), [repository](), [review](), [rollback](), [sync]() ### AI overview Windmill introduces redesigned bidirectional Git sync and workspace forks. Git sync commits and pushes deployed items to a configured repository and can pull updates from Git, while forks provide isolated feature-development workspaces with deployment, merge, and Git-based workflows. ### Source excerpt Introducing improved Git sync and workspace forks: sync workspaces to Git, fork for feature development, and deploy via CI/CD. ## Get ready for Backstage ContribFest at KubeCon! DevFeed: [Get ready for Backstage ContribFest at KubeCon!]() Original publisher: [Read original article]() Author: André Wanlin, Spotify Published: 2025-10-15T00:00:00Z Content type: article Language: en Sources: [Backstage Software Catalog and Developer Platform Blog]() Topics: [Backstage](), [Node.js](), [Yarn](), [GitHub]() Tags: [2025](), [backstage](), [cncf](), [community](), [contribute](), [contributors](), [developer-experience](), [developer-portal](), [fork](), [getting-started](), [github](), [guide](), [idp](), [internal-developer-platform](), [kubecon](), [node](), [node-js](), [open-source](), [platform-engineering](), [projects](), [software-catalog](), [software-templates](), [techdocs]() ### AI overview A preparation guide for Backstage ContribFest at KubeCon 2025 North America. It explains the hands-on contribution session and recommends forking the Backstage repositories, installing Node.js 22 and Yarn, and testing the local setup beforehand. ### Source excerpt Get ready for Backstage ContribFest at KubeCon! ## Checkpoint #6: Oct 2025 DevFeed: [Checkpoint #6: Oct 2025]() Original publisher: [Read original article]() Author: Nixo Rokish Published: 2025-10-01T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Development](), [Testing](), [Network]() Tags: [2025](), [developer](), [ethereum](), [fork](), [monitor](), [network](), [research-development](), [test](), [testing](), [updates](), [upgrade]() ### AI overview This October 2025 checkpoint summarizes Ethereum core development, including the upcoming Fusaka testnet upgrade, Glamsterdam feature selections, testing beyond a 60 million gas limit, and lessons from the Holešky testnet fork and non-finality events. ### Source excerpt Ethereum's weekly All Core Developer calls are a lot to keep up with, so this "Checkpoint" series aims for high-level updates roughly every 4-5 weeks, depending on what's happening in core development. See the previous update here.... ## Why we maintain a ClickHouse® fork at Tinybird (how it's different) DevFeed: [Why we maintain a ClickHouse® fork at Tinybird (how it's different)]() Original publisher: [Read original article]() Author: Javi Santana, Maksim Kita Published: 2025-09-11T08:00:00Z Content type: article Language: en Sources: [Tinybird]() Topics: [clickhouse]() Tags: [clickhouse](), [fork](), [performance](), [tinybird-news]() ### AI overview Tinybird explains why it maintains a ClickHouse fork, stating that the fork is maintained for performance and describing the article as an explanation of its changes and significance for users. ### Source excerpt We maintain a ClickHouse fork at Tinybird. Not for ego. For performance. Here's what we changed and why it matters for you. ## Fork yeah: We're bringing kaniko back DevFeed: [Fork yeah: We're bringing kaniko back]() Original publisher: [Read original article]() Published: 2025-06-05T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [Open Source](), [supply-chain-security](), [container-security](), [Docker](), [Kubernetes]() Tags: [chainguard](), [container](), [container-security](), [deprecated](), [docker](), [docker-images](), [fork](), [google](), [kaniko](), [kubernetes](), [maintenance](), [open-source](), [safe-source-for-open-source](), [software-supply-chain]() ### AI overview Chainguard is forking and taking over maintenance of Kaniko after Google announced plans to archive it. The project will remain open and upstream, with a focus on maintenance and minor bug fixes rather than new features, while Chainguard also offers commercial Kaniko images for organizations needing zero-CVE or FIPS versions. ### Source excerpt Chainguard is taking over the maintenance of the Kaniko project, recently deprecated by Google. Learn more about why we're doing it and what is next. ## Ekapkgs, a poly-repo fork of Nixpkgs DevFeed: [Ekapkgs, a poly-repo fork of Nixpkgs]() Original publisher: [Read original article]() Author: Jon Ringer Published: 2025-03-31T00:00:00Z Content type: opinion Language: en Sources: [Nixcademy Blog]() Topics: [Nix](), [repo](), [Development](), [Maintainability](), [cloud-infrastructure]() Tags: [development](), [fork](), [glibc](), [infrastructure](), [maintainability](), [openssl](), [repo]() ### AI overview The article presents Ekapkgs as a poly-repository fork of Nixpkgs. It argues that Nixpkgs' monolithic scale, lengthy RFC process, and staging workflow make maintenance, convention changes, and package updates difficult, while separate repositories could enable faster iteration and more focused curation. ### Source excerpt Ekapkgs forks Nixpkgs, splitting it into repos for faster updates & easier curation. Ditch monolithic development flows & slow RFCs. Innovate freely! ## Introducing Limbo: A complete rewrite of SQLite in Rust DevFeed: [Introducing Limbo: A complete rewrite of SQLite in Rust]() Original publisher: [Read original article]() Author: Pekka Enberg Published: 2024-12-10T00:00:00Z Content type: article Language: en Sources: [Turso Blog]() Topics: [SQLite](), [Rust](), [libSQL](), [Turso]() Tags: [fork](), [libsql](), [memory-safe](), [rust](), [sqlite](), [turso]() ### AI overview The article introduces Limbo, an ambitious project to completely rewrite SQLite in Rust. It contrasts this approach with libSQL's earlier fork of SQLite and discusses goals such as memory safety, compatibility, easier evolution, and support for changes like asynchronous I/O. ### Source excerpt we forked SQLite with the libSQL project. What would it be like if we just rewrote it? ## How to copy large Postgres databases in seconds DevFeed: [How to copy large Postgres databases in seconds]() Original publisher: [Read original article]() Author: Carlota Soto Published: 2024-03-04T17:24:38Z Content type: tutorial Language: en Sources: [Blog -- Neon Docs]() Topics: [Databases](), [Development](), [Testing](), [data](), [Replication]() Tags: [backups](), [consistency](), [databases](), [fork](), [how-to](), [migrations](), [postgres](), [product](), [production](), [replication](), [storage](), [testing](), [upgrade]() ### AI overview The article explains why conventional methods for copying large Postgres databases become slow, resource-intensive, or costly, and presents Neon database branching as an alternative. Branching uses copy-on-write to create immediate copies while allocating additional storage only when the branch diverges. ### Source excerpt If you're running Postgres in production, you'll most likely be handling database copies not only as backups but also for creating development and testing environments that replicate production settings. Database copies also play a key role in preparing for migrations and upgrade... ## How to contribute to Open Source for the first time? DevFeed: [How to contribute to Open Source for the first time?]() Original publisher: [Read original article]() Author: Meri Nova Published: 2024-02-12T17:46:06Z Content type: tutorial Language: en Sources: [Meri Nova]() Topics: [Open Source](), [GitHub](), [Development](), [Pull Request](), [Git]() Tags: [contribute](), [fork](), [git](), [github](), [how-to](), [open-source](), [programming](), [pull-request]() ### AI overview A beginner-oriented tutorial explains why open-source contributions can provide practical collaborative experience and outlines a nine-step path to making a first contribution, including finding a project and issue, reviewing contribution guidelines, forking, and creating a branch. ### Source excerpt It is easier than you think. Follow this 9-step guideline to make your first contribution on Github with the help of active community. ## libSQL, the fork of SQLite, crosses 5k GitHub stars DevFeed: [libSQL, the fork of SQLite, crosses 5k GitHub stars]() Original publisher: [Read original article]() Author: Pekka Enberg Published: 2023-11-07T00:00:00Z Content type: article Language: en Sources: [Turso Blog]() Topics: [libSQL](), [SQLite](), [GitHub]() Tags: [community](), [fork](), [github](), [libsql](), [open](), [sqlite]() ### AI overview The article examines libSQL, an open contribution fork of SQLite, after it surpassed 5,000 GitHub stars. It reviews the reasons for the fork, what the project shipped, and how the community is shaping its direction. ### Source excerpt libSQL, our open contribution fork of SQLite, crossed 5,000 GitHub stars. A look back at why we forked, what we shipped, and where the community is taking it. ## We're bringing libSQL into the Turso family DevFeed: [We're bringing libSQL into the Turso family]() Original publisher: [Read original article]() Author: Glauber Costa Published: 2023-10-03T00:00:00Z Content type: article Language: en Sources: [Turso Blog]() Topics: [libSQL](), [Turso](), [SQLite](), [Open Source](), [Replication]() Tags: [cloud](), [community](), [databases](), [fork](), [libsql](), [offline](), [open-source](), [replication](), [sdks](), [sqlite](), [turso]() ### AI overview The article announces that libSQL is being brought into the Turso family after starting as a fork of SQLite. It explains that current Turso is a ground-up rewrite of SQLite, with Turso Cloud providing database access over the network and synchronization with users' devices and servers, including offline support. It also notes that legacy libSQL SDKs have been replaced by Turso-native SDKs and that edge replication is no longer a current concept. ### Source excerpt One year ago, we announced a bold project: a fork of SQLite. After noticing that SQLite doesn't welcome external contributions (Open Source, not Open Contribution), and companies were increasingly... ## 10x faster python test iteration via fork(2) DevFeed: [10x faster python test iteration via fork(2)]() Original publisher: [Read original article]() Author: raylu Published: 2023-07-20T16:01:45Z Content type: tutorial Language: en Sources: [Benchling]() Topics: [Python](), [Testing](), [SQLAlchemy](), [modules](), [import](), [Code]() Tags: [benchling](), [code](), [dependencies](), [developer-productivity](), [engineering](), [fork](), [import](), [modules](), [python](), [sqlalchemy](), [testing]() ### AI overview This Benchling Engineering article explains how the Build team reduced Python test iteration time in a dependency-heavy codebase. It discusses the limitations of importlib.reload() and describes a fork-based approach that made the second test run start 10 times faster, reducing waiting by 90%. ### Source excerpt It's ideal to get feedback on your code faster -- to make a code change and see the result instantly. But, as projects get larger, reload times get longer. Each incremental dependency or bootstrap code block that adds 200ms feels worth it, but 50 of them later and it takes 10 seconds to see the result of a code change. On the Build team at Benchling, that's where we found ourselves one day. We used 146 packages which pull in 128 transitive dependencies for a total of 274 packages. We also spent a lot of time waiting for SQLAlchemy models to initialize. The result is our test harness took 10 seconds to set up. After making a code change, you'd start the test runner, wait a few seconds, alt+tab to your browser, get distracted for a few minutes, and then find out you had a typo in your code. This is a common challenge for a growing codebase, but it's something we knew we needed to fix. Here's the process we arrived at which allowed the second run of tests to start 10x faster -- 90% less waiting. While it'll work a little differently for your codebase depending on the language, dependencies, etc. you're using, hopefully this can inspire you on your journey to faster feedback and testing. importlib.reload() Since the problem is that we spend so long setting up a bunch of modules just right and then want to see the change in a single file we're editing, the most obvious solution is to use importlib.reload from the standard library. import importlib import sys import test_harness_stuff # takes 10 seconds import tests def rerun_tests(changed_path): for mod in sys.modules.values(): if mod.__file__ == changed_path: importlib.reload(mod) tests.run_tests() break if __name__ == '__main__': setup_file_watcher(rerun_tests) tests.run_tests() This (with some special handling for built-in modules, relative path resolution, and batching to handle editors that perform multiple filesystem operations per save) works alright when the file being changed is a test file (or any other leaf node ## Imposter commits in GitHub Actions can bypass allowed workflow settings DevFeed: [Imposter commits in GitHub Actions can bypass allowed workflow settings]() Original publisher: [Read original article]() Published: 2023-03-08T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [GitHub Actions](), [GitHub](), [vulnerability](), [CI/CD](), [GitOps](), [Git](), [Pull Request]() Tags: [chainguard-enforce](), [ci-cd](), [fork](), [github](), [github-actions](), [github-vulnerability](), [gitops](), [pull-request](), [software-supply-chain](), [supply-chain](), [vulnerability](), [workflow]() ### AI overview Chainguard reports a GitHub Actions vulnerability in which commits from forked repositories can bypass allowed workflow settings. The article explains how GitHub fork and commit-sharing behavior enables these imposter commits and why they pose a CI/CD supply-chain security risk. ### Source excerpt Chainguard found a vulnerability in GitHub Actions that bypasses allowed Workflow settings by using commits from forked repositories. Read the report. ## Enterprise-ready Trino at Bloomberg: One Giant Leap Toward Data Mesh! DevFeed: [Enterprise-ready Trino at Bloomberg: One Giant Leap Toward Data Mesh!]() Original publisher: [Read original article]() Author: Vishal Jadhav, Pablo Arteaga, Cole Bowden Published: 2022-11-30T00:00:00Z Content type: article Language: en Sources: [Trino Blog]() Topics: [data](), [Availability](), [Security](), [Architecture & Design](), [Unified Access]() Tags: [availability](), [clusters](), [data](), [fork](), [high-availability](), [infrastructure](), [latency](), [load-balancer](), [low-latency](), [open](), [recap](), [security](), [series](), [summit](), [unified-access]() ### AI overview This recap describes Bloomberg's use of Trino to federate diverse financial data and provide unified access. It focuses on the Trino Load Balancer, a privacy-aware fork of presto-gateway that routes workloads across Trino clusters according to resource use and user needs while supporting high availability, performance, and data-access policies. ### Source excerpt This post continues a larger series of posts on the Trino Summit 2022 sessions. Following the Trino at Apple talk, engineers from Bloomberg shared the latest about their additions to Trino. Bloomberg uses Trino to federate huge amounts of disparate financial data together. When you have many users with different use cases and resource needs, you need something to ensure that the huge workloads don't bully the small ones. Enter the Trino Load Balancer, a privacy-aware solution to help maintain high availability while still treating data security as the first-class citizen that it should be. ## The Road to Altair: Pyrmont Testing and Prater Upgrade Scheduled DevFeed: [The Road to Altair: Pyrmont Testing and Prater Upgrade Scheduled]() Original publisher: [Read original article]() Author: Danny Ryan Published: 2021-08-25T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Testing](), [releases](), [Network](), [Code]() Tags: [code](), [configuration](), [consensus](), [deprecated](), [fork](), [load](), [network](), [offline](), [releases](), [research-development](), [scheduled](), [testing](), [upgrade]() ### AI overview This developer update reports that the Pyrmont public testnet successfully upgraded to Altair and is undergoing scenario testing. It schedules the Prater testnet upgrade for September 2 at 12pm UTC, with the Altair mainnet launch targeted for the end of September if testing and the Prater upgrade are successful. ### Source excerpt The Road to Altair edition 🛣⭐ tl;dr Pyrmont upgrade successful, scenario testing underway Prater upgrade scheduled for September 2, 12pm UTC Mainnet to follow... ## Ethereum consensus-layer series rebranded as Finalized; node upgrades required for Berlin DevFeed: [Ethereum consensus-layer series rebranded as Finalized; node upgrades required for Berlin]() Original publisher: [Read original article]() Author: Danny Ryan Published: 2021-03-11T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Protocol (disambiguation)](), [Software]() Tags: [consensus-algorithm](), [ethereum](), [fork](), [pow](), [proof-of-work](), [protocol](), [research-development](), [upgrade](), [upgrades]() ### AI overview The article announces that the blog series formerly associated with "eth2" will be rebranded as "Finalized: the Ethereum consensus-layer." It also explains that the Berlin mainnet upgrade requires Ethereum PoW node operators and beacon-chain stakers to update their software by the stated deadlines. ### Source excerpt tl;dr Finalized: rebranding the blog Upgrade your nodes!... ## Ethereum Berlin Upgrade Announcement DevFeed: [Ethereum Berlin Upgrade Announcement]() Original publisher: [Read original article]() Author: Tim Beiko Published: 2021-03-08T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Network](), [bug]() Tags: [announcement](), [bug](), [deprecated](), [fork](), [network](), [node](), [optional](), [protocol-announcements](), [release](), [release-schedule](), [upgrade]() ### AI overview Ethereum's Berlin upgrade is scheduled for deployment on testnets beginning with Ropsten on March 10, 2021, and on mainnet around April 15, 2021. The article lists compatible client versions, upgrade guidance for node operators, and the EIPs included in Berlin. ### Source excerpt TL;DR Berlin is ready to be deployed! We're moving fast: the first testnet to upgrade, Ropsten, is scheduled to upgrade on March 10th. Mainnet is scheduled for April 15th. If you are running an Ethereum node, you should upgrade it to a Berlin-compatible version ASAP for testnets and before... [Next page]()