Repository navigation
v2.0.9
Changes
- fix(deps): ⬆️ update dependency @haskou/value-objects to ^7.1.0
Release details
- npm: https://www.npmjs.com/package/@haskou/ddd-kernel/v/2.0.9
- Pull request: #67
- Source branch:
renovate/non-major-runtime-dependencies - Version bump:
patch
Pull request notes
This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| @haskou/value-objects (source) | ^7.0.2 → ^7.1.0 |
Release Notes
haskou/value-objects (@haskou/value-objects)
v7.1.0
Changes
- feat(docs): ✨ Explain value objects through practical examples
Release details
- npm: https://www.npmjs.com/package/@haskou/value-objects/v/7.1.0
- Pull request: #76
- Source branch:
feat/library-discovery - Version bump:
minor
Pull request notes
Rework the README around the problems value objects solve: repeated primitive validation, domain invariants, and missing values. Add a custom Username example, explain NullObject behavior and assertions, and make installation, API discovery and contribution links easier to find. Add the weekly npm downloads badge.
The Username example preserves NullObject construction, and the Email explanation distinguishes validated values from absence.
Validation: executed the README's Username example against the built library with valid, invalid, null and undefined inputs; all checks pass. git diff --check passes. Only README.md changes.
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.
Configuration
📅 Schedule: (in timezone Europe/Madrid)
- Branch creation
- At any time (no schedule defined)
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.