Automate updating Dev Proxy Homebrew formulas for stable and beta releases.
Install
mkdir -p .claude/skills/update-release && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10698" && unzip -o skill.zip -d .claude/skills/update-release && rm skill.zipInstalls to .claude/skills/update-release
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
This skill should be used when the user asks to "update the beta release", "update the stable release", "bump dev-proxy", "bump dev-proxy-beta", "update formula", "get latest release", "get latest pre-release", or needs to update the Homebrew formula with a new Dev Proxy version.Key capabilities
- →Update beta and stable releases
- →Calculate SHA256 checksums
- →Update Homebrew formula files
- →Determine latest release versions
How it works
The skill identifies the latest release, calculates platform-specific SHA256 checksums, and updates the corresponding Homebrew formula file.
Inputs & outputs
When to use update-release
- →Update beta release
- →Bump stable release version
- →Calculate formula SHA256
About this skill
Update Dev Proxy Homebrew Formula
Update the Homebrew formula with a new Dev Proxy release from the GitHub repository.
Determine Release Type
Based on the user's request, determine which formula to update:
| User mentions | Formula file | Release type |
|---|---|---|
| beta, pre-release | Formula/dev-proxy-beta.rb | Pre-release (e.g., vX.Y.Z-beta.N) |
| stable, latest, (unspecified) | Formula/dev-proxy.rb | Latest stable (e.g., vX.Y.Z) |
Workflow
Step 1: Check Current Version
Read the appropriate formula file to identify the current proxyVersion value.
Step 2: Find Target Release
Fetch the GitHub releases page:
https://github.com/dotnet/dev-proxy/releases
- Beta: Find the most recent release marked "Pre-release"
- Stable: Find the most recent release marked "Latest" (not pre-release)
Step 3: Calculate SHA256 Checksums
Download each platform's zip file and calculate the SHA256 checksum.
macOS (osx-x64):
curl -sL "https://github.com/dotnet/dev-proxy/releases/download/v{VERSION}/dev-proxy-osx-x64-v{VERSION}.zip" | shasum -a 256
Linux (linux-x64):
curl -sL "https://github.com/dotnet/dev-proxy/releases/download/v{VERSION}/dev-proxy-linux-x64-v{VERSION}.zip" | shasum -a 256
Replace {VERSION} with the version number (e.g., 2.1.0-beta.4 or 2.0.0).
Step 4: Update the Formula
Update the formula file with:
- New
proxyVersionvalue (without thevprefix) - New
proxyShafor Linux - New
proxyShafor macOS
Formula structure (both files follow the same pattern):
class DevProxy < Formula # or DevProxyBeta
proxyVersion = "{VERSION}"
if OS.linux?
proxyArch = "linux-x64"
proxySha = "{LINUX_SHA256}"
else
proxyArch = "osx-x64"
proxySha = "{OSX_SHA256}"
end
# ... rest of formula
end
Key Differences Between Formulas
| Aspect | Stable | Beta |
|---|---|---|
| File | Formula/dev-proxy.rb | Formula/dev-proxy-beta.rb |
| Class | DevProxy | DevProxyBeta |
| Binary | devproxy | devproxy-beta |
| Livecheck | strategy :github_latest | regex(/^v(.*)$/i) |
Important Notes
- The version in the formula should NOT include the
vprefix - Each platform has a different SHA256 checksum
- Run the SHA256 commands sequentially (not in parallel) to avoid terminal conflicts
- The download URL includes the
vprefix in the tag name
When not to use it
- →Non-Dev Proxy projects
Prerequisites
Limitations
- →Requires manual SHA256 calculation
- →Dev Proxy specific
How it compares
It automates the specific, multi-step process of updating Dev Proxy Homebrew formulas, including checksum calculation and version management.
Compared to similar skills
update-release side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| update-release (this skill) | 0 | 6mo | Review | Intermediate |
| unity-editor-toolkit | 10 | 6mo | Review | Advanced |
| workflow | 4 | 2mo | Review | Intermediate |
| setup-build-tools | 2 | 6mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by dotnet
View all by dotnet →You might also like
unity-editor-toolkit
Dev-GOM
Automate and control Unity Editor with 500+ commands, real-time WebSocket communication, and SQLite integration for efficient game development.
workflow
vercel
Creates durable, resumable workflows using Vercel's Workflow DevKit. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow devkit", or step-based orchestration.
setup-build-tools
aaddrick
Install build and extraction tools needed for building Claude Desktop Debian packages
macos-spm-app-packaging
Dimillian
Scaffold, build, and package SwiftPM-based macOS apps without an Xcode project. Use when you need a from-scratch macOS app layout, SwiftPM targets/resources, a custom .app bundle assembly script, or signing/notarization/appcast steps outside Xcode.
railway-templates
davila7
Search and deploy services from Railway's template marketplace. Use when user wants to add a service from a template, find templates for a specific use case, or deploy tools like Ghost, Strapi, n8n, Minio, Uptime Kuma, etc. For databases (Postgres, Redis, MySQL, MongoDB), prefer the railway-database skill.
pinme
glitternetwork
This skill should be used when the user asks to "deploy", "upload", "publish", or "pin" any files, folders, frontend projects, or static websites to IPFS. Also activates when user mentions "pinme", "IPFS", or wants to share files via decentralized storage.