release

Engineering Community

Skill notes

Phase 1: Pre-checks

Before starting, verify the repository is ready: If there are uncommitted changes, stop and ask the user to resolve them first.

2.1 Get the new version number

Ask the user for the new version number (e.g., 0.12.0). Verify it follows semver format.

2.2 Update version file

Edit src/vorta/_version.py:

2.3 Update translations (optional)

Note: Use command op to bypass shell function issues with 1Password CLI. If this fails (e.g., 1Password not configured), ask user if they want to skip or fix it.

2.4 Update metadata and create commit + tag

Note: make bump-version has a preflight check that requires a clean tree, but we've already edited _version.py. Perform the steps manually instead: Update appdata.xml with new version and today's date: Create commit and tag: Prompt the user for the tag message (brief summary of changes).

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@borgbase · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Pre-checks

Before starting, verify the repository is ready: If there are uncommitted changes, stop and ask the user to resolve them first.

02
Phase 2: Version Bump

Phase 2: Version Bump

03
Phase 3: Push to Upstream

Phase 3: Push to Upstream

04
Phase 4: Wait for CI

Monitor the test workflow: Wait for tests to pass before proceeding. If tests fail, stop and notify the user.

05
Phase 5: Create GitHub Release

Phase 5: Create GitHub Release

06
Phase 6: PyPi Release

Note: Use `command op` to bypass shell function issues with 1Password CLI. This builds the sdist and uploads to PyPi via twine. If `op` fails, provide manual instructions:

07
Phase 7: macOS Builds

Phase 7: macOS Builds

08
Phase 8: Publish Release

After verifying the release looks correct: Provide the release URL to the user.

09
Phase 9: Update GitHub Pages (Appcast)

Update the Sparkle appcast for macOS auto-updates. Note: The gh-pages branch doesn't have pre-commit config, so commits may fail. Handle this: If the commit fails due to pre-commit, complete manually:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.