Update CHANGELOG.md for version 1.0.3

[HackingRepo]

No description provided.

[qodo-code-review]

Review Summary by Qodo

Add CHANGELOG entry for version 1.0.3 release

📝 Documentation

Walkthroughs

Description

• Add version 1.0.3 release notes to CHANGELOG
• Document security vulnerability fix GHSA-8p33-q827-ghj5
• Include build configuration and documentation fixes

Diagram

flowchart LR
  A["Version 1.0.3 Release"] --> B["Security Updates"]
  A --> C["Build & Documentation Fixes"]
  B --> D["Fix GHSA-8p33-q827-ghj5"]
  C --> E["tsconfig.json fix"]
  C --> F["README.md IPv6 claim fix"]

Loading

File Changes

1. CHANGELOG.md 📝 Documentation +10/-0

Add version 1.0.3 release notes

• Added version 1.0.3 release section with security and other changes
• Documented security vulnerability fix GHSA-8p33-q827-ghj5
• Added notes about tsconfig.json build fix and README.md IPv6 documentation correction

CHANGELOG.md

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0)

1. Inconsistent security heading 🐞 Bug ⚙ Maintainability

Description

The 1.0.3 entry uses a plain text label "⚠️ Security Updates:" instead of a Markdown heading, while
the same entry uses a proper heading for "Other Changes", making the section structure inconsistent
and harder to scan.

Code

CHANGELOG.md[R18-21]

+⚠️ Security Updates:
+- Fix GHSA-8p33-q827-ghj5 vuln
+
+### Other Changes

Evidence

Earlier versions (1.0.1, 1.0.2) use a consistent pattern of "## <version>" followed by bullet
points. In 1.0.3, "Other Changes" is a proper heading ("###"), but "Security Updates" is not,
creating mixed formatting within the same release entry.

CHANGELOG.md[3-14]
CHANGELOG.md[16-23]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
In `CHANGELOG.md`, the 1.0.3 entry uses `⚠️ Security Updates:` as plain text rather than a Markdown heading, while `Other Changes` is a heading. This makes the release entry formatting inconsistent.

### Issue Context
Earlier entries (1.0.1/1.0.2) use a consistent structure of a version heading followed by bullet points.

### Fix Focus Areas
- CHANGELOG.md[16-23]

### Suggested change
Change `⚠️ Security Updates:` to a proper heading (e.g., `### Security Updates`) and keep the bullets under it (optionally include the ⚠️ in the heading if desired).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Changelog grammar typo 🐞 Bug ≡ Correctness

Description

The 1.0.3 changelog line "to allow build to successed" is grammatically incorrect, reducing clarity
of the release notes.

Code

CHANGELOG.md[22]

+- That affects only build from source, fixed tsconfig.json, to allow build to successed

Evidence

The added 1.0.3 bullet contains the phrase "to allow build to successed", where "successed" is not
correct English; this should be corrected to avoid confusing readers.

CHANGELOG.md[21-23]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The 1.0.3 changelog contains a grammar error: `to allow build to successed`.

### Issue Context
This is user-facing release documentation; typos reduce clarity and professionalism.

### Fix Focus Areas
- CHANGELOG.md[22-22]

### Suggested change
Replace with something like:
- `... to allow builds to succeed` (or `... to allow the build to succeed`).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[codacy-production]

Not up to standards ⛔

🔴 Issues 3 minor

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

Results:
3 new issues

Category	Results
CodeStyle	3 minor

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.}