Skip to content

Version bumped to v4.0.3 to keep numbering aligned with eXeLearning. #72

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eXeLearningProject merged 1 commit into from
Aug 6, 2026
Merged

Version bumped to v4.0.3 to keep numbering aligned with eXeLearning. #72

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 13 additions & 2 deletions .agents/skills/changelog/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,10 +78,10 @@ Follow the **exact style** of the existing changelog entries in `CHANGELOG.md`.

### Style rules

* **One sentence per bullet.** Start with a capital letter; no trailing full stop.
* **One sentence per bullet.** Start with a capital letter and end with a full stop.
* Describe the **outcome for users**, not the implementation.

* ✅ `Sort iDevice: exercises with identical cards are now correctly validated`
* ✅ `Sort iDevice: exercises with identical cards are now correctly validated.`
* ❌ `Fixed a bug in the validation logic of SortIdevice.js`
* Use component prefixes only when they improve clarity and match the style already used in the changelog (e.g. `TinyMCE:`, `File Manager:`).
* Avoid technical jargon unless it is already common in the existing changelog (e.g. `blob:`, `asset://`, `SCORM`).
Expand All @@ -96,6 +96,17 @@ Follow the **exact style** of the existing changelog entries in `CHANGELOG.md`.
* Merge commits.
* Version-bump-only PRs.
* Purely internal changes (CI, tests, linting, formatting) unless they have a significant user or developer impact.
* Documentation-only changes that are not addressed to end users (contributor guides, issue-tracker links, README maintenance notes).

### Releases with no user-facing changes

If, after applying the rules above, no entry remains, do **not** publish an empty section and do **not** pad it with internal changes. Use this single bullet instead:

```markdown
- Maintenance release with no functional changes: version bumped to keep numbering aligned with eXeLearning for consistency across related projects.
```

Also tell the user which PRs were discarded and why, so they can confirm the release really has no user-visible content.

---

Expand Down
6 changes: 6 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,11 @@
# CHANGELOG

## v4.0.3 – 2026-08-06

- Maintenance release with no functional changes: version bumped to keep numbering aligned with eXeLearning for consistency across related projects.

---

## v4.0.2 – 2026-07-07

- Allow saving the plugin settings page without requiring an optional package template file.
Expand Down
Loading