chore(main): release 26.2.0#8290
Merged
davbree merged 1 commit intoJul 7, 2026
Merged
Conversation
token-generator-app
Bot
force-pushed
the
release-please--branches--main--components--netlify-cli
branch
from
aba4585 to
ae4effa
Compare
token-generator-app
Bot
changed the title
token-generator-app
Bot
force-pushed
the
release-please--branches--main--components--netlify-cli
branch
10 times, most recently
from
e70f7a0 to
606c030
Compare
token-generator-app
Bot
force-pushed
the
release-please--branches--main--components--netlify-cli
branch
3 times, most recently
from
f7cddb5 to
a744555
Compare
token-generator-app
Bot
force-pushed
the
release-please--branches--main--components--netlify-cli
branch
2 times, most recently
from
67e2683 to
a6b509e
Compare
davbree
added a commit
that referenced
this pull request
Jul 6, 2026
## Summary
Two related changes:
1. **Fix the failing Windows unit tests.** 5 tests in
`tests/unit/lib/edge-functions/watch-ignore.test.ts` hardcoded
POSIX-style expected paths (e.g. `/project/_site`,
`/absolute/src/posts`). The `EdgeFunctionsRegistryImpl` constructor
normalizes `publishDir`/`watchIgnore` with `path.resolve(projectDir, …)`
(`src/lib/edge-functions/registry.ts:179-180`), which on Windows
produces drive-prefixed, backslash paths (`D:\project\_site`), so the
assertions could only pass on macOS/Linux:
```
AssertionError: expected 'D:\project\_site' to be '/project/_site'
AssertionError: expected [ 'D:\project\src\posts', …(1) ] to deeply
equal [ '/project/src/posts', …(1) ]
```
Fixed by computing the expected values with the same
`resolve('/project', …)` call the implementation uses, so the assertions
hold on every platform while still verifying the meaningful behavior
(inputs resolved relative to `projectDir`).
2. **Run unit tests on macOS and Windows for every PR.** Since #8199,
macOS/Windows test jobs only run on `release-please--*` PRs and the
nightly schedule — which is exactly why this regression wasn't caught
until it surfaced on the release PR (#8290). This adds a `macOS-latest`
and a `windows-2025` job at the primary Node version to every PR's
**unit test** matrix, via a new `extra_oses_always` key in
`.github/test-matrix.yml`, deduplicated against the release-only OS set
so release PRs don't get duplicate jobs. Integration and E2E matrices
are unchanged (they remain release/schedule-gated).
## Context
The broken tests were introduced in #8271 (`feat: add watch-ignore
flag`), so this failure already exists on `main` — it's not specific to
the release PR (#8290) that surfaced it. Once this merges, #8290 goes
green on re-run.
## Verification
- `npm exec vitest -- run
tests/unit/lib/edge-functions/watch-ignore.test.ts` → 14 passed locally.
- Simulated the updated matrix computation: regular PRs now include
`macOS-latest / 24` and `windows-2025 / 24` on top of the always-on
Linux coverage; `release-please--*` PRs include each exactly once
(deduped).
- With change (2) in place, this PR's own CI now runs the macOS and
Windows unit jobs and validates the fix directly.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
token-generator-app
Bot
force-pushed
the
release-please--branches--main--components--netlify-cli
branch
from
a6b509e to
d402a0d
Compare
davbree
approved these changes
Jul 6, 2026
davbree
deleted the
release-please--branches--main--components--netlify-cli
branch
Contributor
Author
|
🤖 Created releases: 🌻 |
token-generator-app
Bot
added
autorelease: tagged
and removed
autorelease: pending
labels
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
26.2.0 (2026-07-06)
Features
Bug Fixes
&&,||, etc.) (#8234) (d07599e)This PR was generated with Release Please. See documentation.