Skip to content

chore(main): release 1.501.2 #6044

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

Conversation

rubenfiszel
Copy link
Contributor

@rubenfiszel rubenfiszel commented Jun 24, 2025

🤖 I have created a release beep boop

1.501.2 (2025-06-24)

Bug Fixes

  • improve schema form handling of inconsistent order and properties (3daf79f)

This PR was generated with Release Please. See documentation.


Important

Release version 1.501.2 with a bug fix for schema form handling and version updates across multiple files.

  • Version Bump:
    • Update version to 1.501.2 in Cargo.lock, Cargo.toml, openapi.yaml, package.json, Pipfile, pyproject.toml, jsr.json, and version.txt.
  • Bug Fix:
    • Improve schema form handling of inconsistent order and properties in backend.
  • Misc:

This description was created by Ellipsis for 1336462. You can customize this summary. It will automatically update as commits are pushed.

@rubenfiszel
Copy link
Contributor Author

/ai review this PR

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.

Important

Looks good to me! 👍

Reviewed everything up to 8a01e6b in 25 seconds. Click for details.
  • Reviewed 24 lines of code in 2 files
  • Skipped 0 files when reviewing.
  • Skipped posting 1 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. version.txt:1
  • Draft comment:
    Version bump to 1.501.2 is correct.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_V4EW5f3WatKzz4hs

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

@rubenfiszel rubenfiszel merged commit d24eea2 into main Jun 24, 2025
11 checks passed
@rubenfiszel rubenfiszel deleted the release-please--branches--main--components--windmill branch June 24, 2025 18:30
@github-actions github-actions bot locked and limited conversation to collaborators Jun 24, 2025
@rubenfiszel
Copy link
Contributor Author

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.

Important

Looks good to me! 👍

Reviewed 1336462 in 2 minutes and 55 seconds. Click for details.
  • Reviewed 421 lines of code in 13 files
  • Skipped 1 files when reviewing.
  • Skipped posting 12 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. backend/Cargo.lock:1639
  • Draft comment:
    Bump 'bumpalo' dependency from v3.18.1 to v3.19.0 with an updated checksum. Confirm that the new checksum is correct and that all tests pass with this upgraded version.
  • 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 bumping the version of 'bumpalo'. It asks the PR author to confirm the checksum and ensure tests pass, which violates the rules against asking for confirmation or testing. The comment does not provide a specific code suggestion or highlight a potential issue with the change itself.
2. backend/Cargo.toml:1
  • Draft comment:
    The Cargo.toml version has been bumped to 1.501.2 to match the lockfile. This is consistent with the other backend updates.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, providing information about a version bump in a configuration file. It does not offer a suggestion, ask for confirmation, or point out a potential issue. According to the rules, purely informative comments should be removed.
3. benchmarks/lib.ts:5
  • Draft comment:
    The VERSION constant is updated to 'v1.501.2'. Verify that using the 'v' prefix here is intentional compared to other modules that omit it.
  • 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 several rules. It asks the author to "verify" something, which is explicitly discouraged. It's speculative since it's not pointing out a clear issue. The use of 'v' prefix appears consistent with other version numbers in the file. The change is just a minor version bump from v1.501.1 to v1.501.2. The version format could be dictated by some external requirement or convention I'm not aware of. There might be other files in the codebase that use a different format. Even if there are different conventions elsewhere, this comment is still not actionable and asks for verification rather than suggesting a clear change. The existing format appears intentional and consistent within this file. Delete this comment as it violates the rules by asking for verification rather than suggesting a clear change, and the version format appears consistent within the visible context.
4. cli/main.ts:66
  • Draft comment:
    CLI's VERSION constant is updated to '1.501.2' (without the 'v' prefix), which appears intentional. Ensure this format difference is documented if needed.
  • Reason this comment was not posted:
    Comment looked like it was already resolved.
5. frontend/package.json:3
  • Draft comment:
    The frontend package.json version is updated to 1.501.2. This is a straightforward bump.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, as it only states that the version in package.json has been updated. It doesn't provide any actionable feedback or suggestions for improvement.
6. lsp/Pipfile:7
  • Draft comment:
    Dependency constraints for 'wmill' and 'wmill_pg' have been updated to ">=1.501.2", ensuring that the newer release is used.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, as it only states that dependency constraints have been updated. It does not provide any actionable feedback or suggestions for improvement.
7. openflow.openapi.yaml:4
  • Draft comment:
    The OpenFlow OpenAPI spec version is updated to 1.501.2. This version bump helps keep documentation in sync.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, as it only states that the OpenFlow OpenAPI spec version is updated and mentions the purpose of the update. It does not provide any actionable feedback or suggestions for improvement.
8. powershell-client/WindmillClient/WindmillClient.psd1:15
  • Draft comment:
    ModuleVersion in the PowerShell manifest is updated to 1.501.2. This ensures consistency for the PowerShell client.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, as it simply states what was done without providing any actionable feedback or suggestions. It does not ask for confirmation or suggest any changes.
9. python-client/wmill/pyproject.toml:3
  • Draft comment:
    The Python client version is updated to 1.501.2 in pyproject.toml, aligning it with the release.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, as it only states that the Python client version is updated in the pyproject.toml file. It doesn't provide any actionable feedback or suggestions for improvement.
10. python-client/wmill_pg/pyproject.toml:3
  • Draft comment:
    The extension client version is updated to 1.501.2. Note that the dependency on 'wmill' remains '^1.5.0'; verify if this liberal constraint is intentional.
  • Reason this comment was not posted:
    Comment was on unchanged code.
11. typescript-client/jsr.json:3
  • Draft comment:
    The version in jsr.json is updated to 1.501.2, ensuring consistency for the TypeScript client entry point.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, as it only states what has been done without providing any actionable feedback or suggestions. It does not ask for confirmation or suggest any improvements.
12. typescript-client/package.json:4
  • Draft comment:
    The TypeScript client package version is updated to 1.501.2. This completes the version bump across all modules.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, as it only states that a version bump has been completed across all modules. It does not provide any actionable feedback or suggestions for improvement.

Workflow ID: wflow_LECzDALBh5Q5KAyO

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant