Skip to content

chore(main): release 1.881.0 - #12554

Merged
rubenfiszel merged 2 commits into
mainfrom
release-please--branches--main--components--windmill
Nov 20, 2026
Merged

rubenfiszel merged 2 commits into
mainfrom
release-please--branches--main--components--windmill

Conversation

@rubenfiszel

@rubenfiszel rubenfiszel commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.881.0 (2026-11-20)

Features

  • fill argument descriptions from JSDoc @param and Python Args: (#12515) (2eddc5d)
  • give the chat's deploy confirmation a card of its own (#12571) (c8d0479)
  • hide items from home's recently run panel (#12572) (64995fa)
  • hub: publish a folder's AI agents with their project (#12490) (4fd4b04)
  • lead the run graph's error handler to the node that receives its output (#12516) (6ec19f0)
  • let a subflow step override its worker tag (#12556) (7f5bdee)
  • outline an expanded subflow on hover and selection (#12560) (1d38a6b)
  • show selection actions in the flow canvas right-click menu (#12561) (775c371)

Bug Fixes

  • cli: show the workspace commands actually target in workspace list (#12464) (5819ced)
  • enforce access checks on cancel_persistent and flow_dependencies (#12551) (42c9cdd)
  • hand flow previews on an agent's tag to a flow worker (#12563) (e061d11)
  • list running jobs in the inputs history of an older script version (#12493) (8ee2a7e)
  • relax git auto-pull polling only once the webhook has delivered (#12532) (d538f2a)
  • reload the npmrc and cargo_registries settings without a restart (#12569) (a932614)
  • resolve scoped packages in the npm proxy behind strict registries (#12568) (cdba6b0)
  • respect minimal telemetry on manual stats send and download (#12570) (a44f315)
  • retries, subflow error handlers and empty branches in the run graph (#12511) (fb13514)
  • send null for untouched nullable inputs in run forms (#12553) (666f3e5)
  • session chat shows its own workspace's AI config (#12573) (8b3b692)
  • store an artifact edit only when made on its latest version (#12477) (a8f7c56)

Performance Improvements

  • keep only the open session's column off the sessions route (#12558) (d23f4d4)

This PR was generated with Release Please. See documentation.

@claude

claude Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @rubenfiszel's task in 24s —— View job


Good to merge

Review of release PR 1.880.2

  • Read the diff against origin/main
  • Checked the release-please config and the version bump

This is a release-please PR, and the diff is what one should look like:

  • .release-please-manifest.json: version goes from 1.880.1 to 1.880.2.
  • version.txt: same bump, 1.880.1 to 1.880.2. release-please-config.json uses release-type: simple, so version.txt is the only version file it should touch.
  • CHANGELOG.md: the new 1.880.2 entry lists the single fix since 1.880.1, fix: enforce access checks on cancel_persistent and flow_dependencies #12551 (42c9cdd). The compare link (v1.880.1...v1.880.2) and the date are correct.

I found no P0, P1 or P2 issues.

Test coverage

This PR only changes release metadata and docs, so it needs no automated tests and has nothing to exercise in the app. The fix being released, the access checks from #12551, was reviewed in its own PR.

@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is a release-please PR for 1.880.2. The diff contains only release metadata and is exactly what the release-type: simple configuration should produce:

Considered and dismissed

  • Version consistency across files — .release-please-manifest.json, version.txt, and the CHANGELOG.md heading all agree on 1.880.2. No mismatch.
  • CHANGELOG references the correct commit — the linked commit 42c9cdd is exactly the base SHA of this PR (the release-please cutoff), so the changelog is pointing at the right fix.
  • Extra version files left stale — checked release-please-config.json: release-type: simple, include-component-in-tag: false, so version.txt + manifest + changelog are the complete set of files this PR should touch. Nothing else in the repo carries a hardcoded 1.880.1 version that this PR failed to bump (verified the diff touches only the three expected files).
  • Code changes hidden in the release commit — git log for the range shows a single commit (chore(main): release 1.880.2), and the underlying fix (fix: enforce access checks on cancel_persistent and flow_dependencies #12551) was reviewed in its own PR.

Test coverage

This PR is release metadata / docs only — no automated tests are expected, and there is no in-app surface to exercise. The bug fix being released (access checks on cancel_persistent and flow_dependencies) was reviewed separately in #12551.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

Deploying windmill with  Cloudflare Pages  Cloudflare Pages

Latest commit: c1b6aed
Status:⚡️  Build in progress...

View logs

@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is an automated release-please PR for v1.880.2. The diff is exactly what the repo's release process should produce: a chore(main): release commit plus an "Apply automatic changes" commit driven by .github/workflows/change-versions.yml (which runs .github/change-versions.sh and cargo generate-lockfile).

  • .release-please-manifest.json and version.txt: 1.880.1 → 1.880.2.
  • All version-bearing files the script touches are bumped to 1.880.2 (Cargo.toml, both Cargo.locks, openapi.yaml, openflow.openapi.yaml, cli constants, benchmarks/lib.ts, frontend/chat-sdk/typescript-client/python-client/powershell-client/yaml-validator/lsp package files, pyproject.toml, Pipfile, psd1). A repo-wide grep confirms no stray 1.880.1 remains outside ignored/vendor paths.
  • CHANGELOG.md: correct new entry listing the single fix (fix: enforce access checks on cancel_persistent and flow_dependencies #12551), correct compare link (v1.880.1...v1.880.2), correct commit link (42c9cdd…, the base SHA and the fix's merge commit).

Considered and dismissed

  • Lockfile dependency upgrades bundled into the release — backend/Cargo.lock also bumps clap 4.6.8→4.6.9, serde_with 3.24.0→3.25.0, and adds jiff 1.0.1 as a new transitive dep. This is the expected output of the cargo generate-lockfile step in the pre-existing change-versions.yml workflow, not a change made by this PR's author. The direct-dep changes are semver-compatible patch/minor bumps, and windmill-common still resolves jiff 0.2.46 directly (1.0.1 rides in only via serde_with), so no behavioral change to Windmill's own jiff usage. This is pre-existing release-process behavior, so it is not a finding against this PR.
  • Version consistency across all files — manifest, version.txt, both workspaces' Cargo.toml/lockfiles, and every client/lsp package all agree on 1.880.2; the windmill-* entries in Cargo.lock were all updated to 1.880.2. No mismatch.
  • Changelog referencing the wrong commit / date — the linked 42c9cdd is exactly the base SHA of this PR (the fix being released), and the date matches the release commit. Correct.
  • Missing bump in a file outside the script's list — grep across all .json/.toml/.txt/.yaml/.yml/.ts/.py/.psd1/lockfiles found no remaining 1.880.1, so nothing was missed.
  • Code changes hidden in the release commit — git log for the range shows only chore(main): release 1.880.2 and Apply automatic changes; the actual fix (access checks on cancel_persistent / flow_dependencies) landed separately in fix: enforce access checks on cancel_persistent and flow_dependencies #12551 and was reviewed there.

Test coverage

This PR is release metadata, version bumps, and generated lockfiles only — no automated tests are expected, and there is no in-app surface to exercise. The bug fix being released was reviewed in its own PR (#12551); nothing in this PR needs manual verification beyond CI confirming the versioned artifacts build.

@github-actions

Copy link
Copy Markdown
Contributor

Codex Review

Good to merge

Reviewed the full 22-file diff, including the automatic changes. Release versions consistently advance to 1.880.2. The Rust lockfile also updates clap and serde_with and adds Jiff 1.x alongside the existing 0.2 dependency. No definite introduced issues found.

Test coverage

No new automated tests are expected for the release metadata. Existing backend builds and tests should validate the Rust dependency refresh; I did not run them. git diff --check passed.

There is no new in-app surface. Manual release verification remains: start the built artifacts and confirm normal startup and the reported 1.880.2 version.

@rubenfiszel
rubenfiszel force-pushed the release-please--branches--main--components--windmill branch from e24e5be to 251b1fc Compare November 20, 2026 07:44
@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is a release-please PR for v1.880.2 (release-type: simple), and the diff is exactly what the release process should produce — a single chore(main): release 1.880.2 commit touching only three files:

  • .release-please-manifest.json: 1.880.1 → 1.880.2.
  • version.txt: 1.880.1 → 1.880.2.
  • CHANGELOG.md: new 1.880.2 entry with correct compare link (v1.880.1...v1.880.2), correct date (2026-11-20), and both fixes released since 1.880.1.

Considered and dismissed

  • Changelog lists the correct set of fixes — the entry lists two bug fixes: fix: enforce access checks on cancel_persistent and flow_dependencies #12551 (enforce access checks on cancel_persistent and flow_dependencies, commit 42c9cdd) and fix: send null for untouched nullable inputs in run forms #12553 (send null for untouched nullable inputs in run forms, commit 666f3e5). git log confirms both commits landed after the 1.880.1 release commit (66262f3, chore(main): release 1.880.1 #12552) and before this release, and 666f3e5 is exactly this PR's base SHA. Correct — earlier reviewers' "single fix" phrasing was simply wrong, not a defect in the PR.
  • Version consistency across files — manifest, version.txt, and the changelog heading all agree on 1.880.2. No mismatch.
  • Other version-bearing files not bumped (Cargo.toml, Cargo.lock, package.json, etc.) — release-please-config.json uses release-type: simple with include-component-in-tag: false, so version.txt + manifest + changelog are the complete set of files this step is expected to touch. The broader version-propagation is a separate post-release workflow, not part of this PR's range.
  • Commit links and compare URL — 42c9cdd0dc81b1e9a41d710cdeda5fe7ff27a40f and 666f3e5577a573da3ce6a72d65d625ed1a523f92 are both verified real commits; the compare link resolves to the correct tag range.
  • Code changes hidden in the release commit — git log for the range shows only the single release commit; both underlying fixes were reviewed in their own PRs (fix: enforce access checks on cancel_persistent and flow_dependencies #12551, fix: send null for untouched nullable inputs in run forms #12553).

Test coverage

This PR is release metadata / changelog only — no automated tests are expected, and there is no in-app surface to exercise. The bug fixes being released were reviewed separately in #12551 and #12553. No manual verification is needed beyond CI confirming the tagged artifacts build.

@github-actions

Copy link
Copy Markdown
Contributor

Codex Review

Good to merge

No introduced issues found in the exact three-file diff. The manifest, version.txt, and changelog agree on 1.880.2; both referenced fixes are included in the reviewed head.

Test coverage

No new automated tests are expected for release metadata and documentation. Read-only version consistency checks and git diff --check passed. Builds and tests were not run.

There is no in-app surface to exercise, and no additional manual verification is needed for this diff.

@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is an automated release-please PR for v1.880.2 (release-type: simple, include-component-in-tag: false), and the diff is exactly what the release process should produce. The range contains two commits:

  • 251b1fc9f6 (chore(main): release 1.880.2) — release-please's own commit, touching only the three files it owns: .release-please-manifest.json, version.txt, and CHANGELOG.md.
  • 03f50f358e (Apply automatic changes) — the output of the pre-existing .github/workflows/change-versions.yml, which runs .github/change-versions.sh and cargo generate-lockfile.

Verified specifics:

  • Version consistency — .release-please-manifest.json, version.txt, both Cargo.toml files (backend + parser-wasm), openapi.yaml, openflow.openapi.yaml, benchmarks/lib.ts, cli/src/core/constants.ts, all package.json/package-lock.json files (chat-sdk, frontend, typescript-client, windmill-yaml-validator), jsr.json, pyproject.toml, lsp/Pipfile, and WindmillClient.psd1 all agree on 1.880.2. A repo-wide grep finds no stray 1.880.1 outside ignored/vendor paths.
  • CHANGELOG entry — correctly lists both fixes shipped since 1.880.1 (fix: enforce access checks on cancel_persistent and flow_dependencies #12551 and fix: send null for untouched nullable inputs in run forms #12553), with the compare link (v1.880.1...v1.880.2), the date (2026-11-20), and both commit links (42c9cdd and 666f3e5, the latter being this PR's base SHA).

Considered and dismissed

  • Lockfile dependency bumps bundled into the release — backend/Cargo.lock bumps clap 4.6.8→4.6.9 and serde_with 3.24.0→3.25.0, and adds jiff 1.0.1 (plus its jiff-core/jiff-static/jiff-tzdb family) as a new transitive dependency. This is the expected output of the cargo generate-lockfile step in the pre-existing change-versions.yml workflow, not a change made by this PR's author. The bumps are semver-compatible patch/minor releases, and I confirmed serde_with 3.25.0 pulls jiff 1.0.1 transitively while windmill-common still resolves jiff 0.2.46 directly (both coexist in the lockfile), so Windmill's own jiff usage is unchanged. Not a finding.
  • CHANGELOG listing the wrong set of fixes — verified against git log: both 42c9cdd (fix: enforce access checks on cancel_persistent and flow_dependencies #12551) and 666f3e5 (fix: send null for untouched nullable inputs in run forms #12553) landed after the v1.880.1 release and before this release; 666f3e5 is exactly this PR's base SHA. The entry is complete and correct.
  • Version-bearing files left stale — grep across .toml/.json/.txt/.yaml/.yml/.ts/.py/.psd1/lockfiles found no remaining 1.880.1; the full set of files touched matches what change-versions.sh is expected to rewrite. Nothing missed.
  • Code changes hidden in the release commit — the range contains only the two release-process commits; the actual fixes (fix: enforce access checks on cancel_persistent and flow_dependencies #12551, fix: send null for untouched nullable inputs in run forms #12553) were reviewed in their own PRs and are not part of this diff.

Test coverage

This PR is release metadata, version bumps, and regenerated lockfiles only — no automated tests are expected, and there is no in-app surface to exercise. The bug fixes being released were reviewed separately in #12551 and #12553. No manual verification is needed beyond CI confirming the versioned artifacts build and startup reports 1.880.2.

@github-actions

Copy link
Copy Markdown
Contributor

Codex Review

Good to merge

No introduced issues found in the authoritative 22-file diff. Release versions consistently advance to 1.880.2; the generated Rust lockfile also refreshes clap and serde_with and adds Jiff 1.x alongside 0.2.

Test coverage

No new automated tests are expected for release metadata and generated lockfiles. Read-only version consistency, JSON/TOML parsing, changelog commit ancestry, and git diff --check passed. Builds and tests were not run; existing CI should validate the refreshed Rust dependencies.

There is no changed in-app surface, and no additional manual scenarios are needed.

@rubenfiszel
rubenfiszel force-pushed the release-please--branches--main--components--windmill branch from 03f50f3 to ae87db8 Compare November 20, 2026 10:01
@github-actions

Copy link
Copy Markdown
Contributor

Codex Review

Good to merge

No introduced issues found in the exact 22-file range d23f4d4...c001dd4. Release versions consistently advance to 1.880.2; the changelog matches the included commits. The remaining changes refresh generated Rust dependencies.

Test coverage

No new automated tests are expected for release metadata and version propagation. Read-only JSON/TOML parsing, version consistency, changelog ancestry, and git diff --check passed.

Builds and tests were not run; existing CI should validate the Rust dependency refresh. There is no changed in-app surface and no additional manual scenario needed.

@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is an automated release-please PR for v1.880.2, and the diff is exactly what the repo's release process should produce — two commits (chore(main): release 1.880.2 and Apply automatic changes) touching 22 files: version bumps across all version-bearing files, a CHANGELOG.md entry, and regenerated lockfiles.

Verified specifics:

Considered and dismissed

  • serde_with 3.24.0 → 3.25.0 pulls jiff 1.0.1 in transitively (backend/Cargo.lock) — the only substantive non-version change in the diff. I traced it: serde_with is not a direct dependency of any Windmill crate (no serde_with reference in any backend/**/Cargo.toml); it is pulled only transitively by bollard-stubs and openidconnect. Windmill's own code does not use serde_with at all (windmill-common/windmill-api sources contain no reference), and windmill-common's direct jiff dependency still resolves to jiff 0.2.46 unchanged. The jiff 1.0.1 copy is inert for Windmill's serialization paths — it only adds a second jiff to the build graph, and serde_with 3.25.0's jiff integration is feature-gated code that Windmill never invokes. No functional impact.
  • clap 4.6.8 → 4.6.9 — semver-compatible patch bump; no behavior change.
  • Lockfile regenerated without --locked — this is the pre-existing cargo generate-lockfile step in .github/workflows/change-versions.yml, not a decision made in this PR; the refreshed transitive deps (all patch/minor, semver-compatible) are validated by CI before the release publishes.
  • Changelog listing the wrong set of fixes / wrong commit — verified the three listed commits all landed after v1.880.1 and are included in this range; 666f3e5 and d23f4d4 are this PR's own base SHA, so the entry is complete and correct.

Test coverage

This PR is release metadata, version bumps, and regenerated lockfiles only — no automated tests are expected, and there is no in-app surface to exercise. The bug fixes being released (#12551, #12553) were reviewed in their own PRs. No manual verification is needed beyond CI confirming the versioned artifacts build and the binary reports 1.880.2 at startup.

@rubenfiszel rubenfiszel changed the title chore(main): release 1.880.2 chore(main): release 1.881.0 Nov 20, 2026
@rubenfiszel
rubenfiszel force-pushed the release-please--branches--main--components--windmill branch from c001dd4 to 8ea487a Compare November 20, 2026 10:08
@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is an automated release-please PR for v1.881.0. The diff is exactly what the repo's release config should produce: one chore(main): release 1.881.0 commit touching only the three files release-type: simple owns — .release-please-manifest.json, version.txt, and CHANGELOG.md.

Verified specifics:

Considered and dismissed

Test coverage

This PR is release metadata and changelog only — no automated tests are expected, and there is no in-app surface to exercise. The changes being released were reviewed in their own PRs. No manual verification is needed beyond CI confirming the tagged artifacts build and the binary reports 1.881.0 at startup.

@github-actions

Copy link
Copy Markdown
Contributor

Codex Review

Good to merge

No introduced issues found in the exact three-file diff. The manifest, version.txt, and changelog consistently advance to 1.881.0; all four referenced commits are included in the release’s ancestry.

Test coverage

No automated tests are expected for release metadata and documentation. JSON parsing, version consistency, changelog commit ancestry, and git diff --check passed. Builds and tests were not run.

There is no changed in-app surface to exercise, and no additional manual verification is needed for this diff.

@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is an automated release-please PR for v1.881.0 (release-type: simple, include-component-in-tag: false). The range contains two commits — 8ea487a077 (chore(main): release 1.881.0) and 6f90203e51 (Apply automatic changes) — and the diff is exactly what the release process should produce.

Verified specifics:

Considered and dismissed

  • backend/Cargo.lock dependency refresh (clap 4.6.8→4.6.9, serde_with 3.24.0→3.25.0, new transitive jiff 1.0.1) — the only substantive non-version change. This is the expected output of the cargo generate-lockfile step in the pre-existing .github/workflows/change-versions.yml, not an author decision. The bumps are semver-compatible patch/minor releases; serde_with is not a direct Windmill dependency (pulled only via bollard-stubs/openidconnect), and windmill-common's own direct jiff still resolves to 0.2.46. The jiff 1.0.1 copy is inert for Windmill's code. Not a finding.
  • Commits in the range absent from the changelog — non-conventional commit subjects (show workspace fairness settings…, show the fairness reserve toggle…) without feat:/fix: prefixes are correctly excluded by release-please. Expected, not a defect.
  • [@param](https://github.com/param) autolink and trailing "Python Args:" — cosmetic release-please output derived from the original commit message; no author-introduced issue.
  • Code changes hidden in the release commit — git log shows only the two release-process commits; the underlying changes were reviewed in their own PRs (feat: fill argument descriptions from JSDoc @param and Python Args: #12515, fix: enforce access checks on cancel_persistent and flow_dependencies #12551, fix: send null for untouched nullable inputs in run forms #12553, perf: keep only the open session's column off the sessions route #12558).

Test coverage

This PR is release metadata, version bumps, and regenerated lockfiles only — no automated tests are expected, and there is no in-app surface to exercise. The changes being released were reviewed in their own PRs. No manual verification is needed beyond CI confirming the versioned artifacts build and the binary reports 1.881.0 at startup.

@github-actions

Copy link
Copy Markdown
Contributor

Codex Review

Good to merge

No introduced issues found in the full 22-file range 8dc728e...6f90203, including the automatic changes. Release versions consistently advance to 1.881.0; the Rust lockfile refresh preserves Windmill’s direct Jiff 0.2 dependency.

Test coverage

No new automated tests are expected for release metadata and generated lockfiles. Read-only JSON/TOML parsing, version consistency, changelog ancestry, and git diff --check passed. Builds and tests were not run; existing CI should validate the refreshed Rust dependencies.

There is no changed in-app surface. Manual release verification remains: start the built artifacts and confirm normal startup and the reported 1.881.0 version.

@rubenfiszel
rubenfiszel force-pushed the release-please--branches--main--components--windmill branch 2 times, most recently from d6151c1 to 1864fd0 Compare November 20, 2026 11:12
@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is an automated release-please PR for v1.881.0 (release-type: simple, include-component-in-tag: false). The range contains a single commit (1864fd0 chore(main): release 1.881.0) touching exactly the three files the config owns: .release-please-manifest.json, version.txt, and CHANGELOG.md.

Verified specifics:

Considered and dismissed

Test coverage

This PR is release metadata and changelog only — no automated tests are expected, and there is no in-app surface to exercise. No manual verification is needed beyond CI confirming the tagged artifacts build and the binary reports 1.881.0 at startup.

@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is an automated release-please PR for v1.881.0 (release-type: simple, include-component-in-tag: false). The range contains two commits — 1864fd0 (chore(main): release 1.881.0) and 84ceed1 (Apply automatic changes) — and the diff is exactly what the release process should produce: version bumps across all version-bearing files, a CHANGELOG.md entry, and regenerated lockfiles.

Verified specifics:

Considered and dismissed

Test coverage

This PR is release metadata, version bumps, and regenerated lockfiles only — no automated tests are expected, and there is no in-app surface to exercise. The changes being released were reviewed in their own PRs. No manual verification is needed beyond CI confirming the versioned artifacts build and the binary reports 1.881.0 at startup.

@github-actions

Copy link
Copy Markdown
Contributor

Codex Review

Good to merge

No introduced issues found in the exact 22-file range e061d11...84ceed1. Release versions consistently advance to 1.881.0, and all six changelog entries match included commits. The Rust lockfile refresh preserves Windmill’s direct Jiff 0.2 dependency.

Test coverage

No new automated tests are expected for release metadata and generated lockfiles. Read-only JSON/TOML parsing, version consistency, changelog ancestry, and git diff --check passed. Builds and tests were not run; existing CI should validate the refreshed Rust dependencies.

There is no changed in-app surface. Manual release verification remains: start the built artifacts and confirm normal startup and the reported 1.881.0 version.

@rubenfiszel
rubenfiszel force-pushed the release-please--branches--main--components--windmill branch 3 times, most recently from 0e28630 to 199b01f Compare November 20, 2026 12:59
@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is an automated release-please PR for v1.881.0 (release-type: simple, include-component-in-tag: false). The range a8f7c56...5f7412b contains a single commit (5f7412b30a chore(main): release 1.881.0) touching exactly the three files the config owns: .release-please-manifest.json, version.txt, and CHANGELOG.md. No source code is in the diff.

Verified specifics:

Considered and dismissed

  • Commits in the range absent from the changelog — b08a2aada1 (show fairness reserve toggle) and 8dc728ec99 (show fairness settings) carry no conventional prefix, while 554cfd0620 (chore: remove the akeyless icon), 67b1f15a63 (chore: bump windmill-parser-wasm-ts and -csharp), and b8a24bdd5c (rebuild std) are non-feat:/fix:/perf:. Release-please correctly excludes all five. Not a defect.
  • #12477 listed despite being this PR's base SHA — a8f7c56 is the fix: commit for fix: store an artifact edit only when made on its latest version #12477, which landed before the release commit, so it belongs in the entry. Correct inclusion, not an off-by-one error.
  • [@param](https://github.com/param) autolink and the trailing "Python Args:" in the changelog — release-please autolinks the literal @param in the source commit subject to a GitHub user and carries the trailing colon verbatim; cosmetic release-process output derived from the commit message, not an author-introduced issue.
  • Other version-bearing files not bumped (Cargo.toml, Cargo.lock, package.json, etc.) — release-please-config.json uses release-type: simple with include-component-in-tag: false, so version.txt + manifest + changelog are the complete set this step touches; the broader version propagation is a separate post-release workflow outside this PR's range. Confirmed the diff touches only the three expected files.
  • Code changes hidden in the release commit — git log for the range shows only the single release commit; the underlying changes were reviewed in their own PRs.

Test coverage

This PR is release metadata and changelog only — no automated tests are expected, and there is no in-app surface to exercise. The changes being released were reviewed in their own PRs. No manual verification is needed beyond CI confirming the tagged artifacts build and the binary reports 1.881.0 at startup.

@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is an automated release-please PR for v1.881.0 (release-type: simple, include-component-in-tag: false). The range a8f7c56...15abdf69 contains two commits — 5f7412b3 (chore(main): release 1.881.0) and 15abdf69 (Apply automatic changes) — and the diff is exactly what the release process should produce: a CHANGELOG.md entry, version bumps across all version-bearing files, and regenerated lockfiles. No source code (*.rs/*.svelte/*.py/*.go) is touched.

Verified specifics:

Considered and dismissed

  • backend/Cargo.lock dependency refresh (clap 4.6.8→4.6.9, clap_derive 4.6.8→4.6.9, cc 1.11.2→1.11.3, serde_with 3.24.0→3.25.0, new transitive jiff 1.0.1 family) — the only substantive non-version change. This is the expected output of the cargo generate-lockfile step in the pre-existing .github/workflows/change-versions.yml, not an author decision. I confirmed jiff 0.2.46 (windmill-common's direct dependency) is still resolved in the lockfile unchanged; the jiff 1.0.1 copy rides in only transitively via serde_with, which is not a direct dependency of any backend/**/Cargo.toml. No functional impact. The windmill-parser-wasm/Cargo.lock diff is pure 1.880.1 → 1.881.0 version bumps.
  • Stray 1.880.1 remaining in the tree — a git grep at the head finds it only in the windmill-parser-wasm-ts/windmill-parser-wasm-csharp pins in cli/package.json, frontend/package.json and frontend/package-lock.json (a separate package with its own release cycle, bumped to 1.880.1 by chore: bump the ts and csharp wasm parsers to 1.880.1 #12565), plus the CHANGELOG compare link and previous release heading (both correct). No Windmill version itself is left unbumped. Not a finding.
  • Commits in range absent from the changelog — 67b1f15a (chore: bump windmill-parser-wasm-ts and -csharp), 554cfd06 (chore: remove the akeyless icon), and the three non-conventional subjects (b8a24bdd rebuild std, 8dc728ec show fairness settings, b08a2aad show fairness reserve toggle) all sit inside the range but carry no feat:/fix:/perf: prefix, so release-please correctly excludes them. Not a defect.
  • #12477 listed despite being this PR's base SHA — a8f7c56 is the fix: commit for fix: store an artifact edit only when made on its latest version #12477, which landed before the release commit, so it belongs in the entry. Correct inclusion, not an off-by-one error.
  • [@param](https://github.com/param) autolink and the trailing "Python Args:" in the changelog — release-please autolinks the literal @param in the source commit subject to a GitHub user and carries the trailing colon verbatim; cosmetic release-process output derived from the commit message, not an author-introduced issue.
  • Code changes hidden in the release commit — git log for the range shows only the two release-process commits; the underlying changes were reviewed in their own PRs.

Test coverage

This PR is release metadata, version bumps, and regenerated lockfiles only — no automated tests are expected, and there is no in-app surface to exercise. The changes being released were reviewed in their own PRs (#12515, #12490, #12556, #12560, #12561, #12551, #12563, #12493, #12569, #12568, #12570, #12511, #12553, #12477, #12558). No manual verification is needed beyond CI confirming the versioned artifacts build and the binary reports 1.881.0 at startup.

@github-actions

Copy link
Copy Markdown
Contributor

Codex Review

Good to merge

No introduced issues found in the exact 22-file diff a8f7c56...15abdf6. Release versions consistently advance to 1.881.0, and all 15 changelog entries match the release ancestry.

Test coverage

No new automated tests are expected for release metadata and generated lockfiles. JSON/TOML parsing, version consistency, lockfile references, changelog ancestry, and git diff --check passed.

Builds and tests were not run; existing CI should validate the Rust dependency refresh. There is no changed in-app surface. Manual release verification should confirm the built artifacts start normally and report 1.881.0.

@rubenfiszel
rubenfiszel force-pushed the release-please--branches--main--components--windmill branch from 15abdf6 to c91f9c9 Compare November 20, 2026 15:52
@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is an automated release-please PR for v1.881.0 (release-type: simple, include-component-in-tag: false). The range c8d047905e...c91f9c91da contains a single commit (c91f9c91da chore(main): release 1.881.0) touching exactly the three files the config owns: .release-please-manifest.json, version.txt, and CHANGELOG.md. No source code is in the diff.

Verified specifics:

Considered and dismissed

  • Commits in the range absent from the changelog — b08a2aada1 (show the fairness reserve toggle only when it can matter), 8dc728ec99 (show workspace fairness settings and events only when relevant), b8a24bdd5c (rebuild std for the tree-sitter wasm parsers) carry no conventional prefix, and 554cfd0620 / 67b1f15a63 are chore:. None carry a feat:/fix:/perf: prefix, so release-please correctly excludes them. Not a defect.
  • #12571 listed despite being this PR's base SHA — c8d047905e is the feat: commit for feat: give the chat's deploy confirmation a card of its own #12571, which landed before the release commit, so it belongs in the entry. Correct inclusion, not an off-by-one error.
  • [@param](https://github.com/param) autolink and the trailing "Python Args:" — release-please autolinks the literal @param in the source commit subject to a GitHub user and carries the trailing colon verbatim. Cosmetic release-process output derived from the commit message, not an author-introduced issue.
  • Other version-bearing files not bumped (Cargo.toml, Cargo.lock, package.json, openapi.yaml, etc.) — .release-please-config.json uses release-type: simple with include-component-in-tag: false, so version.txt + manifest + changelog are the complete set this step touches; the broader version propagation is a separate post-release workflow outside this PR's range. Confirmed the diff touches only the three expected files.
  • Code changes hidden in the release commit — git log for the range shows only the single release commit; the underlying changes were reviewed in their own PRs.

Test coverage

This PR is release metadata and changelog only — no automated tests are expected, and there is no in-app surface to exercise. The changes being released were reviewed in their own PRs. No manual verification is needed beyond CI confirming the tagged artifacts build and the binary reports 1.881.0 at startup.

@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is an automated release-please PR for v1.881.0 (release-type: simple, include-component-in-tag: false). The range c8d047905e...3353df253f contains two commits — c91f9c91da (chore(main): release 1.881.0) and 3353df253f (Apply automatic changes) — and the diff is exactly what the release process should produce: a CHANGELOG.md entry, version bumps across all version-bearing files, and regenerated lockfiles. No source code (*.rs/*.svelte/*.py/*.go) is touched.

Verified specifics:

Considered and dismissed

  • backend/Cargo.lock dependency refresh (cc 1.11.2→1.11.3, clap/clap_derive 4.6.8→4.6.9, serde_with 3.24.0→3.25.0, new transitive jiff 1.0.1 family) — the only substantive non-version change. This is the expected output of the cargo generate-lockfile step in the pre-existing .github/workflows/change-versions.yml, not an author decision. I confirmed jiff 0.2.46 (windmill-common's direct dependency) is still resolved in the lockfile unchanged, and the jiff 1.0.1 copy rides in only transitively via serde_with; serde_with is not a direct dependency of any backend/**/Cargo.toml, and its jiff integration is feature-gated code Windmill never invokes. No functional impact.
  • Stray 1.880.1 remaining in the tree — a git grep at the head finds it only in the windmill-parser-wasm-ts/windmill-parser-wasm-csharp pins in cli/package.json/cli/bun.lock/frontend/package.json/frontend/package-lock.json (a separate package with its own release cycle, bumped to 1.880.1 by chore: bump the ts and csharp wasm parsers to 1.880.1 #12565), the CHANGELOG compare link and previous release heading (both correct), and frontend/src/lib/components/copilot/chat/flow/openFlow.json (a fixture). No Windmill version itself is left unbumped.
  • Commits in range absent from the changelog — 67b1f15a63 and 554cfd0620 (chore:), and the three non-conventional subjects (b8a24bdd5c rebuild std, 8dc728ec99 show fairness settings, b08a2aada1 show fairness reserve toggle) all sit inside the range but carry no feat:/fix:/perf: prefix, so release-please correctly excludes them.
  • #12571 listed despite being this PR's base SHA — c8d047905e is the feat: commit for feat: give the chat's deploy confirmation a card of its own #12571, which landed before the release commit, so it belongs in the entry. Correct inclusion, not an off-by-one error.
  • [@param](https://github.com/param) autolink and the trailing "Python Args:" in the changelog — release-please autolinks the literal @param in the source commit subject to a GitHub user and carries the trailing colon verbatim; cosmetic release-process output derived from the commit message, not an author-introduced issue.
  • windmill-parser-wasm/Cargo.lock — verified its diff is purely 1.880.1 → 1.881.0 version bumps with no dependency drift.

Test coverage

This PR is release metadata, version bumps, and regenerated lockfiles only — no automated tests are expected, and there is no in-app surface to exercise. The changes being released were reviewed in their own PRs (#12515, #12571, #12490, #12556, #12560, #12561, #12551, #12563, #12493, #12569, #12568, #12570, #12511, #12553, #12477, #12558). No manual verification is needed beyond CI confirming the versioned artifacts build and the binary reports 1.881.0 at startup.

@rubenfiszel
rubenfiszel force-pushed the release-please--branches--main--components--windmill branch 2 times, most recently from c5d292b to f3b47b7 Compare November 20, 2026 15:57
@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is an automated release-please PR for v1.881.0 (release-type: simple, include-component-in-tag: false). The range 5819ced...f3b47b7 contains a single commit (f3b47b700a chore(main): release 1.881.0) touching exactly the three files the config owns: .release-please-manifest.json, version.txt, and CHANGELOG.md. No source code is in the diff.

Verified specifics:

Considered and dismissed

Test coverage

This PR is release metadata and changelog only — no automated tests are expected, and there is no in-app surface to exercise. The changes being released were reviewed in their own PRs. No manual verification is needed beyond CI confirming the tagged artifacts build and the binary reports 1.881.0 at startup.

@github-actions

Copy link
Copy Markdown
Contributor

Codex Review

Good to merge

No introduced issues found in the exact three-file diff 5819ced...f3b47b7. The manifest, version.txt, and changelog consistently advance to 1.881.0; all 18 changelog entries match the release ancestry.

Test coverage

No automated tests are expected for release metadata and documentation. JSON parsing, version consistency, changelog completeness and ancestry, and git diff --check passed. Builds and tests were not run.

There is no changed in-app surface to exercise, and no additional manual verification is needed for this diff.

@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is an automated release-please PR for v1.881.0 (release-type: simple, include-component-in-tag: false). The range 5819ced...8fb72509 contains two commits — f3b47b70 (chore(main): release 1.881.0) and 8fb72509 (Apply automatic changes) — and the diff is exactly what the release process should produce: a CHANGELOG.md entry, version bumps across all version-bearing files, and regenerated lockfiles. No source code (*.rs/*.svelte/*.py/*.go) is touched; the only .ts changes are VERSION constants.

Verified specifics:

Considered and dismissed

Test coverage

This PR is release metadata, version bumps, and regenerated lockfiles only — no automated tests are expected, and there is no in-app surface to exercise. The changes being released were reviewed in their own PRs. No manual verification is needed beyond CI confirming the versioned artifacts build and the binary reports 1.881.0 at startup.

@github-actions

Copy link
Copy Markdown
Contributor

Codex Review

Good to merge

No introduced issues found in the exact 22-file diff 5819ced...8fb7250, including the automatic changes since the previous review. Release versions consistently advance to 1.881.0, all 18 changelog entries match the release ancestry, and both lockfiles’ dependency references resolve.

Test coverage

No new automated tests are expected for release metadata, version constants, and generated lockfiles. Read-only JSON/TOML parsing, version consistency, lockfile reference checks, changelog completeness and ancestry, and git diff --check passed.

Builds and tests were not run; existing CI should validate the refreshed Rust dependencies. There is no changed in-app surface to exercise. Manual release verification should confirm the built artifacts start normally and report 1.881.0.

@rubenfiszel
rubenfiszel force-pushed the release-please--branches--main--components--windmill branch from 8fb7250 to e751334 Compare November 20, 2026 16:14
@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is an automated release-please PR for v1.881.0 (release-type: simple, include-component-in-tag: false). The range 6ec19f0...e75133470 contains a single commit (e75133470d chore(main): release 1.881.0) touching exactly the three files the config owns: .release-please-manifest.json, version.txt, and CHANGELOG.md. No source code is in the diff.

Verified specifics:

Considered and dismissed

Test coverage

This PR is release metadata and changelog only — no automated tests are expected, and there is no in-app surface to exercise. The changes being released were reviewed in their own PRs. No manual verification is needed beyond CI confirming the tagged artifacts build and the binary reports 1.881.0 at startup.

@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is an automated release-please PR for v1.881.0 (release-type: simple, include-component-in-tag: false). The range 6ec19f0...d13be300 contains two commits — e7513347 (chore(main): release 1.881.0) and d13be300 (Apply automatic changes) — and the diff is exactly what the release process should produce: a CHANGELOG.md entry, version bumps across all version-bearing files, and regenerated lockfiles. No source code (*.rs/*.svelte/*.py/*.go) is touched; the only .ts changes are VERSION constants.

Verified specifics:

Considered and dismissed

  • backend/Cargo.lock dependency refresh (cc 1.11.2→1.11.3, clap/clap_derive 4.6.8→4.6.9, serde_with/serde_with_macros 3.24.0→3.25.0, new transitive jiff 1.0.1 family) — the only substantive non-version change. This is the expected output of the cargo generate-lockfile step in the pre-existing .github/workflows/change-versions.yml, not an author decision. I confirmed jiff = "0.2.39" (resolved to 0.2.46) is still windmill-common's direct workspace dependency and unchanged, and serde_with is not a direct dependency of any backend/**/Cargo.toml; the jiff 1.0.1 copy rides in only transitively via serde_with. No functional impact. The windmill-parser-wasm/Cargo.lock diff is pure 1.880.1 → 1.881.0 version bumps.
  • Stray 1.880.1 remaining in the tree — it survives only in the windmill-parser-wasm-ts/windmill-parser-wasm-csharp pins (a separate package with its own release cycle, bumped to 1.880.1 by chore: bump the ts and csharp wasm parsers to 1.880.1 #12565), the CHANGELOG compare link and previous release heading (both correct), and the openFlow.json fixture. No Windmill version itself is left unbumped. Not a finding.
  • typescript-client/package-lock.json at 1.813.0 while package.json is 1.881.0 — pre-existing: that lockfile is not in this PR's diff, and the base already had it stale at 1.813.0 against package.json 1.880.1. Not introduced here.
  • Commits in range absent from the changelog — 67b1f15a/554cfd06 (chore:) and the non-conventional subjects (b8a24bdd rebuild std, 8dc728ec fairness settings, b08a2aad fairness reserve toggle) carry no feat:/fix:/perf: prefix, so release-please correctly excludes them.
  • #12516 listed despite being this PR's base SHA — 6ec19f0 is the feat: commit for feat: lead the run graph's error handler to the node that receives its output #12516, which landed before the release commit, so it belongs in the entry. Correct inclusion, not an off-by-one error.
  • [@param](https://github.com/param) autolink and the trailing "Python Args:" — release-please autolinks the literal @param in the source commit subject and carries the trailing colon verbatim; cosmetic release-process output derived from the commit message, not an author-introduced issue.
  • Code changes hidden in the release commit — git log for the range shows only the two release-process commits; the underlying changes were reviewed in their own PRs.

Test coverage

This PR is release metadata, version bumps, and regenerated lockfiles only — no automated tests are expected, and there is no in-app surface to exercise. The changes being released were reviewed in their own PRs (#12515, #12571, #12490, #12516, #12556, #12560, #12561, #12464, #12551, #12563, #12493, #12532, #12569, #12568, #12570, #12511, #12553, #12477, #12558). No manual verification is needed beyond CI confirming the versioned artifacts build and the binary reports 1.881.0 at startup.

@github-actions

Copy link
Copy Markdown
Contributor

Codex Review

Good to merge

No introduced issues found in the exact 22-file diff 6ec19f0...d13be30. Release versions consistently advance to 1.881.0, all 19 changelog entries match the release ancestry, and both lockfiles’ dependency references resolve.

Test coverage

No new automated tests are expected for release metadata, version constants, and generated lockfiles. JSON/TOML parsing, version consistency, lockfile references, changelog completeness and ancestry, and git diff --check passed.

Application builds and tests were not run; CI should validate the refreshed Rust dependencies. There is no changed in-app surface to exercise. Manual release verification should confirm the built artifacts start normally and report 1.881.0.

@rubenfiszel
rubenfiszel force-pushed the release-please--branches--main--components--windmill branch from d13be30 to 4c4667c Compare November 20, 2026 16:44
@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is an automated release-please PR for v1.881.0 (release-type: simple). The range contains a single commit (4c4667c204 chore(main): release 1.881.0) touching exactly the three files the release config owns: .release-please-manifest.json, version.txt, and CHANGELOG.md. No source code is in the diff.

Verified specifics:

Considered and dismissed

  • Commits in range absent from the changelog — 67b1f15a (chore: bump windmill-parser-wasm-ts and -csharp) and 554cfd06 (chore: remove the akeyless icon) carry chore:, and b8a24bdd (rebuild std), 8dc728ec (show fairness settings), b08a2aad (show fairness reserve toggle) carry no conventional prefix. None are feat:/fix:/perf:, so release-please correctly excludes them. Not a defect.
  • #12573 listed despite being this PR's base SHA — 8b3b692b is the fix: commit for fix: session chat shows its own workspace's AI config #12573, which landed before the release commit, so it belongs in the entry. Correct inclusion, not an off-by-one error.
  • [@param](https://github.com/param) autolink and the trailing "Python Args:" — release-please autolinks the literal @param in the source commit subject to a GitHub user and carries the trailing colon verbatim; cosmetic release-process output derived from the original commit message, not an author-introduced issue.
  • Other version-bearing files not bumped (Cargo.toml, Cargo.lock, package.json, openapi.yaml, etc.) — .release-please-config.json uses release-type: simple, so version.txt + manifest + changelog are the complete set this step touches; the broader version propagation is a separate post-release workflow outside this PR's range. Confirmed the diff touches only the three expected files.
  • Code changes hidden in the release commit — git log for the range shows only the single release commit; the underlying changes were reviewed in their own PRs.

Test coverage

This PR is release metadata and changelog only — no automated tests are expected, and there is no in-app surface to exercise. The changes being released were reviewed in their own PRs. No manual verification is needed beyond CI confirming the tagged artifacts build and the binary reports 1.881.0 at startup.

@github-actions

Copy link
Copy Markdown
Contributor

Codex Review

Good to merge

No introduced issues found in the exact three-file diff 8b3b692...4c4667c. Release metadata consistently advances to 1.881.0, and all 20 changelog entries match the release ancestry.

Test coverage

No automated tests are expected for this docs/config-only change. JSON parsing, version consistency, changelog completeness and ancestry, and git diff --check passed. Builds and application tests were not run.

There is no changed in-app surface to exercise, and no additional manual verification is needed for this diff.

@github-actions

Copy link
Copy Markdown
Contributor

Pi Review

Good to merge

This is an automated release-please PR for v1.881.0 (release-type: simple). The range 8b3b692b...440892426e contains two commits — 4c4667c204 (chore(main): release 1.881.0) and 440892426e (Apply automatic changes) — and the diff is exactly what the release process should produce: a CHANGELOG.md entry, version bumps across all version-bearing files, and regenerated lockfiles. No source code (*.rs/*.svelte/*.py/*.go) is touched; the only .ts changes are VERSION constants.

Verified specifics:

Considered and dismissed

Test coverage

This PR is release metadata, version bumps, and generated lockfiles — no automated tests are expected, and there is no in-app surface to exercise. The changes being released were reviewed in their own PRs. No manual verification is needed beyond CI confirming the tagged artifacts build and the binary reports 1.881.0 at startup.

@github-actions

Copy link
Copy Markdown
Contributor

Codex Review

Good to merge

No introduced issues found in the exact 22-file diff 8b3b692...4408924, including the automatic changes since the previous review. Release versions consistently advance to 1.881.0, all 20 changelog entries match the release ancestry, and both Cargo lockfiles’ dependency references resolve.

Test coverage

No new automated tests are expected for release metadata, version constants, and generated lockfiles. Read-only JSON/TOML parsing, version consistency, lockfile reference checks, changelog completeness and ancestry, and git diff --check passed.

Builds and application tests were not run; CI should validate the refreshed Rust dependencies. There is no changed in-app surface to exercise. Manual release verification should confirm the built artifacts start normally and report 1.881.0.

@rubenfiszel
rubenfiszel force-pushed the release-please--branches--main--components--windmill branch from 4408924 to 1f88815 Compare November 20, 2026 17:05
@rubenfiszel
rubenfiszel merged commit 184b97d into main Nov 20, 2026
18 of 21 checks passed
@rubenfiszel
rubenfiszel deleted the release-please--branches--main--components--windmill branch November 20, 2026 17:08
@rubenfiszel

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

@github-actions github-actions Bot locked and limited conversation to collaborators Nov 20, 2026
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