Bump version from 1.0.3 to 1.0.5

[HackingRepo]

PR Summary by Qodo

Bump package version to 1.0.5
⚙️ Configuration changes 🕐 Less than 5 minutes

Walkthroughs

User Description

Previously we keeped 1.0.3 in package.json we forget to change it to 1.4.0, now will be changed to 1.5.0 since that a new release

AI Description

• Update the npm package version from 1.0.3 to 1.0.5 for the new release.

High-Level Assessment

The approach is appropriate for a release version bump. Alternatives (e.g., deriving version via git tags or release tooling) are unnecessary for this change’s scope.

File Changes

Other (1)

package.json Bump npm package version to 1.0.5 +1/-1

Bump npm package version to 1.0.5

• Updates the package metadata version field from 1.0.3 to 1.0.5 to reflect the new release.

package.json

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0)

1. Lockfile version mismatch 🐞 Bug ☼ Reliability

Description

package.json is bumped to 1.0.5 but package-lock.json still declares the root package version as
1.0.3. This out-of-sync state can cause npm ci to fail in CI (and for developers) because it
validates lockfile consistency against package.json.

Code

package.json[3]

+  "version": "1.0.5",

Evidence

The repo’s lockfile still declares version 1.0.3, while CI runs npm ci, which performs a clean
install based on package-lock.json and checks it matches package.json. With package.json now
at 1.0.5, the metadata mismatch can break CI installs.

package.json[1-5]
package-lock.json[1-12]
.github/workflows/node.js.yml[24-32]
.github/workflows/snyk-infrastructure.yml[21-33]

Agent prompt

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

### Issue description
`package.json` was updated to version `1.0.5`, but `package-lock.json` still contains `1.0.3` for the root package (`version` at the top-level and under `packages[""]`). CI uses `npm ci`, which expects the lockfile and `package.json` to be in sync.

### Issue Context
This mismatch is introduced by changing only `package.json`'s version.

### Fix
- Update/regenerate `package-lock.json` so the root package version matches `package.json` (typically by running `npm install --package-lock-only` or `npm install`, then committing the updated lockfile).

### Fix Focus Areas
- package.json[1-5]
- package-lock.json[1-12]
- .github/workflows/node.js.yml[24-32]
- .github/workflows/snyk-infrastructure.yml[21-33]

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

---

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
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.}

[qodo-code-review]

1. Lockfile version mismatch 🐞 Bug ☼ Reliability

package.json is bumped to 1.0.5 but package-lock.json still declares the root package version as
1.0.3. This out-of-sync state can cause npm ci to fail in CI (and for developers) because it
validates lockfile consistency against package.json.

Agent Prompt

### Issue description
`package.json` was updated to version `1.0.5`, but `package-lock.json` still contains `1.0.3` for the root package (`version` at the top-level and under `packages[""]`). CI uses `npm ci`, which expects the lockfile and `package.json` to be in sync.

### Issue Context
This mismatch is introduced by changing only `package.json`'s version.

### Fix
- Update/regenerate `package-lock.json` so the root package version matches `package.json` (typically by running `npm install --package-lock-only` or `npm install`, then committing the updated lockfile).

### Fix Focus Areas
- package.json[1-5]
- package-lock.json[1-12]
- .github/workflows/node.js.yml[24-32]
- .github/workflows/snyk-infrastructure.yml[21-33]

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