chore(main): release 1.469.0

[rubenfiszel]

🤖 I have created a release beep boop

1.469.0 (2025-02-25)

Features

• limit the number of times a job can be restarted (3) after loss of pings (c8a9596)
• python-client now support mocked api via WM_MOCKED_API_FILE env (#5372) (50607c7)

Bug Fixes

• improve infinite grid behavior (56d1da7)

---

This PR was generated with Release Please. See documentation.

[cloudflare-workers-and-pages]

Deploying windmill with    Cloudflare Pages

Latest commit:	146027d
Status:	✅  Deploy successful!
Preview URL:	https://16c0cd2c.windmill.pages.dev
Branch Preview URL:	https://release-please--branches--ma.windmill.pages.dev

View logs

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 97efa45 in 23 seconds

More details

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

1. version.txt:1

• Draft comment:
  Version bump updated; ensure this aligns with release notes and Git tags.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

2. version.txt:1

• Draft comment:
  Version updated to 1.469.0 as expected. Confirm that downstream dependencies are updated accordingly.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

Workflow ID: wflow_lkyzA1E0KfWYj34e

---

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

[ellipsis-dev]

👍 Looks good to me! Incremental review on ba5c5fc in 1 minute and 17 seconds

More details

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

1. version.txt:1

• Draft comment:
  Version bump updated to 1.469.0. Ensure this change is in sync with your CHANGELOG and tag.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

2. version.txt:1

• Draft comment:
  Version bump to 1.469.0 looks correct. Confirm consistency with changelog and release tag.
• 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 consistency with the changelog and release tag, which is similar to asking them to double-check something. This violates the rule against asking the author to confirm or ensure things. It does not provide a specific code suggestion or ask for a specific test to be written.

3. CHANGELOG.md:10

• Draft comment:
  Typo alert: In the bullet point beginning with '* python-client now support mocked api via WM_MOCKED_API_FILE env', please change 'support' to 'supports' and 'mocked api' to 'mocked API' to ensure proper grammar and casing.
• 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%
  While the comment is technically correct about grammar and capitalization, changelogs are primarily for documenting changes, not for perfect grammar. The meaning is perfectly clear despite these minor issues. The rules specifically say not to make purely informative comments or obvious/unimportant ones.
  The grammar and capitalization issues could make the changelog look unprofessional. Documentation quality is important for open source projects.
  While documentation quality matters, these are extremely minor issues that don't impact understanding. The rules clearly state not to make obvious or unimportant comments.
  This comment should be deleted as it addresses minor grammatical issues that don't impact understanding and violates the rule about not making obvious or unimportant comments.

Workflow ID: wflow_uxvNfbgh7MImIctK

---

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

[ellipsis-dev]

👍 Looks good to me! Incremental review on 18ba4b9 in 1 minute and 34 seconds

More details

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

1. version.txt:1

• Draft comment:
  Version bump is correct; ensure it matches release documentation.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

2. version.txt:1

• Draft comment:
  Version bump updated to 1.469.0. Confirm that this increment aligns with the release strategy and tagging in your version control system.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

3. CHANGELOG.md:9

• Draft comment:
  Typographical issue: The sentence "python-client now support mocked api..." should read "python-client now supports mocked API via WM_MOCKED_API_FILE env..." to maintain subject-verb agreement and proper casing of "API".
• 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%
  The rules explicitly state to only comment if there's clearly a code change required. This is a purely informative comment about grammar in a documentation file. While technically correct, it's a minor issue that doesn't affect functionality or understanding. The rules emphasize focusing on substantive code issues rather than minor text corrections.
  The grammar issue could potentially affect readability and professionalism of the documentation. Some teams might value maintaining high standards even in changelog entries.
  While documentation quality is important, this is an extremely minor issue in a changelog that doesn't impact understanding. The rules clearly state not to make purely informative comments.
  This comment should be deleted as it's purely informative and doesn't require any meaningful code changes.

Workflow ID: wflow_nOKaMtKgFAHLMfNy

---

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

[ellipsis-dev]

👍 Looks good to me! Incremental review on 98ce158 in 32 seconds

More details

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

1. version.txt:1

• Draft comment:
  Version bump updated to '1.469.0'. Ensure this change remains consistent with other version references.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is related to a version bump, which falls under the category of dependency changes. The rules specify not to comment on pure dependency changes or library versions that are not recognized. Therefore, this comment should be removed as it violates the rules.

2. CHANGELOG.md:2

• Draft comment:
  Changelog entry for version 1.469.0 is correctly added; verify date and commit links.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is purely informative and asks the PR author to verify the date and commit links, which violates the rules. It does not provide a specific code suggestion or highlight a potential issue.

3. version.txt:1

• Draft comment:
  Version number updated to 1.469.0. Ensure this bump is consistent with the changelog and related release process.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

4. CHANGELOG.md:10

• Draft comment:
  Typo: In the Features section, update 'python-client now support mocked api' to 'python-client now supports mocked API'. This improves grammatical correctness.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is purely informative and suggests a minor correction in the documentation. It does not provide a code suggestion or address a potential issue in the code itself. According to the rules, purely informative comments should be removed.

Workflow ID: wflow_yRMwu2DA3miZy17X

---

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

[ellipsis-dev]

👍 Looks good to me! Incremental review on 0166866 in 1 minute and 15 seconds

More details

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

1. version.txt:1

• Draft comment:
  Version bump updated correctly.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

2. version.txt:1

• Draft comment:
  Version bump to 1.469.0 looks correct. Confirm that the newline after the version number is intentional per our file formatting standards.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

3. CHANGELOG.md:8

• Draft comment:
  Typographical error: In the changelog bullet point, consider changing 'python-client now support mocked api via WM_MOCKED_API_FILE env' to 'python-client now supports mocked API via WM_MOCKED_API_FILE env' for improved grammar and consistency.
• 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%
  While the grammar correction is technically accurate, changelogs are primarily for documenting changes, not for perfect grammar. The meaning is perfectly clear despite the minor errors. The rules specifically say not to make purely informative comments or unimportant ones. This seems like an unnecessary nitpick that doesn't affect functionality.
  Perhaps maintaining consistent and professional documentation is important for project quality. Grammar errors could make the project look unprofessional.
  While professional documentation is valuable, this minor grammar issue doesn't significantly impact readability or understanding. The rules explicitly state to avoid obvious or unimportant comments.
  Delete this comment as it's purely informative and doesn't require any meaningful code changes. It's too minor to warrant attention in a code review.

Workflow ID: wflow_rHYU4LbKVaYGIfZv

---

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

[ellipsis-dev]

👍 Looks good to me! Incremental review on df82e76 in 58 seconds

More details

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

1. version.txt:1

• Draft comment:
  Version bump to 1.469.0 is correct; no issues found.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

2. version.txt:1

• Draft comment:
  Version bump in version.txt updated to 1.469.0 as expected. Confirm that this aligns with your release process.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

3. CHANGELOG.md:9

• Draft comment:
  Typo: 'python-client now support mocked api via...' should be 'python-client now supports mocked API via...'. Please fix the grammar and acronym capitalization.
• 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%
  While the comment is technically correct about the grammar and capitalization, changelogs are primarily for documenting changes and their meaning. Small grammatical issues don't impact the understanding of what changed. The rules specifically say not to make purely informative comments that don't require clear code changes.
  The grammar mistake could make the project look unprofessional. Documentation quality is important for user experience.
  While documentation quality matters, this is a minor issue that doesn't affect functionality or understanding. The meaning is perfectly clear despite the small grammatical error.
  This comment should be removed as it's a minor grammatical issue that doesn't impact the understanding of the changelog entry and doesn't require a meaningful code change.

Workflow ID: wflow_564GknkzNIrnBmQa

---

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

[ellipsis-dev]

👍 Looks good to me! Incremental review on a7b4e13 in 1 minute and 3 seconds

More details

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

1. version.txt:1

• Draft comment:
  Version number correctly updated to 1.469.0.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

2. version.txt:1

• Draft comment:
  Version bump updated to 1.469.0 appears correct. Ensure consistency with changelog and other version references.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

3. CHANGELOG.md:9

• Draft comment:
  In the bullet point "python-client now support mocked api via WM_MOCKED_API_FILE env", consider changing 'support' to 'supports' for correct grammar. Additionally, 'api' might be capitalized to 'API' for consistency.
• 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%
  Changelogs are meant to communicate changes to users. While grammar should be correct, making minor grammar corrections in changelog entries is not a valuable use of review comments. These small issues don't impact understanding and don't require code changes. Additionally, we're told not to make purely informative comments or comments about obvious/unimportant things.
  The grammar issue could make the changelog look unprofessional. Consistent capitalization of technical terms like API is a common best practice.
  While professionalism matters, these are extremely minor issues that don't impact functionality or understanding. The comment adds noise to the review process without providing significant value.
  Delete this comment as it's purely about minor grammar/style in documentation and doesn't highlight any significant issues that need addressing.

Workflow ID: wflow_ugqGr74vxJZoRQIJ

---

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

[ellipsis-dev]

👍 Looks good to me! Incremental review on f65bdff in 1 minute and 34 seconds

More details

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

1. version.txt:1

• Draft comment:
  Version bump looks correct.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

2. version.txt:1

• Draft comment:
  Version bump to 1.469.0 looks correct. Ensure this version is in sync with release tags and that the file ends with a newline.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

3. CHANGELOG.md:9

• Draft comment:
  Typo: Change 'python-client now support mocked api via WM_MOCKED_API_FILE env' to 'python-client now supports mocked API via WM_MOCKED_API_FILE env' for correct grammar.
• 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%
  While the grammar correction is technically accurate, changelogs are primarily for documenting changes and their impact. Minor grammatical issues don't affect the understanding of what changed. The meaning is perfectly clear despite the small grammar mistake. This seems like an unnecessary nitpick that doesn't add value.
  The grammar error could potentially make the project look unprofessional. Documentation quality is important for open source projects.
  While documentation quality matters, this is a very minor issue that doesn't impact comprehension. The changelog serves its primary purpose of communicating the change clearly.
  Delete this comment as it's too minor and doesn't require a code change. It's purely about grammar in documentation.

Workflow ID: wflow_5Ln4VDv1QP01kR3G

---

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