Location: c:\temp\printmaster\release.ps1
Usage:
# Patch release (bug fixes)
.\release.ps1 agent patch
# Minor release (new features)
.\release.ps1 agent minor
# Major release (breaking changes)
.\release.ps1 agent major
# Release server or both
.\release.ps1 server patch
.\release.ps1 both patchWhat it does automatically:
- ✅ Checks if working directory is clean
- ✅ Bumps version in VERSION file(s)
- ✅ Runs all tests
- ✅ Builds optimized release binary
- ✅ Commits VERSION change
- ✅ Creates git tag (e.g., v0.2.0)
- ✅ Pushes to GitHub
Flags:
--DryRun- Preview what would happen--SkipTests- Skip test execution--SkipPush- Don't push to GitHub
Access: Press Ctrl+Shift+B or Terminal → Run Task
Build Tasks:
- Build: Agent (Dev) ← Default task
- Build: Server (Dev)
- Build: Both (Dev)
- Build: Clean artifacts
Test Tasks:
- Test: Agent (all)
- Test: Server (all)
Release Tasks:
- Release: Agent Patch/Minor/Major
- Release: Server Patch
- Release: Both Patch
Git Tasks:
- Git: Status
- Git: Commit All
- Git: Push
- Git: Pull
Utility Tasks:
- Kill: PrintMaster processes
- Show Build Log
- Show Version
Access: Press F5 or Run and Debug panel
Agent Debugging:
- Debug: Agent (Default Port) - Port 8080
- Debug: Agent (Port 9090)
- Debug: Agent (Custom Config)
- Run: Agent (No Debug)
Server Debugging:
- Debug: Server (Default Port) - Port 3000
- Debug: Server (Port 8080)
- Run: Server (No Debug)
Test Debugging:
- Debug: Current Test Function
- Debug: All Tests in Package
- Debug: Current File Tests
Compound:
- Debug: Agent + Server Together ← Launches both simultaneously
Location: c:\temp\printmaster\docs\BUILD_WORKFLOW.md
Contents:
- Quick reference for daily development
- Release procedures
- Semantic versioning guide (when to use patch/minor/major)
- VS Code integration examples
- Troubleshooting tips
- Best practices
Now includes .vscode/ tasks and launch configs for team consistency:
.vscode/*
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.jsonThis ensures everyone on the team has the same build/debug experience.
# Build and test
.\build.ps1 agent
.\build.ps1 test-all
# Or use VS Code: Ctrl+Shift+B → "Build: Agent (Dev)"# For bug fixes (0.1.0 → 0.1.1)
.\release.ps1 agent patch
# For new features (0.1.0 → 0.2.0)
.\release.ps1 agent minor
# Or use VS Code: Terminal → Run Task → "Release: Agent Patch"Press F5 → Select "Debug: Agent (Default Port)"
All standard git commands work as usual:
git status
git add -A
git commit -m "message"
git push
git pullThe automation is additive - it doesn't replace git, it just makes releases easier!
Test the release script with a dry run:
.\release.ps1 agent patch -DryRunThis shows you exactly what would happen without actually doing it.
✅ Committed:
- Source code
- Documentation
- Build scripts
- VS Code tasks/launch configs
- VERSION files
❌ Ignored:
- Binaries (*.exe)
- Debug binaries (__debug_bin.exe)
- Logs (logs/)
- Databases (*.db)
- Config files (config.ini, keeps .example)
URL: https://github.com/mstrhakr/printmaster Visibility: Private (will go public at v0.9.0) Current Version: v0.1.0
-
Test the release script:
.\release.ps1 agent patch -DryRun -
Try VS Code tasks:
- Press
Ctrl+Shift+B - Select "Build: Agent (Dev)"
- Press
-
Try debugging:
- Press
F5 - Select "Debug: Agent (Default Port)"
- Press
-
When ready for first real release:
.\release.ps1 agent patch
See docs/BUILD_WORKFLOW.md for complete workflow guide.