DJLS Changelog
Use this for any user-facing change or release-note work.
Rules
- Every user-facing change needs a changelog entry in the same commit or PR.
- Entries go under
[Unreleased]in the appropriate section:AddedChangedDeprecatedRemovedFixedSecurity
- Keep entries short and factual: what changed, not why.
- Use past tense verbs:
Added,Fixed,Removed,Bumped. - Prefix internal-only changes with
**Internal**:and list them after user-facing entries. - Backtick-wrap code identifiers: crate names, types, commands, config keys.
Example
### Fixed
- Fixed `{% load %}` completions for custom template tag libraries.
- **Internal**: Refactored `djls-semantic` validation helpers.