Skip to content

fix(release): test joined output in the Windows packaged smoke - #599

Merged
jmagar merged 1 commit into
mainfrom
fix/release-windows-skills-smoke
Sep 11, 2026
Merged

jmagar merged 1 commit into
mainfrom
fix/release-windows-skills-smoke

Conversation

@jmagar

@jmagar jmagar commented Sep 11, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

The v1.15.1 release never qualified: its Build (x86_64-pc-windows-msvc) job failed at the packaged smoke with Packaged binary does not expose the required Skills surface, even though v1.15.1 compiled the skills feature and carried the expected help text.

The check was wrong, not the binary. PowerShell captures native command output as an array of lines, and -notmatch applied to an array returns the non-matching lines rather than a boolean. For multi-line skills --help output that result is always non-empty, so the if is always true and the step throws.

This joins the captured output with Out-String before matching, for both the Code Mode and Skills checks, and adds the captured help text to the failure message. The guard in crates/labby/tests/ci_changed_paths.rs still sees three occurrences of both skills --help and the help text.

This unblocks the pending 1.16.0 release (#569), which would otherwise fail the same way.

Test plan

  • release.yml parses as YAML
  • Guard-test string counts unchanged (3 and 3)
  • Reproduced in PowerShell 7.5.11 (arm64): the current step throws with the help text present; the fixed step passes with it present, still throws with it absent, and the Code Mode JSON check passes
  • CI green on this PR
  • The v1.16.0 release run passes the Windows packaged smoke

🤖 Generated with Claude Code

PowerShell captures native output as an array of lines, and -notmatch on
an array returns the non-matching lines. The Skills check was therefore
truthy for any multi-line help output and failed even when the expected
text was present, which kept v1.15.1 from qualifying. Join the output with
Out-String before matching, for both the Code Mode and the Skills check,
and include the captured help text in the failure message.
@jmagar
jmagar merged commit 3d34d2b into main Sep 11, 2026
44 checks passed
@jmagar
jmagar deleted the fix/release-windows-skills-smoke branch September 11, 2026 12:04
jmagar added a commit that referenced this pull request Sep 11, 2026
🤖 I have created a release *beep* *boop*
---


## [1.16.0](v1.15.1...v1.16.0) (2026-09-11)


### Added

* **depot:** add full administration control plane ([#567](#567)) ([c83333c](c83333c))


### Fixed

* **auth:** support Codex native loopback OAuth redirects ([#573](#573)) ([163ef53](163ef53))
* **cli:** report rejected gateway config as invalid_param instead of panicking ([#580](#580)) ([f56822e](f56822e))
* **codemode:** bound one-shot CLI catalog cold connects and persist partial results ([#579](#579)) ([f66a3b7](f66a3b7))
* **codemode:** discover read-ready upstream resource URIs ([#592](#592)) ([5c6af13](5c6af13))
* **codemode:** negative-cache failed one-shot catalog upstream probes ([#584](#584)) ([d29bb30](d29bb30))
* **deploy:** keep the team-labby example route loadable on current main ([#585](#585)) ([00b375f](00b375f))
* **file-stash:** own the upload reservation in the spawned finalize task ([#590](#590)) ([2fb1f86](2fb1f86))
* **gateway:** classify stdio lifecycle from the MCP error, not child stderr ([#586](#586)) ([60cf776](60cf776))
* **gateway:** do not respawn stdio upstreams that exit before the handshake ([#582](#582)) ([9f7fb59](9f7fb59))
* preserve Skills over MCP across client and server transports ([#571](#571)) ([b6ad223](b6ad223))
* **release:** test joined output in the Windows packaged smoke ([#599](#599)) ([3d34d2b](3d34d2b))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
@jmagar jmagar mentioned this pull request Oct 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant