Run any Skill in Manus with one click

update-bun

Stars62

Forks2

UpdatedMay 18, 2026 at 20:52

Upgrade Bun to the latest version and sync the pinned version across .bun-version, Dockerfile, Dockerfile.production, and @types/bun in package.json. Use when the user asks to "update bun", "upgrade bun", or "bump bun version".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

khromov

khromov/mochi

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	update-bun
description	Upgrade Bun to the latest version and sync the pinned version across .bun-version, Dockerfile, Dockerfile.production, and @types/bun in package.json. Use when the user asks to "update bun", "upgrade bun", or "bump bun version".
user-invocable	true

Update Bun version

This skill upgrades the local Bun install to the latest release and propagates the new version to every place it is pinned in the repo.

Pinned locations

.bun-version — bare semver, no v prefix (e.g. 1.3.12). Also consumed by oven-sh/setup-bun@v2 via bun-version-file: .bun-version in .github/workflows/test.yml, so CI is updated automatically.
Dockerfile line 2 — FROM oven/bun:<version> AS base (no v prefix)
Dockerfile.production line 2 — FROM oven/bun:<version> AS base (no v prefix)
package.json — "@types/bun" dependency, pinned exactly (no ^, no latest)

Steps

Install the latest Bun:

curl -fsSL https://bun.com/install | bash

Get the new version:
```
bun --version
```
Output is a bare semver like 1.3.12. Call this $NEW.
Read .bun-version to get $OLD (e.g. 1.3.11). The file stores a bare semver with no v prefix.
If $NEW == $OLD, report "Bun is already up to date at $NEW" and stop. Do not touch any files.
Otherwise, update the four files using the Edit tool:
- .bun-version: write $NEW (overwrite full content, no v prefix).
- Dockerfile: replace oven/bun:$OLD with oven/bun:$NEW.
- Dockerfile.production: replace oven/bun:$OLD with oven/bun:$NEW.
- package.json: update the @types/bun entry. If the current value is "latest", replace "@types/bun": "latest" with "@types/bun": "$NEW". If it is already a pinned version ("@types/bun": "$OLD"), replace that string with "@types/bun": "$NEW".
Refresh the lockfile and formatting:
```
bun install
bun run format
```
Report the upgrade: Bun $OLD → $NEW and list the four files modified.

Notes

The bun --version output has no v prefix. No file should have a v prefix — .bun-version, the Dockerfile tags, and @types/bun all use bare semver.
Do not run bun upgrade — the curl | bash installer is the canonical path used by this project.
If the shell PATH still points at the old Bun after installing, use the fresh install path printed by the installer (typically ~/.bun/bin/bun) for the bun --version check.

More from this repository

same repository

mochi

khromov/mochi

Use whenever the user asks to build, add, or modify anything in this Mochi app — pages, routes, islands, selective/lazy/server hydration, forms, JSON/WS/SSE endpoints, cookies, caching, or request context. Before writing any framework code, invoke the "mochi" skill to fetch the relevant Mochi docs and demos.

2026-07-1862

add-event

khromov/mochi

Add a new lifecycle event to Mochi's event bus (`packages/mochi/src/events.ts`). Use when the user asks to "add an event", "emit a new event", "create a new mochiEvents emission", or "/add-event <name>". Walks the payload type, the `MochiEventMap` registry, the emission site, public exports, optional logger wiring, tests, and docs.

2026-07-1762

test-validator

khromov/mochi

Mutation-test unit tests to verify they catch real failures. For each test, temporarily breaks the source code it exercises, confirms the test fails, then reverts. Flags mock-only tests and suggests fixes. Use when the user says "validate tests", "test-validator", or wants to check test quality.

2026-07-1762

component-screenshot

khromov/mochi

Take a 16:9 screenshot of a single component via the /shot/:name endpoint (`packages/site/src/shot/`). Use when the user asks to "screenshot a component", "take a component screenshot", "generate an image of <component>", "grab a shot of X for the docs", or "/component-screenshot <component>". Covers registering a new subject, sizing, and driving the browser.

2026-07-1662

commit

khromov/mochi

Stage and commit the current working changes with a short release-please-style commit title. Does not push. Use when the user says "commit", "commit my changes", or "/commit". Optional args list paths to skip (e.g. "/commit ignore IMPROVEMENTS.md").

2026-07-0762

add-extension

khromov/mochi

Add a new hook or filter to Mochi's extension API (`packages/mochi/src/extensions.ts`). Use when the user asks to "add a hook", "add a filter", "create an extension point", or "/add-extension <name>". Walks both halves of the type/runtime kind-map registry and the call-site wiring.

2026-07-0362

name	update-bun
description	Upgrade Bun to the latest version and sync the pinned version across .bun-version, Dockerfile, Dockerfile.production, and @types/bun in package.json. Use when the user asks to "update bun", "upgrade bun", or "bump bun version".
user-invocable	true

Update Bun version

This skill upgrades the local Bun install to the latest release and propagates the new version to every place it is pinned in the repo.

Pinned locations

.bun-version — bare semver, no v prefix (e.g. 1.3.12). Also consumed by oven-sh/setup-bun@v2 via bun-version-file: .bun-version in .github/workflows/test.yml, so CI is updated automatically.
Dockerfile line 2 — FROM oven/bun:<version> AS base (no v prefix)
Dockerfile.production line 2 — FROM oven/bun:<version> AS base (no v prefix)
package.json — "@types/bun" dependency, pinned exactly (no ^, no latest)

Steps

Install the latest Bun:

curl -fsSL https://bun.com/install | bash

Get the new version:
```
bun --version
```
Output is a bare semver like 1.3.12. Call this $NEW.
Read .bun-version to get $OLD (e.g. 1.3.11). The file stores a bare semver with no v prefix.
If $NEW == $OLD, report "Bun is already up to date at $NEW" and stop. Do not touch any files.
Otherwise, update the four files using the Edit tool:
- .bun-version: write $NEW (overwrite full content, no v prefix).
- Dockerfile: replace oven/bun:$OLD with oven/bun:$NEW.
- Dockerfile.production: replace oven/bun:$OLD with oven/bun:$NEW.
- package.json: update the @types/bun entry. If the current value is "latest", replace "@types/bun": "latest" with "@types/bun": "$NEW". If it is already a pinned version ("@types/bun": "$OLD"), replace that string with "@types/bun": "$NEW".
Refresh the lockfile and formatting:
```
bun install
bun run format
```
Report the upgrade: Bun $OLD → $NEW and list the four files modified.

Notes

The bun --version output has no v prefix. No file should have a v prefix — .bun-version, the Dockerfile tags, and @types/bun all use bare semver.
Do not run bun upgrade — the curl | bash installer is the canonical path used by this project.
If the shell PATH still points at the old Bun after installing, use the fresh install path printed by the installer (typically ~/.bun/bin/bun) for the bun --version check.