v7.0.3

Changes

• fix(release): 🐛 Synchronize package version after publication

Release details

• npm: https://www.npmjs.com/package/@haskou/value-objects/v/7.0.3
• Pull request: #75
• Source branch: fix/release-version-sync
• Version bump: patch

Pull request notes

The release workflow publishes a bumped package version but restores package.json afterward, leaving the repository at 4.0.1 while npm latest is 7.0.2. Update the manifest to 7.0.2 and synchronize it automatically after the release queue completes.

Synchronization reads npm latest, starts from the current remote branch, changes only package.json, and pushes a dedicated chore(release) commit. Rejected pushes retry from the updated remote without force-pushing; matching versions are a no-op, while registry failures, invalid versions, and downgrades fail explicitly. The sync commit does not match the legacy release baseline marker or create another release.

Validation: nine release-workflow tests pass, including real local Git remotes, idempotency, preservation of newer commits, concurrent push recovery, registry failure, malformed versions and downgrade protection. Package and documentation builds pass; workflow YAML and Bash syntax checks pass. Independent review found no actionable issues.

Review follow-up: reject concurrent package renames after every checkout, and retain the successfully published version if npm latest is temporarily stale. Both cases have regression tests.