---
title: "Arcapush v0.5.0 Release Notes | What's New"
url: https://arcapush.com/blog/introducing-arcapush-v0-5-0
description: "Arcapush Web v0.5.0 and CLI v0.3.0: a redesigned site, media on Cloudflare R2, ship logs, Weekly Shipped, weekly stats emails, a published quality bar, new MCP tools and an open CC BY 4.0 registry."
---

Product Updates · 11 min read

# Introducing Arcapush 0.5.0: Ship Logs, Weekly Shipped, CLI 0.3.0 and an Open Registry

Arcapush Web v0.5.0 and CLI v0.3.0: a redesigned site, media on Cloudflare R2, ship logs, Weekly Shipped, weekly stats emails, a published quality bar, new MCP tools and an open CC BY 4.0 registry.

![](/authors/mojeeb-titilayo.jpg)

[Mojeeb Titilayo](https://mojeeb.xyz)

Published November 17, 2026

Share[X](https://twitter.com/intent/tweet?text=Introducing%20Arcapush%200.5.0%3A%20Ship%20Logs%2C%20Weekly%20Shipped%2C%20CLI%200.3.0%20and%20an%20Open%20Registry%20%E2%80%94%20via%20%40arcapush%0Ahttps%3A%2F%2Farcapush.com%2Fblog%2Fintroducing-arcapush-v0-5-0)[LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Farcapush.com%2Fblog%2Fintroducing-arcapush-v0-5-0)

![Cover artwork for “Introducing Arcapush 0.5.0: Ship Logs, Weekly Shipped, CLI 0.3.0 and an Open Registry”](/blog/covers/introducing-arcapush-v0-5-0.jpg)

A launch gets one day of attention. A build needs a record that keeps working after that day is over.

Version 0.4.0 gave Arcapush a new face. Version 0.5.0 is about what happens after a build is listed: owners can post what they shipped, people can follow the builds they care about, a weekly board ranks real activity under a published rule, and every builder gets a short email about the traffic their listings earned.

It also ships CLI v0.3.0, two new tools for AI assistants over MCP, and something we have wanted to do since the start: the registry is now open data, in its own public repository.

This article is the record of what changed, how it was made, what broke along the way and what comes next.

## Release at a glance

- **Version:** Web v0.5.0, the current version of the Arcapush web application
- **Version introduced:** 16 November 2026
- **Shipping alongside:** CLI v0.3.0, published to npm on 17 November 2026
- **Open registry:** [github.com/mojeebdev/arcapush-registry](https://github.com/mojeebdev/arcapush-registry), licensed CC BY 4.0
- **Running on:** Cloudflare Workers, with listing media on Cloudflare R2
- **Public listings on 17 November 2026:** 486, being 479 products, 5 AI agents and 2 hackathon builds

For comparison, the 0.4.0 article counted 332 public records on 17 October 2026.

## Changelog summary

**Design**

- A new type system: Libre Caslon Display for headlines, Switzer for the interface and Commit Mono for numbers
- A redesigned homepage, registry pages, listing pages, pricing page, builder dashboard and submit flow
- Simpler navigation: Products, Agents, Hackathons and Stories, then Pricing, Sign in and Submit

**Listings and media**

- A listing's media is a logo, up to four screenshots and one YouTube demo video
- Images are stored on Cloudflare R2 and served from media.arcapush.com
- The website shrinks large images before uploading them
- Structured pricing: whether a build has a free tier, what its limit is and where paid plans start
- An "Arcapush's note" line, written by an editor, on featured listings

**After launch day**

- Ship log: dated public updates on a listing, from the dashboard, the CLI or an AI assistant
- Follow a listing or a builder, with at most one digest email a day
- Owner notifications: a batched email when someone else upvotes or comments
- Weekly Shipped: a Monday-to-Sunday board ranked by a published rule
- A weekly stats email with each build's views, click-throughs and top referrers
- A verified-builder card for builders who connect GitHub, and a "Verified builders" filter in the registry

**Trust and quality**

- A published quality bar, with an archive for listings that stop meeting it
- Temporary and disposable email addresses can no longer sign up, subscribe, vote or review
- Paid placements never count towards Weekly Shipped

**For builders and agents**

- Boost and Launch can be bought from the dashboard in USDC on Base
- A media kit on /pricing that reports results only when there are enough campaigns to report
- /perks, a page for credits and discounts for builders
- Category pages rebuilt as A to Z indexes, and /llms.txt generated from live listings
- CLI v0.3.0 with `arcapush ship`, and new MCP tools for ship-log updates and Boost

## How to read the dates in this article

The version constant changed to `0.5.0` on 16 November 2026\. Some of what is described here landed in the week before that, and the after-launch-day features landed on 17 November.

The work began on 10 November with the homepage fixes, payments and the new media model. The redesign followed from 14 November, and the after-launch-day features landed in one long day on 17 November. Where it matters, this article says which came when.

## The creative process

We did not start with a feature list. We started with a question: what does a builder need on day two?

The answer shaped five phases, each with a written gate that had to pass before the next one started.

**Phase 0 fixed trust problems on the homepage.** The page could state two different starting prices side by side, some sections spent their slots on items they never showed, and vote counts loaded with a placeholder. Prices now come from one sentence used everywhere, each section draws from its own type, and vote counts arrive with the page and appear only from three upward.

**Phase 1 was money.** Owners got self-serve Boost and Launch, and a single rule: a campaign becomes paid only from a confirmed payment, never from an admin button.

**Phase 2 was media.** We narrowed what a listing carries to the things people actually look at: a logo, screenshots and a short demo video.

**Phase 3 was design.** We collected ten design references, mapped each one to a page, and redesigned those pages one at a time against them.

**Phase 4 was distribution.** Fourteen items, delivered in six blocks, all aimed at what happens after a build is listed.

Two rules held throughout. First, nothing on the site shows a number we cannot back: empty states say they are empty, and nothing is estimated or rounded up. Second, database changes are numbered SQL files with a dry run, a rollback and a verification step, and they are applied by hand, one at a time.

Most of the code was written in pair sessions with Claude Code, with each phase reviewed before it merged.

## A new look, again

The 0.4.0 palette stayed. The type and the layouts changed.

Headlines are set in Libre Caslon Display, a high-contrast display serif. The interface uses Switzer, and numbers use Commit Mono, so counts and dates line up and read as data.

The homepage, the registry pages for products, agents and hackathon builds, the listing pages, the pricing page, the builder dashboard and the submit flow were all redesigned. The registry pages now lead with one large search field, type tabs and a results count.

The dashboard shows when people view your builds, by weekday and by time of day. Submitting can start from your product's URL, which pre-fills what we can read from the page.

## Listings built around what people look at

A listing's media is now a logo, up to four screenshots and one YouTube demo video. Detail pages open with the product and its screenshots rather than a banner.

Images moved from Supabase Storage to Cloudflare R2 and are served from media.arcapush.com. Large images are shrunk in the browser before upload, so pages load faster and big phone photos are accepted.

Listings can now say whether they have a free tier, what its limit is and where paid plans start. One parser serves the website, the CLI and MCP. When an owner has not said, the page says nothing rather than implying there is no free tier. The registry gained a "Free to start" filter.

Editors can add one line to a listing, labelled "Arcapush's note", which appears on featured cards and the detail page.

## After launch day

This is the heart of 0.5.0.

### Ship log

Owners can post short, dated updates to a listing's public ship log: up to 500 characters with an optional link. Posts can come from the dashboard, from the terminal with `arcapush ship`, or from an AI assistant through MCP, where the assistant prepares the post and a person approves it.

Updates appear on the listing page and in a "Recently shipped" rail on the homepage. When there is nothing to show, neither appears.

### Follow, without follower counts

You can follow a listing or a builder. Followers get at most one digest email a day. There are no follower counts anywhere on the site, on purpose.

Owners get a batched email when other people upvote or comment on their listings. Their own activity never triggers one.

### Weekly Shipped

[Weekly Shipped](/weekly-shipped) is a board for each week, Monday to Sunday in UTC. The rule is published on the page, taken from the same constants the ranking uses:

- 3 points for each upvote from a verified account
- 2 points for each ship-log post, counting at most 3
- 1 point for each distinct click-through session, counting at most 25

Paid placements never count, and neither do an owner's own upvotes and clicks. The first board is the week of 16 to 22 November 2026\. Each finished week is frozen once and never rewritten.

### A weekly stats email

Every Monday, builders get one email with last week's listing views, click-throughs and top referrers for each build, counted the way the dashboard counts them. A builder whose listings had no traffic gets no email.

### The GitHub builder pass

Builders who connect GitHub get a verified-builder card on their profile, with their GitHub link, their first Genesis number, their builds and their ship-log posts. The registry has a "Verified builders" filter.

## Quality, in public

The rules for staying in the registry are now published on the [documentation page](/docs#quality-bar), and reviewers see them on every submission.

Each listing's main link is checked about once a week. A listing whose link has been dead for 30 days, or one older than 90 days with no screenshot, no ship-log post and no click-through in 90 days, gets a warning email. It is archived no sooner than seven days later, and restored as soon as it meets the bar again.

Archived listings leave the homepage and directory lists and appear in the registry's Archive view. Their pages, sitemap entries and Genesis records stay.

Temporary and disposable email addresses can no longer create an account, subscribe, vote or review.

## Pricing, payments and the media kit

Boost costs $29 for seven days and Launch costs $79\. Both can be bought from the dashboard in USDC on Base, through Coinbase's x402 facilitator. Card checkout is not available yet.

Pro is listed at $12 a month or $99 a year, and is marked as coming soon. It is not on sale. Its features are built and switch on when Pro goes on sale: a supporter badge, analytics for each ship-log update, priority review, and one Boost credit for each billing period. The badge is labelled as support, never as verification.

The [pricing page](/pricing) has a media kit. It reports average results per placement type from completed campaigns, with paid and organic traffic counted separately and figures rounded down. Until there are at least three completed campaigns, it shows a sample report layout with no numbers.

</perks> is a new page for credits and discounts for builders. It shows only published, unexpired perks, and stays out of search until it lists one.

## Category pages and llms.txt

Category pages are now server-rendered A to Z indexes, with a jump bar and an anchor for every letter and every listing.

</llms.txt> and /llms-full.txt are generated from approved, visible listings, so AI systems reading the site get the current registry rather than a stale summary.

## CLI v0.3.0 and MCP

CLI v0.3.0 is on npm:

```bash
npm install -g @blindspotlab/arcapush@latest

```

**`arcapush ship "…"`** posts an update to the ship log of a published listing you own. It uses the listing linked in `arcapush.json` or `--listing TYPE:ID`, validates on the server first, shows you the exact post and asks before posting. `--dry-run` validates without posting, and `--yes` and `--json` work as they do for `submit`.

**The hosted MCP service** at `https://mcp.arcapush.com/mcp` can now be reached from the CLI through an OAuth-authorised bridge, configured by URL. The local project tools moved under `arcapush mcp --local`, so existing configurations need updating before upgrading.

**Two new MCP tools:**

- `arcapush_ship_update` prepares a ship-log post, shows the person the exact text and posts only after they approve it.
- `arcapush_boost` lists the listings an account can boost, prepares the exact purchase with its price and terms, and pays in USDC with x402 only after the person explicitly approves that purchase.

Submissions over MCP and the CLI also accept the new structured pricing fields.

## The open registry

The registry now has its own public repository: [mojeebdev/arcapush-registry](https://github.com/mojeebdev/arcapush-registry).

Its first generation lists 486 builds across 25 categories, one markdown file per category, each entry with its name, tagline, free-tier line and Arcapush link. The data is licensed CC BY 4.0, with a request to credit Arcapush.

The repository is generated, not hand-edited. Only approved, visible listings that are not archived are included, and only public fields are read. The generator refuses to write any output that contains an email address. A GitHub Action regenerates it every Sunday at 23:17 UTC and opens a pull request for review rather than pushing directly. The generator connects through a dedicated read-only database role that can see public columns of public listings and nothing else.

The repository also explains how to contribute and publishes the same quality bar the site uses.

## Bugs fixed and challenges

Not everything went to plan. These are the ones worth recording.

**Our database provider restricted the account.** Every listing view downloaded logos from Supabase Storage, and that egress went over the plan's limit. We showed a service notice, moved all media to Cloudflare R2, where serving it has no egress charge, and removed the notice once the disruption was over.

**The media migration script was missing.** The command to copy media to R2 pointed at a script that had never been committed, because an ignore rule excluded it. It was rewritten: a dry run by default, and the database rewrite is one transaction that rolls back if any old storage link remains.

**Images were served exactly as uploaded.** A 40-pixel logo could download a multi-megabyte file. Images are now shrunk in the browser before upload.

**Unpaid USDC checkouts could lock builders out.** An abandoned checkout counted towards the open-checkout limit forever. Unpaid checkouts are now cancelled after an hour, and a payment signed after that is refused before it settles.

**The card provider we planned around did not accept paid placements.** That is why Boost and Launch are sold in USDC first, and why the site only offers payment methods that are actually configured.

**Prisma 7 changed how the database client is built.** The registry generator failed on its first run because the new client needs an explicit database adapter. It was fixed the same day.

**A newer database driver started verifying certificates more strictly.** Connection settings that had worked before were now refused. The registry generator now sets its TLS options explicitly.

**The migration history and the database had drifted.** Some earlier migrations were applied outside the migration tool, so its automatic deploy would have replayed them over live data. Every 0.5.0 migration was rehearsed as a dry run and applied by hand, one file at a time.

**The navbar drew over the service notice.** Fixed.

## What's next for Arcapush in 2027

Everything in this section is a priority, not a promise. None of it is shipped, and dates are not set.

- **Card payments,** alongside USDC, once a provider that supports paid placements is in place.
- **Pro on sale.** Its features are already built and switch on by themselves.
- **Priority review** at $9, once a paid review queue exists.
- **Faster images,** by serving them at the size each page draws them.
- **A richer open registry,** with more of each listing's public record and a smoother path from a contribution to a reviewed listing.
- **Agents.** We are still exploring better ways to find useful AI agents and work with them, and we would like to hear what you want.

## Built for people who ship

Start with the [Registry](/registry), this week's [Weekly Shipped](/weekly-shipped) board, or AI agents at [agents.arcapush.com](https://agents.arcapush.com).

If you have built something, [submit it](/submit). It is free, from the browser, the terminal or an AI assistant. If your build is already listed, post your first ship-log update.

The CLI and MCP setup is on the [documentation page](/docs). Earlier release notes are at </updates>.

Shipping is half the work. Being found is the other half.

Found this useful? Pass it on.

Share[X](https://twitter.com/intent/tweet?text=Introducing%20Arcapush%200.5.0%3A%20Ship%20Logs%2C%20Weekly%20Shipped%2C%20CLI%200.3.0%20and%20an%20Open%20Registry%20%E2%80%94%20via%20%40arcapush%0Ahttps%3A%2F%2Farcapush.com%2Fblog%2Fintroducing-arcapush-v0-5-0)[LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Farcapush.com%2Fblog%2Fintroducing-arcapush-v0-5-0)

RELATED READING

Product Updates9 min read

### [Introducing Arcapush 0.4.0: A New Look, Better Discovery, and More Ways to Ship](/blog/introducing-arcapush-v0-4-0)

ARCAPUSH

## Good products deserve to be discovered.

Explore products, AI agents and hackathon builds worth your attention — or give your own build a place to be found.

[Explore the Registry](/registry)[Submit a build](/submit)
