Skip to content

Publish version v0.2.25 #1736

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 9 commits into from
Apr 5, 2025
Merged

Publish version v0.2.25 #1736

merged 9 commits into from
Apr 5, 2025

Conversation

Kitenite
Copy link
Contributor

@Kitenite Kitenite commented Apr 5, 2025

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 to version v0.2.25 with dependency updates and minor code adjustments across multiple files.

  • Version Update:
    • Update version to 0.2.25 in package.json and apps/studio/package.json.
  • Dependency Updates:
    • Update @trainloop/sdk to ^0.1.8 in apps/studio/package.json and bun.lock.
    • Update bun-version to 1.2.8 in .github/workflows/build.yml.
    • Update various dependencies in bun.lock including @ai-sdk/anthropic, @typescript-eslint/eslint-plugin, @types/node, and others.
  • Code Adjustments:
    • Change Message to CoreMessage in trainloop.ts, chat.ts, and code.ts.
    • Modify bun install command in .github/workflows/build.yml to not use --frozen-lockfile.
    • Adjust build scripts in package.json to exclude @onlook/web.

This description was created by Ellipsis for e9c8f4a. It will automatically update as commits are pushed.

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Looks good to me! Reviewed everything up to 8bf098a in 31 seconds

More details
  • Looked at 13 lines of code in 1 files
  • Skipped 0 files when reviewing.
  • Skipped posting 5 drafted comments based on config settings.
1. apps/studio/package.json:4
  • Draft comment:
    Version update to 0.2.25 is correct for a release; good to bump the version accordingly.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50%
    None
2. apps/studio/package.json:4
  • Draft comment:
    The PR description mentions onboarding docs improvements, but no related documentation changes are visible in the diff.
  • 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 to explain the discrepancy between the PR description and the changes. This violates the rule against asking the PR author to update the PR description or to confirm their intention.
3. apps/studio/package.json:4
  • Draft comment:
    Version bump updated from 0.2.24 to 0.2.25.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50%
    None
4. apps/studio/package.json:4
  • Draft comment:
    The diff only shows a version bump. Issue 123 requires onboarding docs improvements for Next.js, Remix, Webpack, and Babel; no such documentation changes are visible.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
    This comment is purely informative and does not provide any actionable feedback or suggestions for improvement. It also mentions documentation changes that are not visible, which is not relevant to the code changes in the PR.
5. apps/studio/package.json:30
  • Draft comment:
    The script key 'pree2e' on line 30 looks like it might be a typographical error. If the intention was to use the automatic pre-script hook (e.g. 'pre:e2e'), please update it accordingly. If it's intentional, consider adding a comment to clarify its purpose.
  • 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_LHcNXhlcstIynJbA


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

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Looks good to me! Incremental review on 38a2202 in 53 seconds

More details
  • Looked at 570 lines of code in 1 files
  • Skipped 0 files when reviewing.
  • Skipped posting 5 drafted comments based on config settings.
1. bun.lock:1
  • Draft comment:
    The diff only updates dependency versions in bun.lock; there are no documentation changes for improved onboarding.
  • 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.
2. bun.lock:1
  • Draft comment:
    No documentation updates found. The diff only shows dependency and version bumps. Ensure the onboarding docs for Next.js, Remix, Webpack, and Babel are included as intended.
  • 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.
3. bun.lock:80
  • Draft comment:
    TailwindCSS was bumped from 4.0.17 to 4.1.3. Verify that this update is compatible and doesn’t break any custom configurations.
  • 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. bun.lock:950
  • Draft comment:
    TypeScript has been updated from 5.8.2 to 5.8.3. Confirm that this minor update does not introduce any type regressions.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
    This comment is about a dependency update, specifically a minor version update of TypeScript. The comment asks the PR author to confirm that the update does not introduce any type regressions. According to the rules, comments should not ask the author to confirm or ensure things, especially regarding dependency updates. Therefore, this comment should be removed.
5. bun.lock:1700
  • Draft comment:
    ESLint is updated from 9.23.0 to 9.24.0. Check that any configuration or peer dependency compatibility issues have been addressed.
  • 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_JvGTy2UMTgi3tCLS


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

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Looks good to me! Incremental review on 2740246 in 1 minute and 7 seconds

More details
  • Looked at 42 lines of code in 1 files
  • Skipped 0 files when reviewing.
  • Skipped posting 10 drafted comments based on config settings.
1. .github/workflows/build.yml:29
  • Draft comment:
    Ensure that the indentation for the matrix 'include' section is consistent with project style.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50%
    None
2. .github/workflows/build.yml:57
  • Draft comment:
    Bun version bumped from 1.2.7 to 1.2.8. Confirm that this version update is intentional for this release.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50%
    None
3. .github/workflows/build.yml:74
  • Draft comment:
    Minor formatting adjustment in the 'Build and Release' step; ensure it doesn't affect functionality.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50%
    None
4. .github/workflows/build.yml:1
  • Draft comment:
    The PR title and issue description mention onboarding docs improvements, but no documentation changes are visible in this diff. Please ensure the onboarding docs updates are included in this release.
  • 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.
5. .github/workflows/build.yml:27
  • Draft comment:
    Indentation in the 'matrix' include block was adjusted—verify that this change maintains consistent YAML formatting.
  • Reason this comment was not posted:
    Confidence changes required: 33% <= threshold 50%
    None
6. .github/workflows/build.yml:57
  • Draft comment:
    The bun version was updated from 1.2.7 to 1.2.8. Please confirm this version is fully compatible with our project.
  • Reason this comment was not posted:
    Confidence changes required: 33% <= threshold 50%
    None
7. .github/workflows/build.yml:74
  • Draft comment:
    Whitespace cleanup: Removed extra spacing in the 'Build and Release' step for better readability.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50%
    None
8. .github/workflows/build.yml:96
  • Draft comment:
    A newline was added at the end of the file, which improves POSIX compliance.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50%
    None
9. .github/workflows/build.yml:1
  • Draft comment:
    The PR description mentions updates for onboarding docs (issue 123), yet this diff only contains release workflow adjustments. Please verify if the documentation changes were omitted.
  • 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. .github/workflows/build.yml:96
  • Draft comment:
    There's no newline at the end of the file. Please add a newline to ensure proper file formatting.
  • 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_wFdWiglfBnGI6MLD


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

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ Changes requested. Incremental review on e3fbe34 in 1 minute and 19 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. .github/workflows/build.yml:1
  • Draft comment:
    PR description mentions onboarding docs improvements (issue 123), but this diff only updates the build workflow. Verify 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.
2. .github/workflows/build.yml:61
  • Draft comment:
    Removing '--frozen-lockfile' may lead to non-deterministic installs. Confirm if this change is intended.
  • Reason this comment was not posted:
    Marked as duplicate.
3. .github/workflows/build.yml:1
  • Draft comment:
    The PR description (issue 123) mentions onboarding docs improvements, but no documentation changes are present. Please verify 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.

Workflow ID: wflow_L7e6pWbzqZgxYPU1


Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

- name: Install dependencies
run: bun install --frozen-lockfile
run: bun install
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing --frozen-lockfile may lead to inconsistent dependency versions. Confirm if this change is intentional.

Suggested change
run: bun install
run: bun install --frozen-lockfile

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ Changes requested. Incremental review on 3da8e03 in 1 minute and 45 seconds

More details
  • Looked at 137 lines of code in 5 files
  • Skipped 0 files when reviewing.
  • Skipped posting 4 drafted comments based on config settings.
1. apps/studio/electron/main/chat/trainloop.ts:21
  • Draft comment:
    Avoid forced casting: converting 'messages' to 'unknown' and then to 'Record<string, string>[]' might hide type mismatches. Consider a proper adapter if the shapes differ.
  • 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.
2. package.json:3
  • Draft comment:
    The version field is still '0.0.0'; update it to 'v0.2.25' to match the release.
  • 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.
3. package.json:52
  • Draft comment:
    Dependency '@trainloop/sdk' was updated to '^0.1.8'. Please verify that this version update is compatible with the recent type changes in the code.
  • 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 compatibility of a dependency update, which is against the rules. It does not provide a specific suggestion or point out a specific issue with the code.
4. package.json:1
  • Draft comment:
    The PR description mentions improvements to onboarding docs (issue [FEAT] Add better onboarding docs #123), but no documentation changes are present in the diff. Please ensure that the intended documentation updates are included or update the PR description accordingly.
  • 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_olWIQLi9md8SIzVS


Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

const client = await this.getClient();
await client.sendData(messages, type as string, 'onlook-apply-set');
await client.sendData(
messages as unknown as Record<string, string>[],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Avoid casting messages via unknown to Record<string, string>[]. An explicit conversion (or mapping) would ensure that the CoreMessage structure meets the expected shape and improves type safety.

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Looks good to me! Incremental review on 9995088 in 1 minute and 35 seconds

More details
  • Looked at 99 lines of code in 4 files
  • Skipped 0 files when reviewing.
  • Skipped posting 10 drafted comments based on config settings.
1. .github/workflows/build.yml:59
  • Draft comment:
    Using '--frozen-lockfile' is good for ensuring consistent dependency installs.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50%
    None
2. apps/studio/package.json:46
  • Draft comment:
    Dependency version bump for '@trainloop/sdk' from 0.1.5 to 0.1.8.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50%
    None
3. bun.lock:3
  • Draft comment:
    Ensure that the upgraded/downgraded 'form-data' versions align with all dependent packages and security patches.
  • Reason this comment was not posted:
    Confidence changes required: 33% <= threshold 50%
    None
4. package.json:48
  • Draft comment:
    Removal of root-level '@trainloop/sdk' dependency appears intentional; verify that all relevant workspaces now include it where needed.
  • Reason this comment was not posted:
    Confidence changes required: 33% <= threshold 50%
    None
5. .github/workflows/build.yml:58
  • Draft comment:
    Good change: using ‘--frozen-lockfile’ ensures dependency consistency in CI. Verify that this doesn’t block builds if the lockfile is outdated.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50%
    None
6. apps/studio/package.json:45
  • Draft comment:
    Updating '@trainloop/sdk' from ^0.1.5 to ^0.1.8 looks correct. Ensure backward compatibility with the studio app.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50%
    None
7. bun.lock:3
  • Draft comment:
    The lock file now removes the top‐level '@trainloop/sdk' dependency and shows mixed versions for 'form-data'. Confirm that the downgrade to [email protected] (for one entry) versus [email protected] (in others) is intentional and won’t cause API 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%
    The rules explicitly state "Do NOT comment on dependency changes, library versions that you don't recognize, or anything else related to dependencies." This comment is entirely about dependency changes and version mismatches in the lock file. Lock files are automatically generated and version conflicts are typically handled by the package manager.
    Maybe version mismatches could cause runtime issues that would be important to catch during review? The comment might be trying to prevent a potential bug.
    While version mismatches could theoretically cause issues, this is precisely the kind of dependency management that should be handled by the package manager, not code review comments. If there were real conflicts, they would surface during build or runtime testing.
    This comment should be deleted as it violates the explicit rule against commenting on dependency changes and version mismatches.
8. package.json:48
  • Draft comment:
    Removal of the root-level dependencies block for '@trainloop/sdk' appears intentional for workspaces. Confirm that all packages now declare their own dependency as needed.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50%
    None
9. package.json:1
  • Draft comment:
    The PR description mentions onboarding docs (issue 123), but the changes here only update dependency versions and release configuration. Please ensure that the documentation updates are included if intended.
  • 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. apps/studio/package.json:30
  • Draft comment:
    Possible typographical error: the script key 'pree2e' on line 30 may be a typo. Consider confirming if it should be 'pre:e2e' or some other naming for clarity and consistency.
  • 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_6vu2CoCDZhetJzFj


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

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ Changes requested. Incremental review on 9268ca5 in 1 minute and 37 seconds

More details
  • Looked at 13 lines of code in 1 files
  • Skipped 0 files when reviewing.
  • Skipped posting 2 drafted comments based on config settings.
1. .github/workflows/build.yml:1
  • Draft comment:
    PR description mentions onboarding docs, but diff only changes dependency install command.
  • 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.
2. .github/workflows/build.yml:61
  • Draft comment:
    Removing --frozen-lockfile may allow unintended dependency updates leading to non-deterministic builds. Also, the PR description mentions onboarding docs improvements, but no documentation changes are present. Please verify if these changes are intentional.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 50% <= threshold 50%
    The comment contains two parts. The first part about removing --frozen-lockfile is a valid concern as it could lead to non-deterministic builds, which is a specific and actionable point. The second part about the PR description mentioning onboarding docs improvements is not allowed as it asks the author to verify the PR description, which violates the rules.

Workflow ID: wflow_vq74TlfjMuqFdFDU


Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

- name: Install dependencies
run: bun install --frozen-lockfile
run: bun install
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reverting --frozen-lockfile may lead to inconsistent installs. Confirm if this change is intentional.

Suggested change
run: bun install
run: bun install --frozen-lockfile

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Looks good to me! Incremental review on 43c5212 in 24 seconds

More details
  • Looked at 11 lines of code in 1 files
  • Skipped 0 files when reviewing.
  • Skipped posting 2 drafted comments based on config settings.
1. apps/studio/electron/main/chat/trainloop.ts:2
  • Draft comment:
    Good use of the type-only import for SampleFeedbackType. However, the PR description mentions better onboarding docs, but no documentation changes are present in this diff.
  • 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 to ensure that the documentation changes are included, which violates the rules. It is not a specific code suggestion or a request for a test to be written.
2. apps/studio/electron/main/chat/trainloop.ts:2
  • Draft comment:
    Good use of 'import type' for importing SampleFeedbackType. This change ensures that only the type is imported with no runtime impact, aligning with TypeScript best practices.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50%
    None

Workflow ID: wflow_t83wW4xHUXUb7i7A


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

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Looks good to me! Incremental review on e9c8f4a in 1 minute and 0 seconds

More details
  • Looked at 15 lines of code in 1 files
  • Skipped 0 files when reviewing.
  • Skipped posting 3 drafted comments based on config settings.
1. package.json:27
  • Draft comment:
    Confirm intentional exclusion of @onlook/web from build.
  • Reason this comment was not posted:
    Confidence changes required: 33% <= threshold 50%
    None
2. package.json:28
  • Draft comment:
    Verify ci:build script aligns with new build configuration.
  • Reason this comment was not posted:
    Confidence changes required: 33% <= threshold 50%
    None
3. package.json:27
  • Draft comment:
    Ensure the change to exclude '@onlook/web' in build/ci:build is intentional. Verify that excluding this package via '!@onlook/web' does not inadvertently drop needed builds and document the reasoning.
  • Reason this comment was not posted:
    Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50%
    This comment violates multiple rules. It starts with "Ensure" and "Verify" which are explicitly mentioned as red flags. It's asking the author to confirm their intention and document reasoning, which our rules specifically say not to do. The change appears deliberate since it's done consistently in both commands.
    Maybe the exclusion could break the build process in a way that's not immediately obvious? The comment might be trying to prevent a potential issue.
    Our rules clearly state not to make speculative comments or ask for confirmation of intent. If there was a concrete build issue, it would be caught by CI.
    The comment should be deleted as it violates our rules by asking for verification of intent and documentation of reasoning.

Workflow ID: wflow_KFXQANm6iqtCcCbm


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

@Kitenite Kitenite merged commit 900c689 into main Apr 5, 2025
5 of 6 checks passed
@Kitenite Kitenite deleted the releases/0.2.25 branch April 5, 2025 20:46
ml-delaurier pushed a commit to ml-delaurier/nolook that referenced this pull request Apr 23, 2025
t1c1 pushed a commit to t1c1/onlookbotcodes that referenced this pull request Jun 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant