release-and-publish

Prepare a PlayBridge release by explicitly requested version uprevs, changelog updates, verification, commit, push, and PR creation or update. Use only when the user asks for an uprev, version bump, or release; do not trigger for an ordinary commit, push, or PR request.

Jump to install

Repository: playbridgeapp/playbridge
Last source activity: July 25, 2026 at 16:53
Detected SKILL.md language: English
Stars: 285
Forks: 19

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

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.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/playbridgeapp/playbridge --skill release-and-publish

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

android-adb

Android device control via raw ADB for PlayBridge phone/TV work. Use when discovering devices on the LAN, connecting over Wi-Fi ADB, force-stopping apps, rebuilding and installing FOSS debug APKs with ABI splits, launching apps, screenshots, UI dumps, input, logcat, or ADB troubleshooting.

2026-08-12

playbridge-android

Work across PlayBridge's Android phone, Android TV, and shared Kotlin projects. Use for Kotlin, Compose, GeckoView, Android playback, Gradle, shared KMP, root version-catalog, or Android-specific protocol consumer changes under mobile/android/, tv/android/, shared/, gradle/, or prebuilt/media3/.

2026-08-12

playbridge-rust-core

Work on the PlayBridge Rust casting core, reusable receiver runtime, sender-hosted browser receiver, FFI bindings, and CLI. Use for discovery and protocol sessions, receiver TLS/WSS and SAS pairing, authentication, UniFFI/C/JNI/Dart bindings, command-line sender or receiver behavior, or changes under cast/core/, cast/receiver/, cast/ffi/, browser-receiver-rust/, packages/playbridge_cast_core_dart/, and cli/.

2026-08-10

View all from this repository

Release and publish

Version locations

Project

Version source

Changelog

Android phone

mobile/android/app/build.gradle.kts

mobile/android/CHANGELOG.md

Android TV player

tv/android/player/app/build.gradle.kts

tv/android/CHANGELOG.md

Desktop

desktop/pubspec.yaml and desktop/lib/update/app_version.dart

desktop/CHANGELOG.md

iOS phone

mobile/apple/PlayBridge Phone/PlayBridge Phone.xcodeproj/project.pbxproj

mobile/apple/CHANGELOG.md

Apple TV

tv/apple/PlayBridge TV/PlayBridge TV.xcodeproj/project.pbxproj

tv/apple/CHANGELOG.md

Extension

extension/manifests/chrome.json

extension/CHANGELOG.md

CLI

cli/Cargo.toml

cli/CHANGELOG.md

Stream proxy

stream-proxy-dart/pubspec.yaml

stream-proxy-dart/CHANGELOG.md

For Desktop, keep version: <semver>+<build> and kAppVersion = '<semver>' in lockstep. CI checks this in desktop/test/update_test.dart.

Monorepo release policy (PR checks → draft release-build on uprev → publish): see docs/release.md. CLI is the reference: uprev arms cli_build.yml (draft cli-v*); cli_publish.yml sets draft=false.

Workflow

Inspect git status and the diff against the intended base. Identify affected projects without absorbing unrelated worktree changes.

Changes under shared/ affect both Android phone and TV releases.
Keep Apple versions in their existing unstable 0.x scheme.

Choose the bump requested by the user. If unspecified, use minor for features and patch for fixes/refactors; increment the numeric build/version code once.

Update every affected project's version source and add a concise Keep a Changelog entry dated today.

Stage only task and release-metadata files. Never use git add -A when unrelated changes exist.

Run focused verification for each affected project. For Desktop, always run flutter test test/update_test.dart.

Commit with a Conventional Commit message, push the feature/release branch, and create or update the PR with gh.

Include new versions and verification results in the PR description.

After merge, for CLI: confirm the draft GitHub Release from CLI Release Build, then run CLI Publish when ready (do not treat draft creation as public ship).

Use the environment's configured Git/GitHub authentication. Do not clear or override authentication variables unless the user or environment specifically requires it.