release: v0.2.8

[Prashant-Surya]

Description

• update axios package to version 1.13.5

Type of Change

• Improvement (change that would cause existing functionality to not work as expected)

Test Scenarios

 PASS  tests/e2e/project.test.ts (9.321 s)
  End to End Project Test
    ✓ should create and list cycles (145 ms)
    ✓ should create and list modules (131 ms)
    ✓ should create work items with assignees (447 ms)
    ✓ should advanced search work items with query (6235 ms)
    ✓ should advanced search work items with nested filters (105 ms)
    ✓ should create work item relations (113 ms)
    ✓ should create work item with parent relationship (160 ms)
    ✓ should add work items to cycle (196 ms)
    ✓ should add work items to module (146 ms)
    ✓ should remove work item from module (128 ms)
    ✓ should remove work item from cycle (159 ms)

Summary by CodeRabbit

• Chores
  • Version bump to 0.2.8

[coderabbitai]

📝 Walkthrough

Walkthrough

Version number incremented from 0.2.7 to 0.2.8 in package.json. No functional code changes, API modifications, or control flow alterations.

Changes

Cohort / File(s)	Summary
Version Update package.json	Bumped package version from 0.2.7 to 0.2.8.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

🐰 A tiny hop, a number grows,
From point-two-seven, onward it goes!
A version bump, so light and small,
The simplest change of all. 🎉

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'release: v0.2.8' is a generic release label that refers to the version bump shown in the raw summary, but it does not clearly communicate the main functional change which is updating the axios package to version 1.13.5 as stated in the PR objectives.	Consider using a more descriptive title that highlights the key functional change, such as 'chore: update axios to 1.13.5' or 'chore: release v0.2.8 with axios update' to better convey the purpose of the release.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch v0.2.8

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

package.json (1)

42-42: ⚠️ Potential issue | 🟠 Major

Move ts-jest to devDependencies.

ts-jest is a testing tool and should be in devDependencies, not dependencies. Keeping it in dependencies unnecessarily increases the package size for production users who don't need testing utilities.

📦 Proposed fix to move ts-jest to devDependencies

Remove ts-jest from dependencies (line 42) and add it to devDependencies:

   "dependencies": {
-    "axios": "1.13.5",
-    "ts-jest": "^29.4.4"
+    "axios": "1.13.5"
   },
   "devDependencies": {
     "@eslint/js": "^9.38.0",
     "@types/jest": "^29.0.0",
     "@types/node": "^20.0.0",
     "@typescript-eslint/eslint-plugin": "^8.46.2",
     "@typescript-eslint/parser": "^8.46.2",
     "dts-bundle-generator": "^9.5.1",
     "eslint": "9.38.0",
     "eslint-plugin-unused-imports": "^4.3.0",
     "globals": "^16.4.0",
     "jest": "^29.0.0",
     "prettier": "3.6.2",
     "ts-node": "^10.9.0",
+    "ts-jest": "^29.4.4",
     "typescript": "5.9.3",
     "typescript-eslint": "^8.46.2"
   },