feat: bump version

[limitofzero]

Summary by CodeRabbit

• Chores
  • Version updated to 0.29.0

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2745d38c-a316-4f1e-9e5f-baa406df0440

📥 Commits

Reviewing files that changed from the base of the PR and between a32d5cc and e98cf11.

📒 Files selected for processing (1)

• package.json

---

📝 Walkthrough

Walkthrough

The project version in package.json is incremented from 0.28.0 to 0.29.0. No other configuration, scripts, or dependencies are modified.

Changes

Version Bump

Layer / File(s)	Summary
Version Update package.json	Version string updated from 0.28.0 to 0.29.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

🐰 Hop, hop! A version springs to life,
From 0.28 through the changelog's night,
Now 0.29 shines so bright,
Minor bump, all's right! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'feat: bump version' is directly related to the changeset, which only modifies package.json to bump the version from 0.28.0 to 0.29.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/bump-version

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	nx@​16.3.2
	typeorm-fastify-plugin@​1.0.5
	reflect-metadata@​0.2.2
	typechain@​8.2.0
	ts-node@​10.9.1
	node-telegram-bot-api@​0.65.1
	vite-plugin-dts@​3.1.0
	typeorm@​0.3.17
	pg@​8.13.1
	tslib@​2.6.0
	pino-pretty@​11.2.2
	openapi-typescript@​7.0.2
	vite-tsconfig-paths@​4.2.0
	pg@​8.14.1
	typescript@​5.5.3
	openapi-fetch@​0.10.2
	ts-jest@​29.1.1
	prettier@​2.8.8
	uuid@​11.1.0
	viem@​2.38.5

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: npm sha.js is missing type checks leading to hash rewind and passing on crafted data CVE: GHSA-95m3-7q98-8xr5 sha.js is missing type checks leading to hash rewind and passing on crafted data (CRITICAL) Affected versions: < 2.4.12 Patched version: 2.4.12 From: ? → npm/typeorm@0.3.17 → npm/sha.js@2.4.11 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/sha.js@2.4.11. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report