Constrain versions only for demonstrated compatibility needs, using the broadest working range and documenting why.
Preserve lockfile-based reproducibility.
Release history
Maintain only root CHANGELOG.md as internal engineering history.
Do not create or update extension-local changelogs.
At release time, write separate human-readable release notes for Pi extension users.
Focus release notes on features, configuration changes, bug fixes, and required user actions.
Include implementation details only when essential to understanding user impact.
Do not publish the internal changelog as consumer release notes.
# Project guidance
## Dependencies
- Prefer `"*"` dependency ranges to track latest stable releases; fix compatibility promptly.
- Constrain versions only for demonstrated compatibility needs, using the broadest working range and documenting why.
- Preserve lockfile-based reproducibility.
## Release history
- Maintain only root `CHANGELOG.md` as internal engineering history.
- Do not create or update extension-local changelogs.
- At release time, write separate human-readable release notes for Pi extension users.
- Focus release notes on features, configuration changes, bug fixes, and required user actions.
- Include implementation details only when essential to understanding user impact.
- Do not publish the internal changelog as consumer release notes.