[PAN-11212] release/2.9.0 fix: Update CHANGELOG.md

[DanielStevenLewis]

Update CHANGELOG.md to reflect the changes in #124

[qodo-code-review]

ⓘ You are approaching your monthly quota for Qodo. Upgrade your plan

Review Summary by Qodo

Add CHANGELOG entry for version 2.9.0 release

📝 Documentation

Walkthroughs

Description

• Add version 2.9.0 release notes to CHANGELOG
• Document bug fixes for npm audit and dependency migration
• Switch from request to axios library documented

Diagram

flowchart LR
  A["CHANGELOG.md"] -- "Add v2.9.0 entry" --> B["Release notes with bug fixes"]
  B -- "npm audit fix" --> C["Dependency updates"]
  B -- "request to axios" --> C

Loading

File Changes

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

Add v2.9.0 release notes and bug fixes

• Added new version 2.9.0 release entry dated 2026-04-10
• Documented bug fixes section with two items
• Noted npm audit production pass fix
• Documented migration from request to axios library

CHANGELOG.md

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (2)   📘 Rule violations (0)   📎 Requirement gaps (0)   🎨 UX Issues (0)

🐞\ ≡ Correctness (1) ⚙ Maintainability (1)

1. Version mismatch 🐞 ≡

Description

CHANGELOG.md declares a 2.9.0 release, but package.json and package-lock.json still declare version
2.8.0, which can result in publishing 2.8.0 while advertising 2.9.0 release notes. This breaks
release/version integrity and can confuse consumers and automation that relies on package.json’s
version.

Code

CHANGELOG.md[5]

+## [2.9.0](https://github.com/rewardops/rewardops-sdk-node/pull/124) (2026-04-10)

Evidence

The PR introduces a 2.9.0 release header in CHANGELOG.md, but the repository’s declared package
version remains 2.8.0 in both package.json and package-lock.json, creating an objective
inconsistency between release notes and publishable version metadata.

CHANGELOG.md[5-12]
package.json[1-6]
package-lock.json[1-6]

Agent prompt

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

### Issue description
CHANGELOG.md announces a `2.9.0` release, but `package.json` and `package-lock.json` still declare `2.8.0`.

### Issue Context
If this branch is used to publish, the published package version would still be `2.8.0` while the changelog suggests `2.9.0`.

### Fix Focus Areas
- CHANGELOG.md[5-12]
- package.json[1-6]
- package-lock.json[1-6]

### Suggested fix
Either:
1) Bump `version` in `package.json` and `package-lock.json` to `2.9.0` (if this PR represents the 2.9.0 release), or
2) If this is only documenting upcoming changes, rename the section to an "Unreleased" section (or otherwise avoid claiming `2.9.0`) until the actual release bump is performed.

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

---

2. Changelog links to PR 🐞 ⚙

Description

The 2.9.0 changelog header links to a pull request URL instead of a tag-to-tag compare URL, unlike
the other release entries. This makes the changelog inconsistent and less useful for navigating
changes between releases.

Code

CHANGELOG.md[R5-12]

+## [2.9.0](https://github.com/rewardops/rewardops-sdk-node/pull/124) (2026-04-10)
+
+### Bug Fixes
+
+- get `npm audit --production` to pass
+- switch from using `request` to using `axios`, as part of getting `npm audit --production` to pass
+
## [2.8.0](https://github.com/rewardops/rewardops-sdk-node/compare/v2.7.3...v2.8.0) (2024-06-05)

Evidence

The newly added 2.9.0 entry links to /pull/124, while adjacent releases (e.g., 2.8.0) use the
/compare/vX...vY format, indicating the established convention in this changelog.

CHANGELOG.md[5-12]

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 `2.9.0` changelog heading links to a PR (`/pull/124`) rather than a standard GitHub compare link used elsewhere in this changelog.

### Issue Context
Other releases (e.g., `2.8.0`) link to `.../compare/v<prev>...v<next>`, which is typically what release tooling and readers expect.

### Fix Focus Areas
- CHANGELOG.md[5-12]

### Suggested fix
Update the `2.9.0` heading link to a compare URL consistent with other entries, e.g.:
`https://github.com/rewardops/rewardops-sdk-node/compare/v2.8.0...v2.9.0`

Optionally add commit/PR references in the bullet items to match the style used in other sections.

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

---

ⓘ The new review experience is currently in Beta. Learn more

[qodo-code-review]

1. Version mismatch 🐞 Bug ≡ Correctness

CHANGELOG.md declares a 2.9.0 release, but package.json and package-lock.json still declare version
2.8.0, which can result in publishing 2.8.0 while advertising 2.9.0 release notes. This breaks
release/version integrity and can confuse consumers and automation that relies on package.json’s
version.

Agent Prompt

### Issue description
CHANGELOG.md announces a `2.9.0` release, but `package.json` and `package-lock.json` still declare `2.8.0`.

### Issue Context
If this branch is used to publish, the published package version would still be `2.8.0` while the changelog suggests `2.9.0`.

### Fix Focus Areas
- CHANGELOG.md[5-12]
- package.json[1-6]
- package-lock.json[1-6]

### Suggested fix
Either:
1) Bump `version` in `package.json` and `package-lock.json` to `2.9.0` (if this PR represents the 2.9.0 release), or
2) If this is only documenting upcoming changes, rename the section to an "Unreleased" section (or otherwise avoid claiming `2.9.0`) until the actual release bump is performed.

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