PR #139 wrapped commit-analyzer with path filtering but tried to fix
release-notes-generator with gitRawCommitsOpts: { path: '.' } -- a
no-op because the plugin reads context.commits from semantic-release,
never gitRawCommitsOpts. Result: every skill release body and CHANGELOG
included commits from the entire repo (see slicc-handoff-v1.0.0).
- Add scripts/path-filtered-notes-generator.cjs mirroring the analyzer
wrapper -- filters context.commits via git log -- . before delegating
to the real plugin.
- Wire it into release.config.cjs in place of the bare plugin entry;
drop the dead gitRawCommitsOpts config.
- Regenerate plugins/aem/edge-delivery-services/skills/slicc-handoff/
CHANGELOG.md (skipped by PR #140 because the tag did not exist yet).
All existing CHANGELOG.md files contained commits from the entire repo
since the skill's last tag, making release notes meaningless. This
regenerates each one from scratch using git log filtered to the skill's
own directory, following up on #139 which fixed the root cause for
future releases.
Empty release sections (e.g. 1.0.0) indicate versions bumped solely by
docs/refactor commits, which is correct — the angular preset omits those
types from the CHANGELOG body.
Also adds scripts/regenerate-changelogs.cjs in case a manual re-run is
ever needed.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Use execFileSync with argument array instead of execSync with
interpolated string to avoid shell injection risk
- Log a warning via context.logger when the git fallback is triggered
so failures are diagnosable rather than silently swallowed
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Each skill was including all repo commits in its CHANGELOG and GitHub
release body, and unrelated breaking changes were triggering spurious
major bumps. Fix by path-filtering at both the commit-analysis and
note-generation stages.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Lars Trieloff