Review all changes in the repository and create a release with proper commit message, version tag, and push to remotes.
The argument should be one of:
patch - Bump the patch version (e.g., v0.35.3 -> v0.35.4)minor - Bump the minor version and reset patch to 0 (e.g., v0.35.3 -> v0.36.0)If no argument provided, default to patch.
pkg/version/version - Parse the current version (format: vMAJOR.MINOR.PATCH)
- If patch: increment PATCH by 1
- If minor: increment MINOR by 1, set PATCH to 0
pkg/version/version) with the new version `
./scripts/update-embedded-web.sh
`
This ensures the latest web UI changes are included in the release.
git status and git diff --stat HEAD- First line: 72 chars max, imperative mood summary - Blank line - Bullet points describing each significant change - "Files modified:" section listing affected files - Footer with Claude Code attribution
git add -Av0.36.0) `
git push origin main --tags
`
Build and deploy the unified orly binary - a fully self-contained relay with all components embedded:
- Embedded Badger/Neo4j database
- Embedded ACL engine (follows, managed, curating modes)
- Embedded NIP-77 negentropy sync
- All subcommands (db, acl, relay) for split-mode if needed
Build on remote (faster than uploading cross-compiled binary due to slow local bandwidth):
`bash
ssh relay.orly.dev 'cd ~/src/next.orly.dev && git pull origin main && GOPATH=$HOME CGO_ENABLED=0 ~/go/bin/go build -o ~/.local/bin/orly ./cmd/orly'
ssh root@relay.orly.dev '/usr/sbin/setcap capnetbind_service=+ep /home/mleku/.local/bin/orly && systemctl restart orly'
ssh relay.orly.dev '~/.local/bin/orly version'
`
Note: setcap must be re-applied after each binary rebuild to allow binding to ports 80/443.
This is the recommended binary - just run orly for a complete monolithic relay,
or use subcommands (orly db, orly acl) for split-mode architecture.
CGO_ENABLED=0 go build -o /dev/null ./...