---
title: "#release articles | Hashnode"
description: "Explore 34 articles tagged #release on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/release"
---

Tag

# #release

34 posts · 0 followers

[dev](https://hashnode.com/@rotiferdev) · [Nov 1](https://hashnode.com/posts/rotifer-v0-9-4-agents-get-a-memory-of-their-own-npm-0-33-0/6af469c7ee3296df916855a4)

### [Rotifer v0.9.4: Agents get a memory of their own (npm 0.33.0)](https://rotifer.hashnode.dev/rotifer-v0-9-4-agents-get-a-memory-of-their-own-npm-0-33-0?utm_source=hashnode&utm_medium=feed)

An agent now keeps a memory its genes read and write between runs. It belongs to the agent, so swapping a gene keeps it. Four categories, a quota with a fixed cleanup order, access scopes and retention, all stored on your machine.

7 min read · [rotifer.hashnode.dev](https://rotifer.hashnode.dev/rotifer-v0-9-4-agents-get-a-memory-of-their-own-npm-0-33-0?utm_source=hashnode&utm_medium=feed)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 27](https://hashnode.com/posts/agent-fixed-main-never-backported-release-branch/6ae0df33a95530826a245738)

### [The agent fixed the bug on main and never backported it to the release branch](https://blogs.powerduck.com/agent-fixed-main-never-backported-release-branch?utm_source=hashnode&utm_medium=feed)

The agent reproduced the bug on main, wrote the fix, watched the suite go green, and reported done. Customers on the supported release branch still hit it, because that branch kept the old code and nobody asked which version lines had to ship the fix.

3 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-fixed-main-never-backported-release-branch?utm_source=hashnode&utm_medium=feed)

[dev](https://hashnode.com/@rotiferdev) · [Oct 24](https://hashnode.com/posts/rotifer-v0-9-3-genes-scored-against-the-season-run-with-the-permissions-they-declare-npm-0-30-0/6ae4489175d75056f311c780)

### [Rotifer v0.9.3: Genes scored against the season, run with the permissions they declare (npm 0.30.0)](https://rotifer.hashnode.dev/rotifer-v0-9-3-genes-scored-against-the-season-run-with-the-permissions-they-declare-npm-0-30-0?utm_source=hashnode&utm_medium=feed)

Arena F(g) now compares a gene's measured latency and cost with the season median of its peers. Every CLI path runs a gene with exactly the permissions its phenotype declares, and each outbound request is checked before it is sent.

5 min read · [rotifer.hashnode.dev](https://rotifer.hashnode.dev/rotifer-v0-9-3-genes-scored-against-the-season-run-with-the-permissions-they-declare-npm-0-30-0?utm_source=hashnode&utm_medium=feed)

[dev](https://hashnode.com/@rotiferdev) · [Oct 21](https://hashnode.com/posts/rotifer-v0-9-2-export-an-agent-to-one-file-rebuild-it-on-another-machine-npm-0-29-0/6af1447bd4187a8a94129de2)

### [Rotifer v0.9.2: Export an agent to one file, rebuild it on another machine (npm 0.29.0)](https://rotifer.hashnode.dev/rotifer-v0-9-2-export-an-agent-to-one-file-rebuild-it-on-another-machine-npm-0-29-0?utm_source=hashnode&utm_medium=feed)

rotifer genome export writes an agent's genome to a .rgenome file; rotifer genome import rebuilds it from the Registry and says, gene by gene, what it installed and why. Four changes in 0.29.0 may affect existing use.

8 min read · [rotifer.hashnode.dev](https://rotifer.hashnode.dev/rotifer-v0-9-2-export-an-agent-to-one-file-rebuild-it-on-another-machine-npm-0-29-0?utm_source=hashnode&utm_medium=feed)

[dev](https://hashnode.com/@rotiferdev) · [Oct 19](https://hashnode.com/posts/rotifer-v0-9-1-content-derived-gene-ids-for-the-lan-p2p-node-npm-0-27-0/6af13582c06d737e50fab73d)

### [Rotifer v0.9.1: Content-derived gene IDs for the LAN P2P node (npm 0.27.0)](https://rotifer.hashnode.dev/rotifer-v0-9-1-content-derived-gene-ids-for-the-lan-p2p-node-npm-0-27-0?utm_source=hashnode&utm_medium=feed)

A gene's ID now comes from its content, not its name. The LAN P2P wire format is frozen and validated before relay. Two machines, one Wi-Fi, 1.4 s.

7 min read · [rotifer.hashnode.dev](https://rotifer.hashnode.dev/rotifer-v0-9-1-content-derived-gene-ids-for-the-lan-p2p-node-npm-0-27-0?utm_source=hashnode&utm_medium=feed)

[Manuel Spigolon](https://hashnode.com/@Eomm) · [Sep 1](https://hashnode.com/posts/how-we-are-securing-the-fastify-organization/6a966c80632c9685cd511981)

### [How we are securing the Fastify organization](https://backend.cafe/how-we-are-securing-the-fastify-organization?utm_source=hashnode&utm_medium=feed)

This is the story of a year of boring work behind the packages you install every day

9 min read · [backend.cafe](https://backend.cafe/how-we-are-securing-the-fastify-organization?utm_source=hashnode&utm_medium=feed)

[dev](https://hashnode.com/@rotiferdev) · [Jun 23](https://hashnode.com/posts/rotifer-v0-9-0-open-mesh-your-first-p2p-gene-node/6aef640237943d86f9ab3f4a)

### [Rotifer v0.9.0: Open Mesh — your first P2P gene node](https://rotifer.hashnode.dev/rotifer-v0-9-0-open-mesh-your-first-p2p-gene-node?utm_source=hashnode&utm_medium=feed)

The CLI can now run a real libp2p node and propagate gene announcements across a LAN — the first runnable step toward a decentralized gene network.

5 min read · [rotifer.hashnode.dev](https://rotifer.hashnode.dev/rotifer-v0-9-0-open-mesh-your-first-p2p-gene-node?utm_source=hashnode&utm_medium=feed)

[Alex Chernysh](https://hashnode.com/@alex-chernysh) · [May 11](https://hashnode.com/posts/1101-through-1106-the-shipped-things/6a01d63cc3a27807b77a8dd5)

### [1.10.1 through 1.10.6: the shipped things](https://bernstein.hashnode.dev/1101-through-1106-the-shipped-things?utm_source=hashnode&utm_medium=feed)

The v1.10.0 post covered the regulated-deployment work. The five point releases since are not headline-shaped. They are the things people kept asking for in issues and the things that were quietly broken once we tried to use the orchestrator on a rea...

6 min read · [bernstein.hashnode.dev](https://bernstein.hashnode.dev/1101-through-1106-the-shipped-things?utm_source=hashnode&utm_medium=feed)

[edekobifrank](https://hashnode.com/@seoguard) · [May 8](https://hashnode.com/posts/seoguard-rules-update-v121/69fe539ac589c5b535ec5f17)

### [SEOGuard Rules Update v1.2.1](https://seoguard.hashnode.dev/seoguard-rules-update-v121?utm_source=hashnode&utm_medium=feed)

SEOGuard rule engine updated to version 1.2.1.

5 min read · [seoguard.hashnode.dev](https://seoguard.hashnode.dev/seoguard-rules-update-v121?utm_source=hashnode&utm_medium=feed)

[dev](https://hashnode.com/@rotiferdev) · [Apr 21](https://hashnode.com/posts/rotifer-v0-8-6-four-cli-fixes-and-installing-no-longer-needs-rust/6ae83c3fd821fee040ed4632)

### [Rotifer v0.8.6: Four CLI fixes, and installing no longer needs Rust](https://rotifer.hashnode.dev/rotifer-v0-8-6-four-cli-fixes-and-installing-no-longer-needs-rust?utm_source=hashnode&utm_medium=feed)

Fixes for async gene crashes, a stale compile cache, native-path failures, and premature fuel exhaustion. Prebuilt native binaries now ship through npm, so installing no longer needs a local Rust toolchain.

2 min read · [rotifer.hashnode.dev](https://rotifer.hashnode.dev/rotifer-v0-8-6-four-cli-fixes-and-installing-no-longer-needs-rust?utm_source=hashnode&utm_medium=feed)
