-
Notifications
You must be signed in to change notification settings - Fork 3
Release Process
Bruno Campos edited this page Oct 8, 2025
·
1 revision
Step-by-step guide for creating and publishing ZPL2PDF releases.
- Major (v2.0.0): Breaking changes
- Minor (v2.1.0): New features, backwards compatible
- Patch (v2.0.1): Bug fixes
- All features merged to
main - All tests passing
- Code coverage > 80%
- Documentation updated
-
CHANGELOG.mdupdated - Version bumped in
.csproj - No open critical bugs
<!-- ZPL2PDF.csproj -->
<PropertyGroup>
<Version>2.0.0</Version>
<AssemblyVersion>2.0.0.0</AssemblyVersion>
<FileVersion>2.0.0.0</FileVersion>
</PropertyGroup>## [2.0.0] - 2024-01-15
### Added
- Multi-language support (8 languages)
- Docker deployment
- Clean Architecture refactoring
### Fixed
- Dimension extraction bugs
- Memory leaks in daemon mode
### Changed
- Improved performance by 30%# Windows
.\scripts\build-all-platforms.ps1
# Linux/macOS
./scripts/build-all-platforms.sh# Create annotated tag
git tag -a v2.0.0 -m "Release v2.0.0"
# Push tag to GitHub
git push origin v2.0.0- Go to GitHub Releases
- Click "Draft a new release"
- Select tag
v2.0.0 - Title:
ZPL2PDF v2.0.0 - Description: Copy from
CHANGELOG.md - Upload artifacts from
build/publish/ - Click "Publish release"
# Login to registries
docker login
docker login ghcr.io
# Build and push multi-arch
docker buildx build --platform linux/amd64,linux/arm64 \
-t brunoleocam/zpl2pdf:2.0.0 \
-t brunoleocam/zpl2pdf:latest \
-t ghcr.io/brunoleocam/zpl2pdf:2.0.0 \
-t ghcr.io/brunoleocam/zpl2pdf:latest \
--push .# Update manifests
.\scripts\winget-submit.ps1 -Version "2.0.0" -NoConfirm- Twitter/X
- Reddit (r/dotnet, r/selfhosted)
- GitHub Discussions
- Monitor for critical bugs
- Update documentation site
- Respond to user feedback
- Plan next release
- Build Process - Building artifacts
- Package Formats - Package types
- Distribution Channels - Publishing locations