القائمة
Use when creating a release, bumping the version, tagging a commit, or working with the GitHub Actions release workflow for rs-summarizer.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when selecting a Gemini model, checking rate limits or quotas, configuring the gemini-rust crate, or debugging model name mismatches.
Create new Kiro skills (Agent Skills). Use when asked to create a skill, write a SKILL.md, add a new workflow to .kiro/skills/, or package agent instructions as a reusable skill.
Use when editing or creating Askama HTML templates, adding template variables, fixing compile-time template errors, or working with HTMX attributes in templates.
Use when working with tokio::spawn background tasks, the summarization pipeline, task state transitions, or the mark_error/mark_summary_done pattern.
Use when building, running, linting with clippy, formatting with rustfmt, or running cargo commands for the rs-summarizer project.
Use when updating Cargo dependencies, checking for new crate versions, evaluating semver bumps, or deciding whether to upgrade a specific crate.
| name | release-process |
| description | Use when creating a release, bumping the version, tagging a commit, or working with the GitHub Actions release workflow for rs-summarizer. |
rs-summarizer uses GitHub Actions to automatically build and publish releases for Linux and macOS when a git tag starting with v is pushed.
v0.2.0 to the repository.github/workflows/release.yml workflowrs-summarizer-linux-amd64.tar.gz)rs-summarizer-macos-amd64.tar.gz)rs-summarizer-macos-arm64.tar.gz)static/ directory (CSS, JS) required at runtimeThe release archive contains:
rs-summarizer — the server binarystatic/htmx.min.js — HTMX library for frontend interactivitystatic/pico.min.css — Pico CSS framework for stylingAskama templates and SQLite migrations are compiled into the binary at build time and do not need separate files.
./scripts/release-check.sh
Verifies:
main branchcargo check passescargo clippy passes./scripts/release.sh <version>
# Example:
./scripts/release.sh 0.2.0
This script:
X.Y.Z)Cargo.toml versioncargo check to verify the buildCargo.lockv<version>If you prefer to release manually:
# 1. Update version in Cargo.toml
sed -i 's/^version = ".*"/version = "0.2.0"/' Cargo.toml
# 2. Verify the build
cargo check
cargo test
# 3. Commit
git add Cargo.toml Cargo.lock
git commit -m "Release v0.2.0"
# 4. Tag and push
git tag v0.2.0
git push origin main
git push origin v0.2.0
After pushing a tag, monitor the build at: https://github.com/plops/rs-summarizer/actions
.github/workflows/release.yml — GitHub Actions workflow definitionscripts/release.sh — Automated release scriptscripts/release-check.sh — Pre-release validationCargo.toml — Version is defined hereFollow semantic versioning: