docs: update branch references from master to main

- Update README.md CI/CD section to reference main branch
- Update CHANGELOG.md to reference main branch
- Add version 1.4 entry documenting branch migration
- All documentation now consistently references main branch

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

Author: Flossy

CHANGELOG.md

@@ -5,11 +5,18 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.4] - 2026-05-16
+
+### Changed
+- Migrated from `master` to `main` as default branch
+- Updated GitHub Actions workflow to trigger on `main` branch
+- Deleted `master` branch (both local and remote)
+
 ## [1.2] - 2026-05-15
 
 ### Added
 - GitHub Actions CD-CI workflow for automated builds
-- Automatic version bumping on push to master branch
+- Automatic version bumping on push to main branch
 - Deployment pipeline to packagecloud.io (flossware/java/maven2)
 - Automatic git tagging for releases
 - Maven SCM integration for version control operations
@@ -72,6 +79,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Blocked dangerous system directories: `/`, `/bin`, `/boot`, `/dev`, `/etc`, `/lib`, `/lib64`, `/proc`, `/root`, `/sbin`, `/sys`, `/usr`, `/var`, `/home`, `/Users`
 - Windows protected paths: `C:\`, `C:\Windows`, `C:\Program Files`
 
+[1.4]: https://github.com/FlossWare/jsecurity/compare/v1.2...v1.4
 [1.2]: https://github.com/FlossWare/jsecurity/compare/v1.0...v1.2
 [1.0]: https://github.com/FlossWare/jsecurity/compare/v0.1...v1.0
 [0.1.0]: https://github.com/FlossWare/jsecurity/releases/tag/v0.1.0

README.md

@@ -184,7 +184,7 @@ See [LICENSE](LICENSE) for the full license text.
 
 This project uses GitHub Actions for automated builds and deployment:
 
-- **Automated Versioning** - Version automatically increments on push to master (X.Y format)
+- **Automated Versioning** - Version automatically increments on push to main (X.Y format)
 - **Automated Building** - Compiles and packages on every push
 - **Automated Tagging** - Creates git tags for each release
 - **Automated Deployment** - Publishes to packagecloud.io (flossware/java/maven2)