chore: version upgrade to 1.2.0

[pushya22]

Upgraded app version from 1.1.0 to 1.2.0

---

Note

Update all package versions across apps and packages from 1.1.0 to 1.2.0.

^{Written by Cursor Bugbot for commit 0046d54. This will update automatically on new commits. Configure here.}

Summary by CodeRabbit

• Chores
  • Bumped version to 1.2.0 across all packages. No functional changes, dependency updates, or behavioral modifications included.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Pushya Mitra Thiruvooru seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Walkthrough

Version bumps applied uniformly across 18 package.json files in the monorepo, advancing all packages from 1.1.0 to 1.2.0. No dependencies, scripts, exports, or functional logic modified.

Changes

Cohort / File(s)	Summary
Application packages apps/admin/package.json, apps/api/package.json, apps/live/package.json, apps/space/package.json, apps/web/package.json	Version bumped: 1.1.0 → 1.2.0
Root workspace package.json	Version bumped: 1.1.0 → 1.2.0
Workspace packages packages/codemods/package.json, packages/constants/package.json, packages/editor/package.json, packages/hooks/package.json, packages/i18n/package.json, packages/logger/package.json, packages/propel/package.json, packages/services/package.json, packages/shared-state/package.json, packages/tailwind-config/package.json, packages/types/package.json, packages/typescript-config/package.json, packages/ui/package.json, packages/utils/package.json	Version bumped: 1.1.0 → 1.2.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

All changes are identical version metadata updates across homogeneous files with no logic, dependencies, or behavioral modifications to evaluate.

Poem

🐰 A hop, a skip, a version bump—
From 1.1.0, up we jump!
To 1.2.0 across the land,
Eighteen packages, hand in hand.
Coordinated growth, smooth as can be,
A monorepo in harmony! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description provides a brief summary of the version upgrade but is missing most required template sections including Type of Change, Test Scenarios, and References; only a partial note is provided.	Complete the description template by selecting an appropriate Type of Change, documenting test scenarios, and linking any related issues or references.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: version upgrade to 1.2.0' is specific and clearly summarizes the main change—a version bump across the project from 1.1.0 to 1.2.0, which matches the raw_summary findings.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/version-upgrade

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 69b6468 and 0046d54.

📒 Files selected for processing (20)

• apps/admin/package.json (1 hunks)
• apps/api/package.json (1 hunks)
• apps/live/package.json (1 hunks)
• apps/space/package.json (1 hunks)
• apps/web/package.json (1 hunks)
• package.json (1 hunks)
• packages/codemods/package.json (1 hunks)
• packages/constants/package.json (1 hunks)
• packages/editor/package.json (1 hunks)
• packages/hooks/package.json (1 hunks)
• packages/i18n/package.json (1 hunks)
• packages/logger/package.json (1 hunks)
• packages/propel/package.json (1 hunks)
• packages/services/package.json (1 hunks)
• packages/shared-state/package.json (1 hunks)
• packages/tailwind-config/package.json (1 hunks)
• packages/types/package.json (1 hunks)
• packages/typescript-config/package.json (1 hunks)
• packages/ui/package.json (1 hunks)
• packages/utils/package.json (1 hunks)

🧰 Additional context used

🧠 Learnings (6)

📓 Common learnings

Learnt from: lifeiscontent
Repo: makeplane/plane PR: 7888
File: packages/propel/package.json:74-79
Timestamp: 2025-10-06T14:40:39.253Z
Learning: When reviewing package.json dependency version updates, verify each package version individually on the npm registry before claiming a version doesn't exist. Different packages within the same organization may have different latest versions.

📚 Learning: 2025-08-29T08:45:15.953Z

Learnt from: sriramveeraghanta
Repo: makeplane/plane PR: 7672
File: pnpm-workspace.yaml:8-9
Timestamp: 2025-08-29T08:45:15.953Z
Learning: The makeplane/plane repository uses pnpm v10.12.1, which supports onlyBuiltDependencies configuration in pnpm-workspace.yaml files.

Applied to files:

• apps/api/package.json
• apps/admin/package.json
• packages/utils/package.json
• packages/editor/package.json
• packages/ui/package.json
• packages/propel/package.json
• package.json
• packages/tailwind-config/package.json
• packages/types/package.json
• packages/shared-state/package.json
• packages/services/package.json
• packages/constants/package.json
• packages/typescript-config/package.json
• packages/i18n/package.json

📚 Learning: 2025-10-01T15:30:17.605Z

Learnt from: lifeiscontent
Repo: makeplane/plane PR: 7888
File: packages/propel/src/avatar/avatar.stories.tsx:2-3
Timestamp: 2025-10-01T15:30:17.605Z
Learning: In the makeplane/plane repository, avoid suggesting inline type imports (e.g., `import { Avatar, type TAvatarSize }`) due to bundler compatibility issues. Keep type imports and value imports as separate statements.

Applied to files:

• packages/types/package.json

📚 Learning: 2025-10-09T20:42:31.843Z

Learnt from: lifeiscontent
Repo: makeplane/plane PR: 7922
File: apps/admin/app/(all)/(dashboard)/ai/form.tsx:19-19
Timestamp: 2025-10-09T20:42:31.843Z
Learning: In the makeplane/plane repository, React types are globally available through TypeScript configuration. Type annotations like React.FC, React.ReactNode, etc. can be used without explicitly importing the React namespace. The codebase uses the modern JSX transform, so React imports are not required for JSX or type references.

Applied to files:

• packages/types/package.json

📚 Learning: 2025-05-14T13:16:23.323Z

Learnt from: vamsikrishnamathala
Repo: makeplane/plane PR: 7061
File: web/core/components/workspace-notifications/root.tsx:18-18
Timestamp: 2025-05-14T13:16:23.323Z
Learning: In the Plane project codebase, the path alias `@/plane-web` resolves to the `ce` directory, making imports like `@/plane-web/hooks/use-notification-preview` correctly resolve to files in `web/ce/hooks/`.

Applied to files:

• packages/hooks/package.json

📚 Learning: 2025-03-11T19:42:41.769Z

Learnt from: janreges
Repo: makeplane/plane PR: 6743
File: packages/i18n/src/store/index.ts:160-161
Timestamp: 2025-03-11T19:42:41.769Z
Learning: In the Plane project, the file 'packages/i18n/src/store/index.ts' already includes support for Polish language translations with the case "pl".

Applied to files:

• packages/i18n/package.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Build and lint web apps
• GitHub Check: Analyze (javascript)

🔇 Additional comments (20)

apps/space/package.json (1)

3-3: Version bump applied cleanly.

The version upgrade from 1.1.0 to 1.2.0 is isolated to the version field with no changes to scripts, dependencies, or exports. The dependency resolution via workspace:* and catalog: entries remains consistent.

apps/live/package.json (1)

3-3: Version bump applied cleanly.

The version upgrade from 1.1.0 to 1.2.0 is isolated to the version field with no changes to scripts, dependencies, exports, or runtime behavior. All dependency versions remain unchanged.

packages/constants/package.json (1)

3-3: Version bump applied cleanly.

The version upgrade from 1.1.0 to 1.2.0 is isolated to the version field with no changes to exports, dependencies, or scripts. The public API surface remains unchanged.

apps/web/package.json (1)

3-3: Version bump applied cleanly.

The version upgrade from 1.1.0 to 1.2.0 is isolated to the version field with no changes to the extensive dependency list, scripts, or behavior. All pinned and workspace-resolved dependencies remain unchanged.

packages/i18n/package.json (1)

3-3: Version bump applied cleanly.

The version upgrade from 1.1.0 to 1.2.0 is isolated to the version field with no changes to exports, dependencies, or scripts. The module contract remains unchanged.

packages/typescript-config/package.json (1)

3-3: Version bump applied cleanly.

The version upgrade from 1.1.0 to 1.2.0 is isolated to the version field with no changes to the distributed config files. Configuration remains stable.

apps/admin/package.json (1)

4-4: Version bump applied cleanly.

The version upgrade from 1.1.0 to 1.2.0 is isolated to the version field with no changes to dependencies, scripts, or description. All dependency versions remain unchanged.

packages/logger/package.json (1)

3-3: Version bump applied cleanly.

The version upgrade from 1.1.0 to 1.2.0 is isolated to the version field with no changes to exports, scripts, or dependencies. The module interface and runtime behavior remain unchanged.

packages/utils/package.json (1)

3-3: Version bump applied correctly.

The package version has been updated from 1.1.0 to 1.2.0 as intended, with no changes to exports, scripts, or dependencies. The change is consistent across the monorepo.

packages/tailwind-config/package.json (1)

3-3: Version bump applied correctly.

The package version has been updated from 1.1.0 to 1.2.0 with no changes to dependencies or configuration. Consistent with the monorepo-wide version upgrade.

packages/codemods/package.json (1)

3-3: Version bump applied correctly.

The package version has been updated from 1.1.0 to 1.2.0 with no changes to scripts or dependencies. Consistent with the version upgrade across the monorepo.

packages/ui/package.json (1)

5-5: Version bump applied correctly.

The package version has been updated from 1.1.0 to 1.2.0 with no changes to exports, dependencies, or peer dependencies. Consistent with the monorepo-wide version upgrade.

packages/types/package.json (1)

3-3: Version bump applied correctly.

The package version has been updated from 1.1.0 to 1.2.0 with no changes to exports, scripts, or dependencies. Consistent with the monorepo-wide version upgrade.

packages/hooks/package.json (1)

3-3: Version bump applied correctly.

The package version has been updated from 1.1.0 to 1.2.0 with no changes to exports, scripts, or dependencies. Consistent with the monorepo-wide version upgrade.

packages/editor/package.json (1)

3-3: Version bump applied correctly.

The package version has been updated from 1.1.0 to 1.2.0 with no changes to exports, scripts, dependencies, or keywords. Consistent with the monorepo-wide version upgrade.

packages/shared-state/package.json (1)

3-3: Version bump applied correctly.

The package version has been updated from 1.1.0 to 1.2.0 with no changes to scripts, dependencies, or devDependencies. Consistent with the monorepo-wide version upgrade.

packages/services/package.json (1)

3-3: Version bump is clean and consistent.

The version field update aligns with the coordinated monorepo bump. No other package.json fields were affected, which is appropriate for a version-only release.

apps/api/package.json (1)

3-3: Version bump is correct.

The version field update is part of the coordinated monorepo bump to 1.2.0. No other fields were affected.

packages/propel/package.json (1)

3-3: Version bump is clean and consistent.

The version field update aligns with the coordinated monorepo release to 1.2.0. All exports, dependencies, and scripts remain unchanged, which is correct for a version-only release.

package.json (1)

5-5: Version bump is correct.

The version field update drives the coordinated 1.2.0 release across the monorepo. All scripts, dependencies, and pnpm configuration remain unchanged, maintaining stability in the build pipeline.

---

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