mleku/next.orly.dev

Files

Go / build-and-release (push) Has been cancelled

Details

Add git.mleku.dev remote push to release process (v0.40.1)

- Update release command to push to git.mleku.dev using gitmlekudev SSH key
- Add release process documentation to README.md

Files modified:
- .claude/commands/release.md: Add GIT_SSH_COMMAND push to git.mleku.dev
- README.md: Document release process and SSH key configuration
- pkg/version/version: Bump to v0.40.1

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2025-12-27 18:07:15 +02:00

2.2 KiB

Raw Blame History

Release Command

Review all changes in the repository and create a release with proper commit message, version tag, and push to remotes.

Argument: $ARGUMENTS

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.

Steps to perform:

Read the current version from pkg/version/version
Calculate the new version based on the argument:
- Parse the current version (format: vMAJOR.MINOR.PATCH)
- If patch: increment PATCH by 1
- If minor: increment MINOR by 1, set PATCH to 0
Update the version file (pkg/version/version) with the new version
Rebuild the embedded web UI by running:
```
./scripts/update-embedded-web.sh
```
This ensures the latest web UI changes are included in the release.
Review changes using git status and git diff --stat HEAD
Compose a commit message following this format:
- 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
Stage all changes with git add -A
Create the commit with the composed message
Create a git tag with the new version (e.g., v0.36.0)

Push to remotes (origin, gitea, and git.mleku.dev) with tags:

git push origin main --tags
git push gitea main --tags
GIT_SSH_COMMAND="ssh -i ~/.ssh/gitmlekudev" git push ssh://mleku@git.mleku.dev:2222/mleku/next.orly.dev.git main --tags

Deploy to VPS by running:

ssh 10.0.0.1 'cd ~/src/next.orly.dev && git stash && git pull origin main && export PATH=$PATH:~/go/bin && CGO_ENABLED=0 go build -o ~/.local/bin/next.orly.dev && sudo systemctl restart orly && ~/.local/bin/next.orly.dev version'

Report completion with the new version and commit hash

Important:

Do NOT push to github remote (only origin and gitea)
Always verify the build compiles before committing: CGO_ENABLED=0 go build -o /dev/null ./...
If build fails, fix issues before proceeding

2.2 KiB Raw Blame History

Release Command

Argument: $ARGUMENTS

Steps to perform:

Important:

2.2 KiB

Raw Blame History