chore(main): release 1.495.0

[rubenfiszel]

🤖 I have created a release beep boop

1.495.0 (2025-06-03)

Features

• ai flow chat (#5842) (68ebf66)
• ai prompts improvements + o3/o4 support (#5862) (825422c)
• fix backward compatibility pg 14 for postgres trigger (#5851) (4cbcbdb)
• ssh repl like direct to workers hosts machine (#5809) (f252657)

Bug Fixes

• replace crypto.randomUUID with generateRandomString for HTTP compatibility (#5849) (64f35d0), closes #5847

---

This PR was generated with Release Please. See documentation.

---

Important

Release 1.495.0 adds AI flow chat, AI prompt improvements, PostgreSQL 14 compatibility fix, and replaces crypto.randomUUID for HTTP compatibility.

• Features:
  • Add AI flow chat feature.
  • Improve AI prompts with o3/o4 support.
  • Fix backward compatibility for PostgreSQL 14 triggers.
  • Add SSH REPL-like direct access to worker host machines.
• Bug Fixes:
  • Replace crypto.randomUUID with generateRandomString for HTTP compatibility.
• Misc:
  • Update version.txt to 1.495.0.

^{This description was created by for f6ccff8. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 34ca4e4 in 22 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 updated to 1.495.0. Confirm consistency with changelog.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_ijaODwY4N3kpOhHy

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

[cloudflare-workers-and-pages]

Deploying windmill with    Cloudflare Pages

Latest commit:	df90829
Status:	✅  Deploy successful!
Preview URL:	https://84eb90f2.windmill.pages.dev
Branch Preview URL:	https://release-please--branches--ma.windmill.pages.dev

View logs

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed 978a582 in 21 seconds. Click for details.

• Reviewed 29 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 updated to 1.495.0. Ensure version.txt remains in sync with changelog.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_VBIT1DfTQQ5hTYSN

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

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed 224d7ed in 24 seconds. Click for details.

• Reviewed 29 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 updated to 1.495.0. This looks correct and is in line with the release notes.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_6D5S4dERZKDrDg6J

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

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed 308002a in 1 minute and 25 seconds. Click for details.

• Reviewed 30 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 2 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 updated from 1.494.0 to 1.495.0 looks correct. Please ensure this change aligns with the changelog and release notes.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

2. CHANGELOG.md:8

• Draft comment:
  Typo/lexicographical check: 'ai flow chat' might be a typo. Verify if the intended term is 'AI flow chat' (or possibly 'AI flow chart') based on the feature's naming.
• 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 comment is about a change in the diff, but it is speculative and asks the author to verify the intended term. The rules specifically say not to make such comments. There is no strong evidence that 'ai flow chat' is a typo without more context. The comment is not actionable unless the typo is certain. I might be missing that 'ai flow chat' is an obvious typo, but without more context, I can't be sure. The rules require strong evidence and prohibit speculative comments. Given the rules, unless the typo is obvious and not speculative, the comment should be deleted. The comment does not provide strong evidence and asks for verification, which is not allowed. The comment should be deleted because it is speculative and asks the author to verify their intention, which is against the rules.

Workflow ID: wflow_GbkES3jnHoEuDMSl

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

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed eacefa7 in 23 seconds. Click for details.

• Reviewed 30 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 number bump looks appropriate. Confirm it aligns with the changelog update.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_kOp58NAP7z118vmH

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

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed 33b7fb1 in 23 seconds. Click for details.

• Reviewed 30 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.495.0 looks good.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_RYQIhJJV7iD6JsZq

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

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed 760369f in 25 seconds. Click for details.

• Reviewed 30 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 updated to 1.495.0; looks correct.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_tCo0sEmFrkEfu5b5

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

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed 2aedb36 in 21 seconds. Click for details.

• Reviewed 30 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 correctly updates the version from 1.494.0 to 1.495.0.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_FETshXWynJWq0jU0

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

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed 3087685 in 1 minute and 20 seconds. Click for details.

• Reviewed 31 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 2 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 updated to 1.495.0; change looks correct.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

2. CHANGELOG.md:10

• Draft comment:
  There's a possible typo on this line: "ssh repl like direct to workers hosts machine". It might be clearer if written as "SSH REPL direct to worker host machine" or similar. Please double-check for intended wording.
• 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 comment is about a changelog entry, which is documentation, not code logic. The rules specify not to comment unless a code change is required, and not to ask the author to double-check or confirm intention. The suggestion is about clarity, but not a required code change. The comment is informative and speculative, not strictly actionable. Perhaps clarity in changelogs is important for users, but the rules are clear that such comments should not be made unless a code change is required. The comment does not point out a bug or logic error, just a possible improvement in wording. Even if the wording could be improved, the rules prioritize only actionable, required changes. This is not a required change, so the comment should be deleted. The comment should be deleted because it does not require a code change and is not actionable per the review rules.

Workflow ID: wflow_b9eECWf8l8PNq6f3

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

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed f6ccff8 in 1 minute and 35 seconds. Click for details.

• Reviewed 32 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 2 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 updated to 1.495.0. This looks correct; verify that all related references (e.g., release tags or package manifests) are kept in sync.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

2. CHANGELOG.md:11

• Draft comment:
  The text on this line seems to contain typographical issues: "ssh repl like direct to workers hosts machine". It’s unclear if this should be something like "SSH REPL-like direct connection to worker host machines". Please review and correct any typos or phrasing issues.
• 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 comment is about the clarity and grammar of a changelog entry, not about a code change. The rules explicitly say not to make comments unless a code change is required, and not to make purely informative comments. This is a suggestion for better wording, not a required change. Therefore, the comment should be deleted. Perhaps the changelog is important for user communication, and unclear entries could be problematic. However, the rules are clear that such comments are not allowed unless a code change is required. Even if changelog clarity is important, the rules prioritize only actionable code changes, not editorial suggestions for changelogs. This comment should be deleted because it is not about a required code change and is purely informative/editorial.

Workflow ID: wflow_qMiN287PNFqxSTG3

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