Publish version v0.2.22

[Kitenite]

Description

Related Issues

Type of Change

• Bug fix
• New feature
• Documentation update
• Release
• Refactor
• Other (please describe):

Testing

Screenshots (if applicable)

Additional Notes

---

Important

Update bun version, remove dependencies, and update TypeScript configurations to target ES2023.

• Version Update:
  • Update bun-version to 1.2.7 in build.yml.
• Dependency Changes:
  • Remove multiple dependencies from bun.lock.
• TypeScript Configurations:
  • Update target to ES2023 in base.json and vite-react.json.
  • Update lib to include ES2023, DOM, and DOM.Iterable in base.json and vite-react.json.

^{This description was created by for 1e3b507. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 00f36d4 in 1 minute and 2 seconds

More details

• Looked at 13 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 3 drafted comments based on config settings.

1. apps/studio/package.json:4

• Draft comment:
  PR labeled as adding onboarding docs but diff only updates version. Missing actual doc changes.
• Reason this comment was not posted:
  Comment was on unchanged code.

2. apps/studio/package.json:4

• Draft comment:
  Version bump updated to 0.2.22. Ensure that onboarding docs updates (issue 123) are reflected in the release notes/changelog if intended.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

3. apps/studio/package.json:30

• Draft comment:
  There's a potential typographical error in the script name 'pree2e'. Consider checking if this should be 'pre-e2e' (or following another consistent naming scheme) to maintain uniformity with other script names.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_xFKQbCQ1qfpodYKq

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

👍 Looks good to me! Incremental review on 5dc882a in 2 minutes and 40 seconds

More details

• Looked at 180 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 21 drafted comments based on config settings.

1. bun.lock:10

• Draft comment:
  Version bump in @onlook/studio: 0.2.21 → 0.2.22 looks correct.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

2. bun.lock:1260

• Draft comment:
  Downgrade of ansi-styles from v5.2.0 to v4.3.0 with added dependency on color-convert. Confirm this change is intentional and won’t break compatibility.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is about a dependency change, specifically a downgrade of a library version and an added dependency. The comment asks the author to confirm the change is intentional and won't break compatibility, which violates the rule against asking for confirmation or ensuring behavior is intended. Therefore, this comment should be removed.

3. bun.lock:1358

• Draft comment:
  Buffer package downgraded from v6.0.3 to v5.7.1. Verify that this downgrade is desired and that dependencies depending on a newer version still work correctly.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is about a dependency change, specifically a downgrade of a package version. The rules specify not to comment on dependency changes or ask the author to verify intentions regarding dependencies. Therefore, this comment should be removed.

4. bun.lock:1476

• Draft comment:
  The main 'commander' entry is changed from v6.2.1 to v4.1.1 while an 'openapi/commander' entry uses v6.2.1. Please verify that mixing these versions is intentional to avoid potential conflicts.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50%
  This is a dependency change in bun.lock. The comment is asking for verification about dependency versions, which violates our rules. We should not ask authors to verify or confirm things. Additionally, dependency-related comments are explicitly forbidden by the rules ("Do NOT comment on dependency changes, library versions that you don't recognize, or anything else related to dependencies").
  Perhaps having multiple versions of the same package could cause real technical issues that should be addressed?
  While that's possible, the rules explicitly state not to comment on dependencies. Package managers like bun are designed to handle multiple versions of the same package through proper resolution and isolation.
  Delete this comment as it violates multiple rules - it asks for verification and comments on dependency versions, both of which are explicitly forbidden.

5. bun.lock:2808

• Draft comment:
  sprintf-js was bumped from v1.0.3 to v1.1.3. Check that this upgrade is compatible with all dependents.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

6. bun.lock:3310

• Draft comment:
  Multiple duplicate entries (e.g. for buffer, ansi-styles, sprintf-js) have been removed. Confirm that these removals are safe and won’t affect dependent packages.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is asking the PR author to confirm the safety of removing duplicate entries, which violates the rule against asking for confirmation or ensuring behavior is intended. It does not provide a specific suggestion or point out a clear issue.

7. bun.lock:3654

• Draft comment:
  New entry 'cohere-ai/readable-stream/buffer' reintroduces buffer v6.0.3 while the main buffer entry is set to v5.7.1. Reconcile these differing versions to avoid conflicts.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

8. bun.lock:3802

• Draft comment:
  The added 'openapi/js-yaml/argparse/sprintf-js' entry uses sprintf-js v1.0.3, yet another entry uses v1.1.3. Ensure version consistency across all sprintf-js usages.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

9. bun.lock:0

• Draft comment:
  PR description mentions onboarding docs additions, but the diff only includes bun.lock changes. Update PR description to accurately reflect the changes.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

10. bun.lock:1

• Draft comment:
  PR description mentions onboarding docs improvements but no documentation changes are present. Confirm that docs updates are handled elsewhere.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

11. bun.lock:5

• Draft comment:
  Removed 'freestyle-sandboxes' from root dependencies. Verify that this removal is intentional for the v0.2.22 release.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is asking the PR author to verify their intention regarding the removal of a dependency. This violates the rule against asking the author to confirm their intention or ensure behavior is intended. Therefore, this comment should not be approved.

12. bun.lock:12

• Draft comment:
  Studio version bumped to 0.2.22, but no onboarding docs changes are evident. Confirm if documentation updates are applied in another commit.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is asking the PR author to confirm if documentation updates are applied in another commit. This violates the rule against asking the PR author to confirm their intention or to ensure that the behavior is intended. The comment does not provide a specific code suggestion or request for a test, and it is related to dependency changes, which should not be commented on.

13. bun.lock:1265

• Draft comment:
  Downgraded 'ansi-styles' from 5.2.0 to 4.3.0; ensure this does not break packages expecting the newer API.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

14. bun.lock:1359

• Draft comment:
  Buffer version changed from 6.0.3 to 5.7.1; verify that modules relying on buffer (and ieee754 version) remain compatible.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is about a dependency change, specifically the version of the 'buffer' library. The comment asks the PR author to verify compatibility, which violates the rule against asking for confirmation or verification of intentions. Therefore, this comment should be removed.

15. bun.lock:1470

• Draft comment:
  Downgraded 'commander' from 6.2.1 to 4.1.1; confirm that consumers of commander can operate with the older version.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

16. bun.lock:2809

• Draft comment:
  sprintf-js upgraded from 1.0.3 to 1.1.3; ensure that this update is consistent for all consumers.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is related to a dependency change, specifically the upgrade of a library version. The comment asks to ensure consistency across consumers, which is not allowed as per the rules. Therefore, this comment should be removed.

17. bun.lock:3170

• Draft comment:
  New '@langchain/core/ansi-styles' mapping uses [email protected] while the global version is 4.3.0; verify that this dual version usage is intentional.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50%
  This is a dependency lock file change. The rules explicitly state "Do NOT comment on dependency changes, library versions that you don't recognize, or anything else related to dependencies." Having multiple versions of a styling library is common in large projects and not necessarily problematic. The comment is asking for verification without clear evidence of an actual issue.
  Maybe there could be a real compatibility issue between these versions that would cause problems? The comment might be trying to prevent potential runtime issues.
  The rules are very clear about not commenting on dependency versions. Without specific evidence of a problem, this is exactly the kind of speculative dependency comment we should avoid.
  Delete this comment as it violates the rule about not commenting on dependency changes and versions.

18. bun.lock:3442

• Draft comment:
  Added 'openapi/commander' with [email protected], which differs from the default commander version; ensure this segregation is deliberate.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

19. bun.lock:3258

• Draft comment:
  Multiple duplicate dependency entries (e.g. for buffer, ansi-styles, sprintf-js) have been removed. Confirm that all necessary overrides remain intact.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is asking the PR author to confirm that necessary overrides remain intact after removing duplicate dependency entries. This falls under the rule of not asking the author to confirm their intention or to double-check things. Therefore, this comment should be removed.

20. bun.lock:3635

• Draft comment:
  Added 'cohere-ai/readable-stream/buffer' using [email protected], while most buffer dependencies are at 5.7.1; check for potential version conflicts.
• Reason this comment was not posted:
  Comment looked like it was already resolved.

21. bun.lock:3785

• Draft comment:
  Pinned 'openapi/js-yaml/argparse/sprintf-js' to version 1.0.3, which differs from the upgraded sprintf-js 1.1.3; verify that this version is required.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is asking the author to verify if a specific version of a dependency is required. This falls under the rule of not commenting on dependency changes or asking for verification of dependency versions. Therefore, this comment should be removed.

Workflow ID: wflow_4AzDTHuHAmDud0yj

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

👍 Looks good to me! Incremental review on 35bf305 in 39 seconds

More details

• Looked at 55 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 4 drafted comments based on config settings.

1. tooling/typescript/base.json:7

• Draft comment:
  Verify ES2023 change
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

2. tooling/typescript/base.json:7

• Draft comment:
  Confirm updating 'lib' from ESNext to ES2023 is intentional and compatible with target environments.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

3. tooling/typescript/base.json:25

• Draft comment:
  Add a newline at EOF for consistent file formatting.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

4. tooling/typescript/base.json:1

• Draft comment:
  PR description mentions onboarding docs updates, but this diff only alters TS config. Confirm that all intended documentation changes are included.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

Workflow ID: wflow_SPwmTwmRWk04N1oo

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

👍 Looks good to me! Incremental review on 7399deb in 1 minute and 49 seconds

More details

• Looked at 31 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 6 drafted comments based on config settings.

1. .github/workflows/build.yml:58

• Draft comment:
  Pinned bun-version to 1.2.7. Confirm this strict version is intentional and compatible with your setup.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

2. tooling/typescript/base.json:6

• Draft comment:
  Changed target from 'ESNext' to 'es2023'. Verify that this aligns with required language features.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

3. .github/workflows/build.yml:57

• Draft comment:
  Pinning Bun to version 1.2.7 ensures reproducible builds. Confirm that this version is compatible across all target environments.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

4. tooling/typescript/base.json:6

• Draft comment:
  Changing 'target' from 'ESNext' to 'es2023' fixes the output version but may limit exposure to newer ECMAScript proposals. Verify this aligns with project needs.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 50%
  None

5. tooling/typescript/base.json:7

• Draft comment:
  Lib entries were changed to lowercase ('dom', 'es2023') for consistency. Ensure these changes are compatible with TypeScript's expected lib names.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

6. .github/workflows/build.yml:55

• Draft comment:
  The PR description references onboarding documentation improvements (Issue 123) for frameworks like Next.js, Remix, Webpack, and Babel, but no doc changes are visible in the diff. Please ensure documentation updates are included or update the PR description accordingly.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is asking the PR author to update the PR description or ensure documentation updates are included. According to the rules, we should not ask the author to update the PR description or ensure that changes are included. Therefore, this comment should be removed.

Workflow ID: wflow_Il8IzRSBykSlmMg1

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

👍 Looks good to me! Incremental review on 11ec391 in 1 minute and 41 seconds

More details

• Looked at 13 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 3 drafted comments based on config settings.

1. apps/studio/package.json:60

• Draft comment:
  PR description mentions onboarding docs changes, but this diff only updates dependency version. Is the docs update missing?
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is asking the PR author to confirm if the documentation update is missing, which violates the rule against asking the author to confirm their intention or to update the PR description. It does not provide a specific code suggestion or request for a test.

2. apps/studio/package.json:60

• Draft comment:
  Dependency update: 'freestyle-sandboxes' bumped from ^0.0.35 to ^0.0.36. Ensure that this update is intentional for the release and that any onboarding docs changes required by issue 123 are included elsewhere.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is about a dependency update, which is not allowed according to the rules. It also asks the author to ensure the update is intentional and to include onboarding docs changes, which violates the rule against asking for confirmations or updates to documentation.

3. apps/studio/package.json:30

• Draft comment:
  The script key 'pree2e' appears to be a typographical error. If it's intended to run a pre-end-to-end test step, consider renaming it to 'pre:e2e' (or another consistent naming convention) for clarity. This will help avoid confusion in the future.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_XPXWQPtT5xoabYMD

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

👍 Looks good to me! Incremental review on 1e3b507 in 1 minute and 19 seconds

More details

• Looked at 32 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 5 drafted comments based on config settings.

1. apps/studio/src/lib/editor/styles/group.ts:245

• Draft comment:
  Removed extra whitespace; this is a formatting-only change.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

2. tooling/typescript/base.json:6

• Draft comment:
  Updated 'target' and 'lib' entries to use uppercase identifiers. Confirm this aligns with project dependency requirements.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

3. tooling/typescript/base.json:1

• Draft comment:
  PR description references onboarding docs improvements, but no related changes are visible in this diff. Confirm that all intended changes are included.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

4. apps/studio/src/lib/editor/styles/group.ts:245

• Draft comment:
  Extraneous whitespace removed in the TextGroup array. This formatting change is non-functional—ensure it aligns with your project's style guidelines.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

5. tooling/typescript/base.json:6

• Draft comment:
  Standardized the 'target' and 'lib' entries to uppercase and added 'DOM.Iterable'. Verify these settings match the intended TypeScript configuration.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

Workflow ID: wflow_GNljK4OaeFB9d7Ms

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.