Release 1.4.8

[AnaisPantheor]

Release Preparation: v1.4.8

This is an automated release candidate PR managed by GitHub Actions.
It acts as a staging area for the next release.

Changes in this PR:

Version Bump:
Updates version strings to 1.4.8 across plugin files.

Changelog:
Synchronizes readme.txt and README.md with recent changes.

Automation:
Tagged with automation so the workflow can continue updating this branch as new code hits main.

[AnaisPantheor]

Branches are diverged — will be resolved by this release

main and release have diverged: main is 23 commits ahead and 1 commit behind release. The commit on release that main is missing is:

• cb76681 — Release 1.4.7 (#527)

This happened because the post-release reconciliation step (git rebase release on main) was done through the GitHub UI instead of from the terminal as specified in CONTRIBUTING.md. The GitHub UI merge options (squash/rebase) create new commit hashes, which breaks the shared history between branches.

How this release fixes it

When this release PR is merged into release, it must use a merge commit (not squash or rebase). This will bring main's commits into release and link the two histories back together. If the GitHub UI doesn't offer the merge commit option, merge from the terminal:

git checkout release
git merge release-1.4.8
git push origin release

Then follow the post-release reconciliation steps in CONTRIBUTING.md exactly:

git checkout release
git pull origin release
git checkout main
git rebase release
# Update version numbers, add -dev flag, update changelog
git add -A .
git commit -m "Prepare X.Y.Z-dev"
git checkout -b release-XYZ-dev
git push origin release-XYZ-dev

Create a PR from release-XYZ-dev to main to trigger CI. Wait for all checks to pass. Once approved, push to main from the terminal:

git checkout main && git push origin main

Do not merge the post-release PR through the GitHub UI. The UI will rewrite commit hashes and cause the branches to diverge again. The open PR with passing tests allows the direct push to main.

[codacy-production]

Not up to standards ⛔

🔴 Issues 2 minor

Alerts:
⚠ 2 issues (≤ 0 issues of at least minor severity)

Results:
2 new issues

Category	Results
BestPractice	1 minor
CodeStyle	1 minor

View in Codacy

🟢 Metrics 6 complexity · 0 duplication

Metric	Results
Complexity	6
Duplication	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}