Commit Graph
5590 Commits
Author SHA1 Message Date
Giteabotandsilverwind 2f89c68b64 chore(deps): update dependencies (#40395)
> [!NOTE]
> This PR body was truncated due to platform limits.

This PR contains the following updates:

| Package | Change |
[Age](https://docs.renovatebot.com/merge-confidence/) |
[Confidence](https://docs.renovatebot.com/merge-confidence/) | Type |
Update | Pending |
|---|---|---|---|---|---|---|
| [@playwright/test](https://playwright.dev)
([source](https://redirect.github.com/microsoft/playwright)) | [`1.64.1`
→
`1.65.0`](https://renovatebot.com/diffs/npm/@playwright%2ftest/1.64.1/1.65.0)
|
![age](https://developer.mend.io/api/mc/badges/age/npm/@playwright%2ftest/1.65.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@playwright%2ftest/1.64.1/1.65.0?slim=true)
| devDependencies | minor | `1.65.1` |
| [@stylistic/stylelint-plugin](https://stylelint-stylistic.github.io/)
([source](https://redirect.github.com/stylelint-stylistic/stylelint-stylistic))
| [`6.0.0` →
`6.0.1`](https://renovatebot.com/diffs/npm/@stylistic%2fstylelint-plugin/6.0.0/6.0.1)
|
![age](https://developer.mend.io/api/mc/badges/age/npm/@stylistic%2fstylelint-plugin/6.0.1?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@stylistic%2fstylelint-plugin/6.0.0/6.0.1?slim=true)
| devDependencies | patch | |
|
[@typescript-eslint/parser](https://typescript-eslint.io/packages/parser)
([source](https://redirect.github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser))
| [`8.72.1` →
`8.72.2`](https://renovatebot.com/diffs/npm/@typescript-eslint%2fparser/8.72.1/8.72.2)
|
![age](https://developer.mend.io/api/mc/badges/age/npm/@typescript-eslint%2fparser/8.72.2?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@typescript-eslint%2fparser/8.72.1/8.72.2?slim=true)
| devDependencies | patch | |
|
[asciinema-player](https://redirect.github.com/asciinema/asciinema-player)
| [`3.17.0` →
`3.18.0`](https://renovatebot.com/diffs/npm/asciinema-player/3.17.0/3.18.0)
|
![age](https://developer.mend.io/api/mc/badges/age/npm/asciinema-player/3.18.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/asciinema-player/3.17.0/3.18.0?slim=true)
| dependencies | minor | `3.18.1` |
| [colord](https://redirect.github.com/omgovich/colord) | [`2.10.0` →
`2.12.0`](https://renovatebot.com/diffs/npm/colord/2.10.0/2.12.0) |
![age](https://developer.mend.io/api/mc/badges/age/npm/colord/2.12.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/colord/2.10.0/2.12.0?slim=true)
| dependencies | minor | `2.13.0` |
|
[crowdin/github-action](https://redirect.github.com/crowdin/github-action)
| `v3.5.1` → `v3.6.0` |
![age](https://developer.mend.io/api/mc/badges/age/github-tags/crowdin%2fgithub-action/v3.6.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/github-tags/crowdin%2fgithub-action/v3.5.1/v3.6.0?slim=true)
| action | minor | |
| [djlint](https://redirect.github.com/djlint/djLint)
([changelog](https://redirect.github.com/djlint/djLint/blob/master/CHANGELOG.md))
| `==1.49.9` → `==1.50.0` |
![age](https://developer.mend.io/api/mc/badges/age/pypi/djlint/1.50.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/djlint/1.49.9/1.50.0?slim=true)
| dependency-groups | minor | `1.50.4` (+3) |
| [docker/login-action](https://redirect.github.com/docker/login-action)
| `v4.7.0` → `v4.8.0` |
![age](https://developer.mend.io/api/mc/badges/age/github-tags/docker%2flogin-action/v4.8.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/github-tags/docker%2flogin-action/v4.7.0/v4.8.0?slim=true)
| action | minor | |
|
[eslint-plugin-import-x](https://redirect.github.com/un-ts/eslint-plugin-import-x)
| [`4.17.1` →
`4.18.1`](https://renovatebot.com/diffs/npm/eslint-plugin-import-x/4.17.1/4.18.1)
|
![age](https://developer.mend.io/api/mc/badges/age/npm/eslint-plugin-import-x/4.18.1?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/eslint-plugin-import-x/4.17.1/4.18.1?slim=true)
| devDependencies | minor | |
| [eslint-plugin-vue](https://eslint.vuejs.org)
([source](https://redirect.github.com/vuejs/eslint-plugin-vue)) |
[`10.12.0` →
`10.12.1`](https://renovatebot.com/diffs/npm/eslint-plugin-vue/10.12.0/10.12.1)
|
![age](https://developer.mend.io/api/mc/badges/age/npm/eslint-plugin-vue/10.12.1?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/eslint-plugin-vue/10.12.0/10.12.1?slim=true)
| devDependencies | patch | |
|
[github.com/blevesearch/bleve/v2](https://redirect.github.com/blevesearch/bleve)
| `v2.6.2` → `v2.6.3` |
![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fblevesearch%2fbleve%2fv2/v2.6.3?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fblevesearch%2fbleve%2fv2/v2.6.2/v2.6.3?slim=true)
| require | patch | |
|
[github.com/dlclark/regexp2/v2](https://redirect.github.com/dlclark/regexp2)
| `v2.12.0` → `v2.13.0` |
![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fdlclark%2fregexp2%2fv2/v2.13.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fdlclark%2fregexp2%2fv2/v2.12.0/v2.13.0?slim=true)
| require | minor | |
|
[github.com/getkin/kin-openapi](https://redirect.github.com/getkin/kin-openapi)
| `v0.152.0` → `v0.153.0` |
![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fgetkin%2fkin-openapi/v0.153.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fgetkin%2fkin-openapi/v0.152.0/v0.153.0?slim=true)
| require | minor | |
|
[github.com/go-co-op/gocron/v2](https://redirect.github.com/go-co-op/gocron)
| `v2.23.0` → `v2.23.1` |
![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fgo-co-op%2fgocron%2fv2/v2.23.1?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fgo-co-op%2fgocron%2fv2/v2.23.0/v2.23.1?slim=true)
| require | patch | |
|
[github.com/klauspost/compress](https://redirect.github.com/klauspost/compress)
| `v1.20.3` → `v1.20.4` |
![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fklauspost%2fcompress/v1.20.4?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fklauspost%2fcompress/v1.20.3/v1.20.4?slim=true)
| require | patch | |
|
[github.com/mattn/go-sqlite3](https://redirect.github.com/mattn/go-sqlite3)
| `v1.14.52` → `v1.14.53` |
![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fmattn%2fgo-sqlite3/v1.14.53?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fmattn%2fgo-sqlite3/v1.14.52/v1.14.53?slim=true)
| require | patch | |
|
[github.com/meilisearch/meilisearch-go](https://redirect.github.com/meilisearch/meilisearch-go)
| `v0.36.3` → `v0.37.0` |
![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fmeilisearch%2fmeilisearch-go/v0.37.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fmeilisearch%2fmeilisearch-go/v0.36.3/v0.37.0?slim=true)
| require | minor | |
|
[github.com/wneessen/go-mail](https://redirect.github.com/wneessen/go-mail)
| `v0.8.1` → `v0.8.2` |
![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fwneessen%2fgo-mail/v0.8.2?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fwneessen%2fgo-mail/v0.8.1/v0.8.2?slim=true)
| require | patch | |
|
[gitlab.com/gitlab-org/api/client-go/v3](https://gitlab.com/gitlab-org/api/client-go)
| `v3.43.0` → `v3.48.0` |
![age](https://developer.mend.io/api/mc/badges/age/go/gitlab.com%2fgitlab-org%2fapi%2fclient-go%2fv3/v3.48.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/go/gitlab.com%2fgitlab-org%2fapi%2fclient-go%2fv3/v3.43.0/v3.48.0?slim=true)
| require | minor | `v3.51.0` (+2) |
| [golang.org/x/image](https://pkg.go.dev/golang.org/x/image) |
[`v0.47.0` →
`v0.48.0`](https://cs.opensource.google/go/x/image/+/refs/tags/v0.47.0...refs/tags/v0.48.0)
|
![age](https://developer.mend.io/api/mc/badges/age/go/golang.org%2fx%2fimage/v0.48.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/go/golang.org%2fx%2fimage/v0.47.0/v0.48.0?slim=true)
| require | minor | |
| [golang.org/x/mod](https://pkg.go.dev/golang.org/x/mod) | [`v0.42.0` →
`v0.43.0`](https://cs.opensource.google/go/x/mod/+/refs/tags/v0.42.0...refs/tags/v0.43.0)
|
![age](https://developer.mend.io/api/mc/badges/age/go/golang.org%2fx%2fmod/v0.43.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/go/golang.org%2fx%2fmod/v0.42.0/v0.43.0?slim=true)
| require | minor | |
| [golang.org/x/oauth2](https://pkg.go.dev/golang.org/x/oauth2) |
[`v0.37.0` →
`v0.38.0`](https://cs.opensource.google/go/x/oauth2/+/refs/tags/v0.37.0...refs/tags/v0.38.0)
|
![age](https://developer.mend.io/api/mc/badges/age/go/golang.org%2fx%2foauth2/v0.38.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/go/golang.org%2fx%2foauth2/v0.37.0/v0.38.0?slim=true)
| require | minor | |
| mcr.microsoft.com/mssql/server | `07d7ded` → `debdc21` | | | service |
digest | |
| [modernc.org/sqlite](https://gitlab.com/cznic/sqlite) | `v1.61.1` →
`v1.62.0` |
![age](https://developer.mend.io/api/mc/badges/age/go/modernc.org%2fsqlite/v1.62.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/go/modernc.org%2fsqlite/v1.61.1/v1.62.0?slim=true)
| require | minor | |
| [pnpm](https://pnpm.io)
([source](https://redirect.github.com/pnpm/pnpm/tree/HEAD/pnpm/npm/pnpm))
| [`12.17.0` →
`12.19.0`](https://renovatebot.com/diffs/npm/pnpm/12.17.0/12.19.0) |
![age](https://developer.mend.io/api/mc/badges/age/npm/pnpm/12.19.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/pnpm/12.17.0/12.19.0?slim=true)
| packageManager | minor | `12.21.0` (+1) |
| [pnpm](https://pnpm.io)
([source](https://redirect.github.com/pnpm/pnpm/tree/HEAD/pnpm/npm/pnpm))
| [`>= 12.17.0` → `>=
12.19.0`](https://renovatebot.com/diffs/npm/pnpm/12.17.0/12.19.0) |
![age](https://developer.mend.io/api/mc/badges/age/npm/pnpm/12.19.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/pnpm/12.17.0/12.19.0?slim=true)
| engines | minor | `12.21.0` (+1) |
| [redis](https://hub.docker.com/_/redis)
([source](https://redirect.github.com/redis/docker-library-redis)) |
`298e5b3` → `1f88291` | | | service | digest | |
| [renovate](https://renovatebot.com)
([source](https://redirect.github.com/renovatebot/renovate)) |
[`44.210.0` →
`44.232.0`](https://octochangelog.com/compare?repo=renovatebot%2Frenovate&from=44.210.0&to=44.232.0)
|
![age](https://developer.mend.io/api/mc/badges/age/npm/renovate/44.232.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/renovate/44.210.0/44.232.0?slim=true)
| | minor | `44.245.0` (+37) |
|
[renovatebot/github-action](https://redirect.github.com/renovatebot/github-action)
| `v46.3.12` → `v46.3.13` |
![age](https://developer.mend.io/api/mc/badges/age/github-tags/renovatebot%2fgithub-action/v46.3.13?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/github-tags/renovatebot%2fgithub-action/v46.3.12/v46.3.13?slim=true)
| action | patch | `v46.3.14` |
|
[rolldown-license-plugin](https://redirect.github.com/silverwind/rolldown-license-plugin)
| [`3.0.14` →
`3.0.15`](https://renovatebot.com/diffs/npm/rolldown-license-plugin/3.0.14/3.0.15)
|
![age](https://developer.mend.io/api/mc/badges/age/npm/rolldown-license-plugin/3.0.15?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/rolldown-license-plugin/3.0.14/3.0.15?slim=true)
| dependencies | patch | |
|
[sigstore/cosign-installer](https://redirect.github.com/sigstore/cosign-installer)
| `v4.1.2` → `v4.1.3` |
![age](https://developer.mend.io/api/mc/badges/age/github-tags/sigstore%2fcosign-installer/v4.1.3?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/github-tags/sigstore%2fcosign-installer/v4.1.2/v4.1.3?slim=true)
| action | patch | |
|
[spectral-cli-bundle](https://redirect.github.com/silverwind/spectral-cli-bundle)
| [`1.0.16` →
`2.0.0`](https://renovatebot.com/diffs/npm/spectral-cli-bundle/1.0.16/2.0.0)
|
![age](https://developer.mend.io/api/mc/badges/age/npm/spectral-cli-bundle/2.0.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/spectral-cli-bundle/1.0.16/2.0.0?slim=true)
| devDependencies | major | |
|
[stylelint-declaration-strict-value](https://redirect.github.com/AndyOGo/stylelint-declaration-strict-value)
| [`1.12.1` →
`1.13.0`](https://renovatebot.com/diffs/npm/stylelint-declaration-strict-value/1.12.1/1.13.0)
|
![age](https://developer.mend.io/api/mc/badges/age/npm/stylelint-declaration-strict-value/1.13.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/stylelint-declaration-strict-value/1.12.1/1.13.0?slim=true)
| devDependencies | minor | |
|
[typescript-eslint](https://typescript-eslint.io/packages/typescript-eslint)
([source](https://redirect.github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/typescript-eslint))
| [`8.72.1` →
`8.72.2`](https://renovatebot.com/diffs/npm/typescript-eslint/8.72.1/8.72.2)
|
![age](https://developer.mend.io/api/mc/badges/age/npm/typescript-eslint/8.72.2?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/typescript-eslint/8.72.1/8.72.2?slim=true)
| devDependencies | patch | |
| [vite](https://vite.dev)
([source](https://redirect.github.com/vitejs/vite/tree/HEAD/packages/vite))
| [`8.3.5` →
`8.3.8`](https://renovatebot.com/diffs/npm/vite/8.3.5/8.3.8) |
![age](https://developer.mend.io/api/mc/badges/age/npm/vite/8.3.8?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/vite/8.3.5/8.3.8?slim=true)
| dependencies | patch | |
| [vue](https://vuejs.org/)
([source](https://redirect.github.com/vuejs/core)) | [`3.5.44` →
`3.5.45`](https://renovatebot.com/diffs/npm/vue/3.5.44/3.5.45) |
![age](https://developer.mend.io/api/mc/badges/age/npm/vue/3.5.45?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/vue/3.5.44/3.5.45?slim=true)
| dependencies | patch | |
|
[vue-eslint-parser](https://redirect.github.com/vuejs/vue-eslint-parser)
| [`10.4.1` →
`10.4.2`](https://renovatebot.com/diffs/npm/vue-eslint-parser/10.4.1/10.4.2)
|
![age](https://developer.mend.io/api/mc/badges/age/npm/vue-eslint-parser/10.4.2?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/vue-eslint-parser/10.4.1/10.4.2?slim=true)
| devDependencies | patch | |

---

### Release Notes

<details>
<summary>microsoft/playwright (@&#8203;playwright/test)</summary>

###
[`v1.65.0`](https://redirect.github.com/microsoft/playwright/releases/tag/v1.65.0)

[Compare
Source](https://redirect.github.com/microsoft/playwright/compare/v1.64.1...v1.65.0)

#### 🥟 Run tests with Bun

The test runner now runs under [Bun](https://bun.com). Bun transpiles
your TypeScript test files itself, so Playwright does not use Babel or
its compilation cache. Pass the `--bun` flag, because without it `bunx
playwright test` runs on Node.js:

```bash
bunx --bun playwright test
```

Our CI runs the test runner tests under Bun 1.4.3 on Linux. Some
features work differently under Bun:

- There is no watch mode. UI mode does not run tests again when files
change, and `--only-changed` does not follow imports.
- Bun loads modules itself, so `--tsconfig` and the JSX options in
`tsconfig.json` have no effect, and custom ESM loaders are not
supported.
- Stack traces do not include async frames, and API names do not include
the class name: `click` instead of `locator.click`. This changes some
step locations, step titles and error messages.
- Console output of a test does not get into the trace and UI mode.

#### 🚨 Reports with only failures

New
[`failures`](https://playwright.dev/docs/test-reporters#failures-reporter)
reporter prints failures and successful retries as they occur, followed
by a summary, without progress output.

New `onlyFailures` option of the HTML, JSON and JUnit reporters [keeps
only](https://playwright.dev/docs/test-reporters#report-only-failures)
tests with unexpected outcomes, flaky tests and interrupted tests:

```js
// playwright.config.ts
import { defineConfig } from '@playwright/test';

export default defineConfig({
  reporter: [
    ['failures'],
    ['html', { onlyFailures: true }],
  ],
});
```

#### 🎯 Test runner

- New built-in `-exclusive-` [test
lock](https://playwright.dev/docs/test-parallel#test-locks) runs a test
only when no other tests are running. All other tests continue to run in
parallel with each other:

  ```js
  test('restart the server', { lock: '-exclusive-' }, async () => {
    // No other test runs while this one is running.
  });
  ```

- [test.skip()](https://playwright.dev/docs/api/class-test#test-skip),
[test.fixme()](https://playwright.dev/docs/api/class-test#test-fixme),
[test.fail()](https://playwright.dev/docs/api/class-test#test-fail) and
[test.slow()](https://playwright.dev/docs/api/class-test#test-slow) now
accept only a description. It is recorded in the test annotation:

  ```js
  test('upload a file', async ({ page }) => {
    test.skip('Not implemented yet');
  });
  ```

- New `PLAYWRIGHT_TRANSFORM_CACHE_DIR` environment variable sets the
directory for transpiled test files, for example on a Linux machine
shared with other users.

#### New APIs

- New options
[`timeout`](https://playwright.dev/docs/api/class-cdpsession#cdp-session-send-option-timeout)
and
[`signal`](https://playwright.dev/docs/api/class-cdpsession#cdp-session-send-option-signal)
in
[cdpSession.send()](https://playwright.dev/docs/api/class-cdpsession#cdp-session-send).
- New
[testRun.mode()](https://playwright.dev/docs/api/class-testrun#test-run-mode)
returns the execution mode of a suite during
[reporter.preprocess()](https://playwright.dev/docs/api/class-reporter#reporter-preprocess).

#### Notable Changes ⚠️

- TypeScript class fields now follow
[`useDefineForClassFields`](https://playwright.dev/docs/test-typescript#tsconfig-class-fields)
from your `tsconfig.json`, the same as `tsc`. It is enabled for `ES2022`
and later targets, and when `target` is not specified. A field
initializer that reads a constructor parameter property now fails,
because the initializer runs first:

  ```js
  class LoginPage {
// TypeError: Cannot read properties of undefined (reading 'getByRole')
    readonly submit = this.page.getByRole('button', { name: 'Submit' });

    constructor(private readonly page: Page) {}
  }
  ```

Move the initialization to the constructor, or set
`"useDefineForClassFields": false` in your `tsconfig.json`.

- Actions such as
[locator.click()](https://playwright.dev/docs/api/class-locator#locator-click),
[locator.check()](https://playwright.dev/docs/api/class-locator#locator-check),
[locator.tap()](https://playwright.dev/docs/api/class-locator#locator-tap),
[locator.fill()](https://playwright.dev/docs/api/class-locator#locator-fill),
[locator.clear()](https://playwright.dev/docs/api/class-locator#locator-clear)
and
[locator.selectOption()](https://playwright.dev/docs/api/class-locator#locator-select-option)
now wait for the element to be [not
inert](https://playwright.dev/docs/actionability#not-inert). An action
on an element with the `inert` attribute, or inside such an element, now
times out if the element stays inert.

- A sharded run now fails with "No tests found" when no tests match
across all shards. Pass `--pass-with-no-tests` to allow this. An empty
shard still passes when other shards have tests.

- Cookie matching now follows RFC 6265. With a URL,
[browserContext.cookies()](https://playwright.dev/docs/api/class-browsercontext#browser-context-cookies)
and
[apiRequestContext.cookies()](https://playwright.dev/docs/api/class-apirequestcontext#api-request-context-cookies)
no longer return host-only cookies for subdomains or `Path=/api` cookies
for `/apiv2`, and a `Path=/foo/` cookie does not match `/foo`.
[APIRequestContext](https://playwright.dev/docs/api/class-apirequestcontext)
sends a cookie without a name as `Cookie: x` instead of `Cookie: =x`,
and stores `Set-Cookie: token` as a cookie without a name.

- Proxy credentials are no longer sent to websites. The credentials in
the
[`proxy`](https://playwright.dev/docs/api/class-browsertype#browser-type-launch-option-proxy)
option now answer only proxy challenges. To authenticate on a website,
use
[`httpCredentials`](https://playwright.dev/docs/api/class-browser#browser-new-context-option-http-credentials).

- Text that the browser does not render, such as text that is not
assigned to a slot or text directly inside a closed `<details>`, is no
longer part of accessible names and aria snapshots. This can change the
results of
[page.getByRole()](https://playwright.dev/docs/api/class-page#page-get-by-role)
with a name,
[locator.ariaSnapshot()](https://playwright.dev/docs/api/class-locator#locator-aria-snapshot)
and
[expect(locator).toMatchAriaSnapshot()](https://playwright.dev/docs/api/class-locatorassertions#locator-assertions-to-match-aria-snapshot).

- String and `URLSearchParams` values of the `params` option in
[APIRequestContext](https://playwright.dev/docs/api/class-apirequestcontext)
requests are now appended to the query that the URL already has, instead
of replacing it.

- `.css`, `.less` and `.scss` imports in test files now load as empty
modules instead of being removed, so the imported file must exist.

- The blob reporter again deletes the content of its output directory
before it writes the report. Playwright 1.64 kept reports with other
names.

- Test locations of imported calls such as `test(` in CommonJS output
now point to the start of the callee, for example `a.spec.ts:3:7`
instead of `a.spec.ts:3:11`. This is the same as in ESM.

#### Announcements

- ⚠️ Playwright no longer tests on Node.js 20. Use Node.js 22, 24 or 26,
as listed in the [system
requirements](https://playwright.dev/docs/intro#system-requirements).
- 🐳 [Docker images](https://playwright.dev/docs/docker) now include
Node.js 26 instead of Node.js 24, and the latest patch of Chromium on
the same branch.

#### Browser Versions

- Chromium 158.0.8127.18
- Mozilla Firefox 159.0
- WebKit 27.2

This version was also tested against the following stable channels:

- Google Chrome 157
- Microsoft Edge 156

</details>

<details>
<summary>stylelint-stylistic/stylelint-stylistic
(@&#8203;stylistic/stylelint-plugin)</summary>

###
[`v6.0.1`](https://redirect.github.com/stylelint-stylistic/stylelint-stylistic/blob/HEAD/CHANGELOG.md#601--20261106)

[Compare
Source](https://redirect.github.com/stylelint-stylistic/stylelint-stylistic/compare/v6.0.0...v6.0.1)

##### Fixed

- The `block-closing-brace-empty-line-before` rule, with the values
`never` and `except: ["after-closing-brace"]`, now requires an empty
line before the closing brace of a block if that block ends
with a nested block, even if there is a declaration earlier
in that block. Previously, this setting incorrectly required the removal
of the empty line (see
[#&#8203;750](https://redirect.github.com/stylelint-stylistic/stylelint-stylistic/issues/750)).

</details>

<details>
<summary>typescript-eslint/typescript-eslint
(@&#8203;typescript-eslint/parser)</summary>

###
[`v8.72.2`](https://redirect.github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#8722-2026-11-09)

[Compare
Source](https://redirect.github.com/typescript-eslint/typescript-eslint/compare/v8.72.1...v8.72.2)

This was a version bump only for parser to align it with other projects,
there were no code changes.

See [GitHub
Releases](https://redirect.github.com/typescript-eslint/typescript-eslint/releases/tag/v8.72.2)
for more information.

You can read about our [versioning
strategy](https://typescript-eslint.io/users/versioning) and
[releases](https://typescript-eslint.io/users/releases) on our website.

</details>

<details>
<summary>asciinema/asciinema-player (asciinema-player)</summary>

###
[`v3.18.0`](https://redirect.github.com/asciinema/asciinema-player/releases/tag/v3.18.0):
3.18.0

[Compare
Source](https://redirect.github.com/asciinema/asciinema-player/compare/v3.17.0...v3.18.0)

This release brings smoother playback progress and more accurate
terminal emulation:

- Smooth progress bar animation synchronized with playback speed,
pauses, seeking, and buffering.
- Fixed column alignment of the sextile symbol (⚹).
- Improved handling of unset options from JSON-based integrations:
`null` values are now treated as absent options.
- Clearer, synchronous errors for invalid `speed` and `markers` options.
- Upgraded the terminal emulator from avt 0.16.0 to 0.20.0, bringing
faster parsing and printing, improved cursor positioning during reflow,
more accurate alternate screen resizing, and fixes for wide-character
repetition and insertion.
- Updated dependencies and expanded regression coverage for playback,
streaming, and terminal rendering.

#### Compatibility notes

- `speed` must be a finite, positive number. Numeric strings are
rejected.
- `markers` must be an array of finite numbers or `[time, label]` pairs,
with a finite numeric time and a string label. Invalid values now throw
during player creation.
- Building from source now requires Rust 1.86 or newer. The Nix
development shell provides the toolchain and WASM target.

</details>

<details>
<summary>omgovich/colord (colord)</summary>

###
[`v2.12.0`](https://redirect.github.com/omgovich/colord/blob/HEAD/CHANGELOG.md#2120)

[Compare
Source](https://redirect.github.com/omgovich/colord/compare/v2.11.0...v2.12.0)

##### Minor Changes

- Parse numbers in scientific notation (`rgb(1e2 .5e1 0 / 25e-2)`), as
the CSS spec allows

##### Patch Changes

- Fix: Parse CSS angle units case-insensitively, so `hsl(0.25TURN 50%
50%)` means 90 degrees instead of 0.25 ❤️
[@&#8203;blueDaydreaming725](https://redirect.github.com/blueDaydreaming725)
- Fix: Keep exact colors at the `mix()` endpoints and when only alpha
differs, so a mixture into white no longer turns green after `.darken()`
❤️
[@&#8203;feritcemkahraman](https://redirect.github.com/feritcemkahraman)
- Fix: Type plugin default imports correctly in ES modules under
TypeScript's `node16` and `nodenext` resolution

###
[`v2.11.0`](https://redirect.github.com/omgovich/colord/blob/HEAD/CHANGELOG.md#2110)

[Compare
Source](https://redirect.github.com/omgovich/colord/compare/v2.10.1...v2.11.0)

##### Minor Changes

- New `oklab` and `oklch` plugins to parse and convert OKLab and OKLCH
colors (CSS Color 4)

###
[`v2.10.1`](https://redirect.github.com/omgovich/colord/blob/HEAD/CHANGELOG.md#2101)

[Compare
Source](https://redirect.github.com/omgovich/colord/compare/b10c2f94457c3bc48af9533b555c308768465d51...v2.10.1)

##### Patch Changes

- Fix: Read the alpha byte of a HEX color exactly, so `#cc88` no longer
comes back as `#cccc8887` ❤️
[@&#8203;spokodev](https://redirect.github.com/spokodev)
- Fix: Stop `minify` from turning down an alpha hex that holds the color
exactly, and from returning nothing at all when every notation is
switched off

</details>

<details>
<summary>crowdin/github-action</summary>

###
[`v3.6.0`](https://redirect.github.com/crowdin/github-action/releases/tag/v3.6.0)

[Compare
Source](https://redirect.github.com/crowdin/github-action/compare/v3.5.1...v3.6.0)

#### What's Changed

- CLI
[5.6.0](https://redirect.github.com/crowdin/crowdin-cli/releases/tag/5.6.0)
by [@&#8203;andrii-bodnar](https://redirect.github.com/andrii-bodnar)

**Full Changelog**:
<https://github.com/crowdin/github-action/compare/v3.5.1...v3.6.0>

</details>

<details>
<summary>djlint/djLint (djlint)</summary>

###
[`v1.50.0`](https://redirect.github.com/djlint/djLint/blob/HEAD/CHANGELOG.md#1500---2026-11-11)

[Compare
Source](https://redirect.github.com/djlint/djLint/compare/v1.49.10...v1.50.0)

##### Bug fixes

- With Click 8.5.1 or newer, `djlint --help` no longer lists a blank
`SRC ...` row under "Other". The files to check are still shown in the
usage line.
- A template that is not valid UTF-8, or that djLint isn't allowed to
read or write, no longer aborts the run with a traceback and a request
to report a bug. djLint names the file and the reason, checks the rest
and still exits `2`, because that file went unchecked. `--github-output`
adds an error annotation on the file, and `--sarif` reports it as a
notification on a run marked as not successful.
- A configuration file djLint can't read, such as a `pyproject.toml`,
`djlint.toml` or `.djlintrc` with a syntax error or a file named by
`--configuration`, is now a usage error that exits `2`. djLint used to
print a red line and check the templates against its defaults, so the
run could pass. The same goes for a number setting with a value that
isn't a number, such as `max_line_length = "wide"`, and for a
`.djlint_rules.yaml` that isn't valid YAML or doesn't hold a list of
rules, which crashed with a traceback. An empty `.djlint_rules.yaml` no
longer crashes. In the Python API, `load_config` raises
`click.UsageError` for these.
- Ctrl+C exits `130`, as shells report an interrupted command, rather
than `1`, which means djLint found something. The same goes for `djlint
--lsp`.

###
[`v1.49.10`](https://redirect.github.com/djlint/djLint/blob/HEAD/CHANGELOG.md#14910---2026-11-07)

[Compare
Source](https://redirect.github.com/djlint/djLint/compare/v1.49.9...v1.49.10)

##### Packaging

- Ship a `py.typed` marker, so type checkers read the annotations of
`djlint.api`.
- Importing `djlint.api` no longer builds the command line, which takes
a little off the start of editors and other programs that use djLint
from Python. The command line moved out of the `djlint` package itself,
which still hands out `main`, `process` and `process_stdin` when they
are asked for.

</details>

<details>
<summary>docker/login-action</summary>

###
[`v4.8.0`](https://redirect.github.com/docker/login-action/releases/tag/v4.8.0)

[Compare
Source](https://redirect.github.com/docker/login-action/compare/v4.7.0...v4.8.0)

- Set Docker Hub OIDC token lifetime default to 1 hour by
[@&#8203;crazy-max](https://redirect.github.com/crazy-max) in
[#&#8203;1070](https://redirect.github.com/docker/login-action/pull/1070)
- Bump
[@&#8203;aws-sdk/client-ecr](https://redirect.github.com/aws-sdk/client-ecr)
and
[@&#8203;aws-sdk/client-ecr-public](https://redirect.github.com/aws-sdk/client-ecr-public)
to 3.1161.0 in
[#&#8203;1103](https://redirect.github.com/docker/login-action/pull/1103)
- Bump
[@&#8203;docker/actions-toolkit](https://redirect.github.com/docker/actions-toolkit)
from 0.107.0 to 0.109.0 in
[#&#8203;1105](https://redirect.github.com/docker/login-action/pull/1105)
- Bump vite from 7.3.6 to 7.3.7 in
[#&#8203;1101](https://redirect.github.com/docker/login-action/pull/1101)

**Full Changelog**:
<https://github.com/docker/login-action/compare/v4.7.0...v4.8.0>

</details>

<details>
<summary>un-ts/eslint-plugin-import-x (eslint-plugin-import-x)</summary>

###
[`v4.18.1`](https://redirect.github.com/un-ts/eslint-plugin-import-x/blob/HEAD/CHANGELOG.md#4181)

[Compare
Source](https://redirect.github.com/un-ts/eslint-plugin-import-x/compare/v4.18.0...v4.18.1)

##### Patch Changes

-
[#&#8203;599](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/599)
[`d9c8a4e`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/d9c8a4efc64ba719b0698fef7fd867bcc434c0e6)
Thanks
[@&#8203;SwastikTripathi](https://redirect.github.com/SwastikTripathi)!
- fix(core): don't load the optional `@typescript-eslint/utils` peer at
runtime, so the plugin loads again without it

-
[#&#8203;604](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/604)
[`28779e0`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/28779e094ccbcb634f7ef0ac8e892fce07817eff)
Thanks [@&#8203;gilbarbara](https://redirect.github.com/gilbarbara)! -
fix(extensions): stop requiring a `js` alias on extensionless imports
that resolve to a file whose extension is `never`, such as `.ts` with `{
js: 'always', ts: 'never' }`.

-
[#&#8203;600](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/600)
[`6172d1d`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/6172d1dc68d7e31f184d208ea40e24c5b9f661e1)
Thanks [@&#8203;thekhegay](https://redirect.github.com/thekhegay)! -
fix(first): the autofix puts imports above the decorators of `@dec()
export class` and on their own line when they have no semicolon, it
could leave code that doesn't parse in both cases

###
[`v4.18.0`](https://redirect.github.com/un-ts/eslint-plugin-import-x/blob/HEAD/CHANGELOG.md#4180)

[Compare
Source](https://redirect.github.com/un-ts/eslint-plugin-import-x/compare/v4.17.1...v4.18.0)

##### Minor Changes

-
[#&#8203;520](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/520)
[`802441c`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/802441c40eb4b630850011390dcc0236e73b1e0d)
Thanks
[@&#8203;SwastikTripathi](https://redirect.github.com/SwastikTripathi)!
- Add a `checkSelfReference` option to the `extensions` rule. When set,
a package's import of its own subpath export (e.g. `pkg/sub` from inside
`pkg`) is treated as a package import, so `ignorePackages` applies to
it.

-
[#&#8203;403](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/403)
[`f4d0a4b`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/f4d0a4b5927d7386a9a889c9581499d5e9ae7417)
Thanks [@&#8203;Zamiell](https://redirect.github.com/Zamiell)! -
`extensions`: when an import has no extension and cannot be resolved
as-is, try the extensions configured as `always` in `pattern` and use
the unique one that resolves for the fix or suggestion. If several
resolve, report the missing extension without guessing. When no
extension can be determined automatically, explain that in the `missing`
message instead of only reporting a bare missing extension.

-
[#&#8203;572](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/572)
[`fc17206`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/fc17206adca43658dae08f127e54ea8f5d201623)
Thanks
[@&#8203;SwastikTripathi](https://redirect.github.com/SwastikTripathi)!
- feat(no-duplicates): add a `whitelist` option listing entry points
that share one declaration file but are different modules, such as
`svelte` and `svelte/easing`

-
[#&#8203;504](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/504)
[`f10dcc4`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/f10dcc4a8250d432b47453cabe1f28af60a4c298)
Thanks [@&#8203;morgan-coded](https://redirect.github.com/morgan-coded)!
- Add a `"top"` mode to the `order` rule's `warnOnUnassignedImports`
option for requiring no-specifier ESM imports before assigned imports.

-
[#&#8203;502](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/502)
[`9c85ced`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/9c85ced6cb65536a598e3ae4228f4e5b5eb867bf)
Thanks [@&#8203;SukkaW](https://redirect.github.com/SukkaW)! - Rewrite
the module analysis core for performance boosts. The speedup depends on
your project, and we expect no performance regression in any setup — if
you measure one, please report it.

Rules like `named`, `default`, `namespace`, `no-cycle`, `no-deprecated`,
and many more, need to know what the modules you import actually export.
Until now, answering that meant running the full ESLint parser over
every one of those files — including everything you pull in from
`node_modules`.

  That core has been rewritten:

- Plain JavaScript is now read with
[`es-module-lexer`](https://redirect.github.com/guybedford/es-module-lexer)
instead of being parsed. Anything it can't read faithfully — TypeScript,
JSX, Flow — still goes through the ESLint parser exactly as before.
- Analysis is lazy. Much of the work now happens when a rule actually
asks for it, so enabling one rule no longer pays for what the others
would have needed.
  - Results are cached and shared between rules.

**There are no breaking changes: no configuration changes are needed,
and no behavior changes are intended.** Every rule should report exactly
what it reported before, with one known exception: an imported plain
JavaScript file that has a syntax error no longer gets a "Parse errors
in imported module" report. ESLint still reports the syntax error when
it lints that file itself. The full test suite passes, but there could
be some edge cases. If a rule starts reporting something it didn't
before, or stops reporting something it should, please open an issue
with a minimum reproduction — bug reports on this are very welcome.

-
[#&#8203;456](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/456)
[`7b78aae`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/7b78aae85bf85b7bc793a9254166c6cc73fd2e27)
Thanks [@&#8203;43081j](https://redirect.github.com/43081j)! - Add four
barrel file detection rules ported from `eslint-plugin-barrel-files`:
`avoid-barrel-files`, `avoid-importing-barrel-files`,
`avoid-namespace-import` and `avoid-re-export-all`.

`avoid-importing-barrel-files` checks every runtime way a module can be
referenced — static imports, re-exports (`export … from`, `export *
from`, `export * as ns from`), dynamic `import()` and CommonJS
`require()` — with type-only statements exempt.

-
[#&#8203;157](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/157)
[`89cfe42`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/89cfe424d1cb37c4ada195ddbebe90260b7108cf)
Thanks [@&#8203;Zamiell](https://redirect.github.com/Zamiell)! -
feat(no-rename-default): accept names derived from bare package paths
and add a `whitelist` option for modules that mangle their default
export names

##### Patch Changes

-
[#&#8203;562](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/562)
[`7cbe683`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/7cbe683d228ed2baf88fe6307e2544f17d00af7d)
Thanks [@&#8203;JounQin](https://redirect.github.com/JounQin)! -
perf(avoid-importing-barrel-files): skip the surface parse for a
dependency that cannot be a barrel

The rule sizes the runtime module graph behind every imported target,
and a
  target only becomes a candidate once its export count passes
`amountOfExportsToConsiderModuleAsBarrel`. A lexer-analyzed module
already
reports its export entries, so a count at or below the threshold settles
the
question without producing the exact export/declaration surface — one
parse
  saved per small plain-JS dependency.

Anything es-module-lexer does not read faithfully still goes through the
parser,
and a module whose source declares a default export is never ruled out:
the
properties of `export default { … }` are exports no entry count can see
(a
  `default` that `esModuleInterop` synthesizes does not count).

A declarator that binds no name — `export const {} = obj`, `export const
{ a: {} } = obj` — is no longer counted as an export by the barrel
surface: it
exports nothing, and counting it made the surface disagree with the
lexer's
  entry count.

-
[#&#8203;568](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/568)
[`225a5aa`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/225a5aae4ef876e0cdd8c9b966178714efd2dc8e)
Thanks
[@&#8203;SwastikTripathi](https://redirect.github.com/SwastikTripathi)!
- Fix `no-extraneous-dependencies` telling you to add a package that is
already in `devDependencies` or `optionalDependencies` when its import
resolves through `@types/*`

-
[#&#8203;579](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/579)
[`db16385`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/db16385a7f234186148a4fbaa515b63c79faee9b)
Thanks [@&#8203;thekhegay](https://redirect.github.com/thekhegay)! -
fix(core): keep the size of `settings` out of module and resolver cache
keys

Every key held the full `stableHash` text of `settings`, `parserOptions`
and the parser. One large value in shared `settings`, like a custom
alphabet from `eslint-plugin-perfectionist`, was copied into each key on
every resolve, so `no-cycle` and any other rule that resolves imports
could run out of memory. Keys now hold a short id per distinct hash.

-
[#&#8203;309](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/309)
[`4b9ea02`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/4b9ea02026781c4f1afd40859fb30a43722b4258)
Thanks [@&#8203;remcohaszing](https://redirect.github.com/remcohaszing)!
- Allow packages to import themselves in
`import-x/no-extraneous-dependencies` when the `exports` field is
defined in `package.json`; importing a package's own name without
`exports` is reported by the new `selfImport` message.

-
[#&#8203;565](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/565)
[`3d0f5a9`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/3d0f5a91583483a5c83e085b96420dda6c2d961e)
Thanks
[@&#8203;SwastikTripathi](https://redirect.github.com/SwastikTripathi)!
- fix(namespace, no-deprecated): don't report members of a parameter
that shadows a namespace import when the namespace is also used in the
same scope, e.g. in a type annotation

-
[#&#8203;539](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/539)
[`bb7b18b`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/bb7b18b7885233699430f207cbcdd86bae7cdb87)
Thanks
[@&#8203;SwastikTripathi](https://redirect.github.com/SwastikTripathi)!
- chore(deps): upgrade `es-module-lexer` from v2 to v3. The v3 API is a
complete redesign using discriminated union types (`StaticImport |
DynamicImport | ImportMetaRef` for imports, `DirectExport | Reexport |
ReexportAll` for exports) replacing numeric `d` fields and short
property names. The lexer route now resolves `export { x }` where `x`
comes from a non-namespace import as a reexport rather than an own
export, which is more semantically accurate.

-
[#&#8203;566](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/566)
[`4c66c87`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/4c66c87332858df44ce9668b6666213e4e8acff0)
Thanks
[@&#8203;SwastikTripathi](https://redirect.github.com/SwastikTripathi)!
- fix(export): don't report a namespace that only declares types as a
duplicate of a value with the same name

-
[#&#8203;536](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/536)
[`db674b5`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/db674b5aed81ec8aad7d59d9dc895df7fc92eaa1)
Thanks [@&#8203;SukkaW](https://redirect.github.com/SukkaW)! -
fix(export): check types and values separately

`export type * from` only re-exports types, so it no longer conflicts
with a value export of the same name, and a type reached through `export
*` no longer conflicts with a value. Duplicate types among re-exports
are now reported, as are a type-only export and a value export of the
same name, and ambient function overloads that clash with another
export. String-literal export names such as `"type:Foo"` are no longer
mistaken for type exports. Fixes
[#&#8203;414](https://redirect.github.com/un-ts/eslint-plugin-import-x/issues/414).

-
[#&#8203;594](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/594)
[`0c82c7e`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/0c82c7e0f8bb8c5a5212fe2339539fe372ebecdd)
Thanks [@&#8203;i1stG](https://redirect.github.com/i1stG)! -
fix(extensions): resolve directory imports to their index file in
autofixes and suggestions, and only offer rewrites of resolved imports
that point back to the same file.

-
[#&#8203;571](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/571)
[`2bc321d`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/2bc321dd56eb886857201689bab35b62006cdacd)
Thanks [@&#8203;TonyTech404](https://redirect.github.com/TonyTech404)! -
Fix the `extensions` rule treating an extension alias as a missing
extension. An import such as `./foo.js` that the resolver maps to
`foo.ts` now keeps its own extension instead of being reported as
missing `ts` and autofixed to `./foo.js.ts`. The `pattern` extension
inference also recognizes an extension alias, so an extensionless
`./foo` that resolves that way is fixed to `./foo.js`. The inference
only accepts a candidate that resolves to the same file, and an
ambiguous result is reported without a fix. Type-only imports and
exports (including inline `type` specifiers) are ignored before the
extension branches, so an aliased `.js` specifier is preserved when
`checkTypeImports` is off.

-
[#&#8203;512](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/512)
[`42dba04`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/42dba0465ff440f1d1660608af322c390d0dcc0b)
Thanks [@&#8203;LeulTew](https://redirect.github.com/LeulTew)! -
fix(extensions): honor `pathGroupOverrides` when no `pattern`,
`ignorePackages`, or `checkTypeImports` option is provided.

-
[#&#8203;575](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/575)
[`27112d6`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/27112d671a78f1c6adfc6cd919bd06a9998993bc)
Thanks
[@&#8203;SwastikTripathi](https://redirect.github.com/SwastikTripathi)!
- fix: keep trailing comments and line-scoped directives with their
targets. `first` inserts moved imports right after the
directive/statement, before any trailing comment, and withholds the
autofix for the whole group when a moved import has comments.
`newline-after-import` inserts the blank before a single-line trailing
comment (or after a multi-line one), so third-party directives such as
`prettier-ignore` keep their target. Both rules share the
`getTrailingComments` util.

-
[#&#8203;555](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/555)
[`27876f2`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/27876f2496556882be69245f3d85e5ea6c2f9a25)
Thanks [@&#8203;JounQin](https://redirect.github.com/JounQin)! -
perf(core): memoize `getExportKind` per module and name

  Rules ask for an export kind once per imported specifier and once per
namespace member access. Without a memo, every lookup re-walks all
`export *`
paths and re-resolves each target; on a 100-star barrel, 2,000 namespace
member accesses took \~5.7 s instead of \~0.1 s. Answers are cached per
  `(module, name, typeOnly)`, so the type-only and value answers stay
  independent.

-
[#&#8203;519](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/519)
[`f6a66a0`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/f6a66a01b56381d2bdf4ba87aba978479d475958)
Thanks [@&#8203;Cherry](https://redirect.github.com/Cherry)! - perf:
cache legacy resolver lookups per directory instead of re-resolving the
resolver package on every import resolution.

-
[#&#8203;570](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/570)
[`7254048`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/72540485d12bea99039f30a636ace9ab8ce84ead)
Thanks [@&#8203;devon-scythe](https://redirect.github.com/devon-scythe)!
- fix: support minimatch v9/v10/v11 and drop makeRe

minimatch v11 is the only release line with the fix for
GHSA-g3hv-75wg-m249.
It removes `makeRe()`, so `no-internal-modules` now matches its `allow`
and
  `forbid` globs with `Minimatch#match`.

-
[#&#8203;535](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/535)
[`66632ec`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/66632ec8738256c9df07b74849219e5a56f7ed0a)
Thanks
[@&#8203;SwastikTripathi](https://redirect.github.com/SwastikTripathi)!
- fix(core): send a `.js` file to the AST route when es-module-lexer
cannot read one of its exports. On the lexer fast path, an export the
lexer does not read was dropped from the module's export set as soon as
the file had any export it did read, so `hasExport`/`getExportNames` —
and `named`, `namespace`, `default`, `no-named-as-default` with them —
reported the name as missing. The lexer route now keeps only the
declaration heads whose exported names are read faithfully by
es-module-lexer v3 (`default`, `{`, `*`, `function`, `class`, `const`,
`let`, `var`) and bails on every unrecognised head as a conservative
fallback, including `module`, `using`, `await using`, `@dec class`,
`abstract class`, `declare`, `enum`, `const enum`, `namespace`, and
`interface` (v3 reads those, but they are not yet in the whitelist).

-
[#&#8203;534](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/534)
[`595f2d7`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/595f2d730f0a647f7a2a26fbb23680651f4ba753)
Thanks
[@&#8203;SwastikTripathi](https://redirect.github.com/SwastikTripathi)!
- fix(module-visitor): treat `import x = require('y')` as a module
reference, so every rule built on `moduleVisitor` (`no-unresolved`,
`no-cycle`, `extensions`, `no-extraneous-dependencies`,
`no-restricted-paths`, `no-absolute-path`, …) sees the specifier.
`export import x = require('y')` was missed too, because its
`ExportNamedDeclaration` has a `null` source. `no-cycle` and
`avoid-importing-barrel-files` keep ignoring the type-only form, `import
type x = require('y')`

-
[#&#8203;556](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/556)
[`19ff6c5`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/19ff6c5006ba5f1213366b20fa6ee0af07aa69b0)
Thanks
[@&#8203;SwastikTripathi](https://redirect.github.com/SwastikTripathi)!
- fix(namespace): report member access in decorator expressions by
walking up to the enclosing module scope.

-
[#&#8203;567](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/567)
[`b2afa70`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/b2afa70f839137b9b27e053b751389b3d1ea8226)
Thanks
[@&#8203;SwastikTripathi](https://redirect.github.com/SwastikTripathi)!
- fix(namespace): don't report a heritage clause that names a type from
a module resolved to JavaScript, which has no types to check against.

-
[#&#8203;526](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/526)
[`8f4f6b9`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/8f4f6b9922146d93168b1d17cd87c767659399f2)
Thanks [@&#8203;JounQin](https://redirect.github.com/JounQin)! - fix:
count `export * as ns from '…'` as a runtime dependency in the module
analysis core

`export * as ns from 'x'` loads `x` at runtime, but both `ModuleInfo`
construction paths omitted the edge, so graph traversal — and
`avoid-importing-barrel-files` in particular — could undercount the
modules an import pulls in. The namespace export metadata is unchanged,
and `export type * as ns from` stays type-only. Fixes
[#&#8203;525](https://redirect.github.com/un-ts/eslint-plugin-import-x/issues/525).

-
[#&#8203;541](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/541)
[`bbd0026`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/bbd0026366bd4d1d19a9546450901e0d98c5f2a6)
Thanks [@&#8203;MFA-G](https://redirect.github.com/MFA-G)! -
fix(namespace): report members exported only as types

A name exported only as a type (`export type Foo`, `export interface
Foo`, `export type { Foo }`, `export type * from`) is erased at runtime,
so accessing it as a member of an imported namespace (`ns.Foo`, `const {
Foo } = ns`, `<ns.Foo />`) is now reported. Classes, enums and names
that are both a type and a value are still accepted, and unresolvable
names still fail open. Fixes
[#&#8203;540](https://redirect.github.com/un-ts/eslint-plugin-import-x/issues/540).

-
[#&#8203;543](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/543)
[`35fc9bf`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/35fc9bf6f3fa069b578f9fbf8f5652428ca3cd18)
Thanks [@&#8203;thekhegay](https://redirect.github.com/thekhegay)! -
fix(newline-after-import): ignore comments between two imports when
`considerComments` is enabled, matching `eslint-plugin-import`.

-
[#&#8203;577](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/577)
[`5169813`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/516981368694ddcad9f3e13ab239f39e7d77dcf4)
Thanks
[@&#8203;SwastikTripathi](https://redirect.github.com/SwastikTripathi)!
- fix(newline-after-import): treat a comment on the import's own line as
part of the import

With `considerComments`, a trailing comment such as `import a from 'a'
// why`
was taken as the comment after the import, so the rule reported even
with an
empty line before the next statement. The autofix also inserted the new
lines
between the import and its trailing comment, moving the comment onto its
own
  line. Both now skip comments that start on the statement's last line.

The fix is withheld when any trailing comment is a line-scoped directive
(`eslint-disable-next-line`, `@ts-ignore`, `@ts-expect-error`), so the
directive
keeps its target, and comments inside the following statement no longer
satisfy
  the blank-line check.

-
[#&#8203;591](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/591)
[`65ea15c`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/65ea15c3201688543356b10ef23b79eed624072a)
Thanks
[@&#8203;SwastikTripathi](https://redirect.github.com/SwastikTripathi)!
- fix(no-absolute-path): prefix `./` when the fixed path starts with a
dot directory such as `.config/`, which would otherwise turn into a
package import

-
[#&#8203;507](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/507)
[`aa1071d`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/aa1071d6eff519364a35573647c07593aec2da80)
Thanks [@&#8203;BridgeAR](https://redirect.github.com/BridgeAR)! -
Reduce `no-cycle` CPU usage for converging dependency graphs.

-
[#&#8203;518](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/518)
[`c45cfb9`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/c45cfb9757c19e7e38dfeb40d1b4b701b22378b5)
Thanks
[@&#8203;wimvanschandevijl](https://redirect.github.com/wimvanschandevijl)!
- fix(no-cycle): `allowUnsafeDynamicCyclicDependency` no longer hides
static-only cycles that happen to sit in the same module as an unrelated
dynamic import

Previously, `no-cycle`'s traversal bailed out of a module's **entire**
remaining import list as soon as it found one path where any declaration
was dynamic - `return` rather than `continue` inside the loop over
`m.imports`. That meant:

- a purely static cycle declared *after* an unrelated dynamic import
earlier in the same file went unreported, and
- a path imported both statically and dynamically (the static
declaration on its own closing a real cycle) was skipped entirely,
because "any declaration to this path is dynamic" discarded the static
declaration too.

Both are now handled per-declaration: only the dynamic declarations for
a path are dropped when `allowUnsafeDynamicCyclicDependency` is set, and
only that one path is skipped when nothing traversable remains - the
module's other, unrelated import paths (and any static declaration to
the very same path) are still checked. See
[#&#8203;515](https://redirect.github.com/un-ts/eslint-plugin-import-x/issues/515)
for the repro that found this.

-
[#&#8203;538](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/538)
[`b6a674b`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/b6a674b235327bede9e598ba2a60dfa23a5e103c)
Thanks [@&#8203;b84330808](https://redirect.github.com/b84330808)! -
fix(no-cycle): report cycles through side-effect imports such as `import
'./foo'` and `import {} from './foo'`. They have no specifiers, so they
were skipped as if they were type-only imports. The unambiguous-module
prefilter also recognizes them now, so a file whose only module syntax
is a side-effect import is analyzed on the AST route too, as it already
was on the lexer route

-
[#&#8203;585](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/585)
[`8777312`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/87773128953307a62ca21b3eb87bc8008ce5bb1d)
Thanks [@&#8203;thekhegay](https://redirect.github.com/thekhegay)! -
fix(no-duplicates): do not treat commas inside comments as specifier
separators in the autofix

-
[#&#8203;581](https://redirect.github.com/un-ts/eslint-plugin-import-x/pull/581)
[`76e97db`](https://redirect.github.com/un-ts/eslint-plugin-import-x/commit/76e97db501b31ff52c35683ff3f7c31640ab6b0c)
Thanks [@&#8203;thekhegay](https://redirect.github.com/thekhegay)! -
fix(no-duplicates): imports of one path with different attributes are
not duplicates, and the autofix no longer drops an attribute, mistakes
the braces of `with {...}` for the braces of the s

> [!IMPORTANT]
> ✂ PR body was truncated to here.


</details>

---

### Configuration

📅 **Schedule**: (UTC)

- Branch creation
  - Between 12:00 AM and 03:59 AM, only on Monday (`* 0-3 * * 1`)
- Automerge
  - At any time (no schedule defined)

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get
[config
help](https://redirect.github.com/renovatebot/renovate/discussions) if
that's undesired.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend Renovate
CLI](https://redirect.github.com/renovatebot/renovate).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4yMTAuMCIsInVwZGF0ZWRJblZlciI6IjQ0LjIxMC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->

---------

Co-authored-by: silverwind <me@silverwind.io>
2026-11-16 15:38:49 +00:00
Mitrahsoftandsilverwind a006a8ae9c fix(markup): render same-repo PR URLs as !N with external issue tracker (#40344)
When a repository uses an external issue tracker, `#N` links to the
external tracker and local pull requests are referenced as `!N`, as
merge messages already do for the title and `Merge pull request !N`. But
full pull request URLs, like the one in `Reviewed-on:`, were always
shortened to `#N`, which looks like a reference to external issue N.

Same-repo pull request URLs are now rendered as `!N` when an external
tracker is configured. Issue URLs, cross-repo links and repositories
without an external tracker are unchanged. Owner and repo are now read
from the parsed URL path, so a `/` in the query or fragment no longer
misattributes the link.

Before:
<img width="1100" height="560" alt="beforeResolving"
src="https://github.com/user-attachments/assets/c48e4219-73b4-42ba-9d10-3f5ce83d5832"
/>

After:
<img width="1100" height="560" alt="afterResolving"
src="https://github.com/user-attachments/assets/26348939-6d55-419b-bf4b-0cfcd5a2f17a"
/>

Fixes: https://github.com/go-gitea/gitea/issues/35050
Assisted-by: Claude Code:claude-opus-5-5

---------

Co-authored-by: silverwind <me@silverwind.io>
2026-11-16 14:15:52 +00:00
e2f451ae11 fix(issues): match no issue when filtering by a non-existent assignee (#40278)
Filtering the dashboard issue and pull lists by a non-existent assignee
listed all unassigned items, because the username lookup returned
"(none)", which the issue search reads as "no assignee".

- Unknown poster and assignee names resolve to the Ghost user instead,
so they no longer match unassigned items
- System user names like `gitea-actions` resolve to their IDs, so their
issues can be filtered by poster

Fixes: https://github.com/go-gitea/gitea/issues/40276

Assisted-by: DeepSeek:V4.1-Flash
Assisted-by: Claude Code:claude-opus-5-5

---------

Co-authored-by: Stella <353917373+Stella050408@users.noreply.github.com>
Co-authored-by: silverwind <me@silverwind.io>
2026-11-14 07:41:33 +00:00
1f614953a2 enhance: allow admins to force user activity visibility (#40002)
Adds `[service] FORCE_USER_ACTIVITY_VISIBILITY` so admins can force the
activity of all users to be `public` or `private`, e.g. for company
instances that require public activity.

- When the value changes, the next start overwrites the "Hide Activity"
setting of all users. New users get the forced value too.
- The "Hide Activity" checkbox is disabled with an explanatory tooltip
while forced, and `PATCH /api/v1/user/settings` rejects a conflicting
`hide_activity` with 422.

| Before | After |
| --- | --- |
| <img width="122" height="17" alt="before"
src="https://github.com/user-attachments/assets/d138acec-5d40-4a0a-881c-0097e5197a8f"
/> | <img width="258" height="46" alt="after"
src="https://github.com/user-attachments/assets/7e8f7d1b-3303-4473-8d3b-aa35ef8fb20d"
/> |

Fixes: https://github.com/go-gitea/gitea/issues/37961

Assisted-by: Claude Code:claude-opus-5-5

---------

Co-authored-by: bircni <bircni@icloud.com>
Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
2026-11-13 17:32:29 +00:00
silverwindandClaude 53aafd7ee1 fix(actions): include previous values in edited payloads (#40179)
Actions `edited` payloads omitted `changes`, so workflows could not see
previous values. Issue/PR title and body edits now carry
`changes.title`/`changes.body`, base branch changes add
`changes.base.ref`/`changes.base.sha` (and `changes.ref` now holds the
old branch, not the new one), release edits carry
`changes.name`/`changes.body`.

_Written by Claude (Opus 5.5)._

---------

Co-authored-by: Claude (Opus 5.5) <noreply@anthropic.com>
2026-11-13 08:43:13 +00:00
Rafail Giavrimisandsilverwind 38389f00be feat: unify code search, add search API (#39403)
Adds GitHub-style code search endpoints and makes code search behave the
same in the web UI and the API, whether it runs on git grep, bleve or
Elasticsearch.

- `GET /repos/{owner}/{repo}/code/search` searches any branch, tag or
commit with git grep, so it works without the code indexer.
- `GET /search/code` searches the default branches of all accessible
repositories with the code indexer.
- One query syntax everywhere: every term must match a file's content or
path, case-insensitively. It supports `"phrases"`, `/regexp/` (git grep
only) and the `path:`, `language:`, `repo:`, `user:` and `org:`
qualifiers. Invalid queries return an error.
- All engines apply the same include, exclude, vendored and size rules,
and return every match. The web UI shows them as multiple snippets per
file with the matched text highlighted.

<img width="359" height="295" alt="image"
src="https://github.com/user-attachments/assets/59b7aa66-b1dc-4938-9ef9-66668ae08d7c"
/>

Fixes: https://github.com/go-gitea/gitea/issues/10706
Fixed: https://github.com/go-gitea/gitea/issues/15841
Fixes: https://github.com/go-gitea/gitea/issues/31375
Related: https://gitea.com/gitea/gitea-mcp/issues/280
Docs: https://gitea.com/gitea/docs/pulls/615

AI usage disclosure: Yes, I used AI to write code, review changes and
verify the factuality of the overview I provided. I take full
responsibility for the code in this PR.

---------

Co-authored-by: silverwind <me@silverwind.io>
2026-11-13 07:24:37 +00:00
c4fb82858e enhance(lfs): report status and body on non-JSON LFS error responses (#40331)
A push mirror or migration pointed at a remote that has LFS disabled
fails with a confusing error like `readObjectStart: expect { or n, but
found N ... |Not Found`. That comes from decoding the batch endpoint's
plain-text "Not Found" response as JSON.

Read the response body before decoding and, when it is not valid LFS
JSON, return the HTTP status together with the raw body so the message
points at the real cause. Responses that are proper LFS JSON errors
behave as before.

Fixes: https://github.com/go-gitea/gitea/issues/34897

Assisted-by: Claude Code:claude-opus-4-8

---------

Co-authored-by: amalsaidov <amalsaidov@users.noreply.github.com>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
2026-11-12 07:10:04 +00:00
wxiaoguang 55539aad51 refactor(git): parse git stdout correctly (#40326)
* Introduce RunWithScannerSplit to correctly handle git stdout parsing
* Introduce IsEmptyObjectID for faster empty object ID checking
* Remove unnecessary and confusing ErrNotEmpty
2026-11-12 06:19:10 +00:00
wxiaoguangandsilverwind b3422c0920 refactor: clean up error system (#40328)
1. `ctx.ServerError("LogMessage", err)` is very messy and useless. When
the log is printed, it already contains the caller's file and line
number
2. `ctx.NotFound(nil)` and `ctx.NotFound(err)` were abused a lot, now
only `ctx.NotFound()`

---------

Co-authored-by: silverwind <me@silverwind.io>
2026-11-11 17:07:57 +00:00
Shudhanshu Singhandsilverwind db23b5a192 fix(api): keep webhook settings that are omitted in an edit request (#40282)
`PATCH .../hooks/{id}` previously reset webhook events to push-only and
cleared the branch filter and authorization header whenever they were
not included in the payload. Disabling a hook with `{"active": false}`
silently destroyed its configuration.

`BranchFilter` and `AuthorizationHeader` are now pointers so omitted
fields remain untouched, while empty strings can still be passed to
clear them explicitly.

---------

Co-authored-by: silverwind <me@silverwind.io>
2026-11-10 19:26:22 +00:00
wxiaoguangandsilverwind d1d702bea9 refactor: user error system (#40308)
Introduce "FlashErrorAuto" for "XxxErrorAuto" family and simplify the
error handling logic.

* Use ErrorUnwrapForHTML for web error messages 
* Use ErrorUnwrapForUser for api error messages
* Make Flash message can take up to about 3000 bytes

Next step: completely refactor "ctx.ServerError"

---------

Co-authored-by: silverwind <me@silverwind.io>
2026-11-10 16:29:36 +00:00
Shivansh Gargandwxiaoguang 640cd615c4 feat: restrict pull/issue creation on access basis (#40069)
Adds a repository-level **"Restrict to collaborators"** option under the
Issues and Pull Request unit settings. When enabled, only users with
collaborator access to the base repository (owner, team members, or
explicit collaborators) can open issues or pull requests against it.

Public repositories often need to be visible/cloneable by everyone, but
owners may want to limit who can open pull requests (e.g. restrict to an
internal team while still keeping the code public)

* Fixes: https://github.com/go-gitea/gitea/issues/40015
* Fixes: https://github.com/go-gitea/gitea/issues/31890
* Fixes: https://github.com/go-gitea/gitea/issues/28021
* Fixes: https://github.com/go-gitea/gitea/issues/14801

---------

Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
2026-11-10 00:53:49 +00:00
wxiaoguang 772f365254 refactor: use RunWithStderr for git commands (#40295)
If the stderr output is not handled, then it needs to use RunWithStderr
to make sure the git error message is included in the returned error.
Otherwise, when the git command fails, the error log won't show useful
information.

Ref:

* #39795 : no useful information in log messages
*
https://github.com/go-gitea/gitea/pull/40160#pullrequestreview-5752720866
2026-11-09 17:59:52 +00:00
bircniandsilverwind e0b2f3425e fix(actions): run pull_request workflows on the merge commit (#40076)
`pull_request` workflow runs checked out the PR head, so a PR could pass
CI and still break the base branch once merged.

Gitea now maintains `refs/pull/<index>/merge`, a test merge of the head
into the base branch, for open pull requests. It is updated on creation
and mergeability checks and removed on close or merge.

- `pull_request` runs read their workflows from the test merge and
expose it as `github.ref`, `github.sha` and
`github.event.pull_request.merge_commit_sha`. Commit statuses, the API's
`head_sha`, `workflow_run` payloads and `paths` filters stay on the
head.
- Runs fall back to the head when the merge conflicts, the pull request
is closed or git is older than 2.40.
- Hidden refs keep each run's test merge (`refs/gitea/run/<id>`) and
merged commits (`refs/gitea/pull/<index>/merged`) from `git gc`, for
reruns and after the base branch is deleted or force-pushed.

Fixes: https://github.com/go-gitea/gitea/issues/27039
Fixes: https://github.com/go-gitea/gitea/issues/13134
Fixes: https://github.com/go-gitea/gitea/issues/30972
Docs: https://gitea.com/gitea/docs/pulls/617

---------

Co-authored-by: silverwind <me@silverwind.io>
2026-11-09 12:42:40 +00:00
7b1cde99d0 perf(charset): skip plain ASCII text when escaping control characters (#39937)
Every line of file, blame, diff and code preview views goes through
`EscapeControlHTML`, which streamed it through a 32 KiB read buffer and
copied every tag and text part. Views render the `EscapeStatus` before
the content, so every caller holds the complete HTML and streaming can't
help. It is now escaped in one pass over the string and returned
unchanged when nothing needs escaping.

- Skip text of printable ASCII, tabs and newlines, such lines return
immediately
- Render markup and wiki pages into a buffer instead of a pipe and
goroutine, and remove `EscapeControlReader`
- Analyze long text parts in windows overlapping by the detection
context, which bounds memory without changing results
- Escape invalid bytes before a tag, they were moved into the tag part
unescaped and could hide a `<math>` tag

| | before | after |
|---|---|---|
| ASCII line | 5.1 µs, 59 allocs | 0.08 µs, 1 alloc |
| line with one `é` | 3.9 µs, 30 allocs | 0.29 µs, 3 allocs |
| 150 KB document | 2.5 ms, 5.6 MB | 0.27 ms, 0.6 KB |

---------

Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Co-authored-by: silverwind <me@silverwind.io>
2026-11-09 03:42:30 +00:00
Lunny Xiaoandsilverwind 1554b6c939 feat!: remove repository adopt feature (#40181)
Remove the "adopt unadopted repositories" feature. Adopting assumes a
fixed repository storage path on disk, which makes the storage path hard
to change. It is mostly used once for migrations, and the [Gitea
importer](https://gitea.com/gitea/importer) covers that after the
repositories are moved out of the repository root. The docs are updated
in https://gitea.com/gitea/docs/pulls/639.

- Remove the admin and user adopt pages, the `/admin/unadopted` API
endpoints and the adopt notifier hook
- Remove the `ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES` and
`ALLOW_DELETION_OF_UNADOPTED_REPOSITORIES` settings
- The user "Repositories" settings page only lists the user's
repositories
- Repository files without a database record must now be removed from
disk by the administrator

Assisted-by: Codet:claude

---------

Co-authored-by: silverwind <me@silverwind.io>
2026-11-08 18:38:23 +00:00
wxiaoguang 3699309edd feat: support jpeg-xl (jxl) (#40283)
Major browsers (Chrome/Firefox/Safari) all support it now,
https://developer.chrome.com/blog/jpeg-xl-in-chrome

* Fix #16629
2026-11-08 15:24:46 +00:00
silverwind cd92c6a008 fix: paste copied code as text, not as a markdown table (#40053)
Copying lines from a diff, file view, blame, code search or code preview
and pasting them into a comment on Gitea or GitHub produced a markdown
table with escaped pipes and stripped indentation. Both use
`@github/paste-markdown`, which converts copied HTML tables unless they
carry `data-paste-markdown-skip`, as GitHub's own code tables do.
Gitea's code tables now set it too.

The test is a bit more complicated because of a upstream bug which
causes `paste-markdown` to insert pasted content twice, once
https://github.com/github/paste-markdown/pull/128 is merged and
released, the negative assertion could be removed.

---------

Signed-off-by: silverwind <me@silverwind.io>
2026-11-08 09:01:50 +00:00
silverwind 51879941dc enhance: improve commit and compare link rendering (#40154)
Commit, compare and SHA links render the SHA in code with the rest of
the URL after it, and links to other repositories get an `owner/repo@`
prefix like references do.

- Abbreviated SHAs, branch compares and `<url>` autolinks now render as
commit links
- Pull request commit URLs no longer break into an issue reference plus
stray text
- Only routes that take a SHA are shortened, so file and API URLs stay
plain

Replaces https://github.com/go-gitea/gitea/pull/36725

<img width="620" alt="Commit links before and after"
src="https://github.com/user-attachments/assets/5919c8a0-94e3-4148-ad11-6944bf790572"
/>
2026-11-07 22:43:07 +00:00
87a703819b fix(queue): bump levelqueue to v0.5.0 and remove workarounds (#40219)
levelqueue v0.5.1 fixes this upstream
(https://gitea.com/lunny/levelqueue/pulls/8), so this now only bumps the
dependency.

A push wrote "high" before the payload, so an interrupted push left an
id counted with no key. `LPop` then returned `ErrNotFound` without
advancing "low" and the wrapper retried forever: nothing popped, no
worker started, later items unreachable. All were only fixable by
clearing the queue, losing the backlog:
- https://github.com/go-gitea/gitea/issues/32006 — mail, 0 workers
- https://github.com/go-gitea/gitea/issues/28919 — mirror, "already in
queue"
- https://github.com/go-gitea/gitea/issues/33862 — archives hanging
- https://github.com/go-gitea/gitea/issues/33882 — self-healing request

v0.5.1 writes counter and payload in one batch, moves the counters past
missing keys, and repairs leftover unique-queue set entries, so affected
instances recover on their next pop.

No test: the behaviour lives in the dependency, which covers it in its
own `recover_test.go`.

---------

Signed-off-by: wxiaoguang <wxiaoguang@gmail.com>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
2026-11-07 22:26:53 +00:00
Lazizbek Ergashevandsilverwind 884884308d fix(pull): don't add a timeline entry for pending API reviews (#40260)
Pending reviews created through the API went through `SubmitReview`,
which added a timeline entry and sent notifications before the review
was submitted, so submitting it later showed the review twice.

- Pending reviews skip the timeline entry and notifications until
submitted, like on GitHub
- `CreatePullReview` rejects comments without a `path` or a positive
line with 422, like GitHub
- Already duplicated reviews stay as they are

Fixes https://github.com/go-gitea/gitea/issues/40259

Assisted-by: Claude Code:claude-opus-5-5

---------

Co-authored-by: silverwind <me@silverwind.io>
2026-11-07 14:19:50 +00:00
Mitrahsoftandsilverwind 3aca9c8fb7 enhance(actions): create commit status for workflow_dispatch runs (#39961)
Runs triggered by `workflow_dispatch` never created a commit status, so
the commit showed no sign that a workflow ran on it.

- Post the status on the run's commit, e.g. `ci / e2e
(workflow_dispatch)`. `schedule` runs stay unchanged.
- These statuses don't count for pull requests. They don't show in a
PR's checks and can't satisfy or fail its required checks, even through
broad globs like `ci / e2e*`.

Closes https://github.com/go-gitea/gitea/issues/39639

---------

Co-authored-by: silverwind <me@silverwind.io>
2026-11-07 12:55:19 +00:00
wxiaoguang a165fdb63c refactor: lazy init global regexp variables (#40269)
Gitea binary is an all-in-one program.

It doesn't make sense to compile dozens or even hundreds of regexps for
git hook sub commands.
2026-11-07 11:56:56 +00:00
silverwindandwxiaoguang baccc2d7cd fix: truncate strings on character boundaries (#40267)
Byte slicing like `t.Description[:255]` can split a multi-byte character
and store invalid UTF-8. Team descriptions were also cut to 255 bytes
although their `MaxSize(255)` validation allows 255 characters.

Team descriptions now truncate by runes. Signup user agents, Actions log
lines and access log request IDs use `util.TruncateStringBytes`, which
now returns short strings untouched.

---------

Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
2026-11-07 11:15:28 +00:00
5d9bfa1e14 feat(packages): add private Terraform module registry (#38040)
Adds a Terraform module registry package type implementing the [module
registry
protocol](https://developer.hashicorp.com/terraform/internals/module-registry-protocol),
so `terraform init` and Terragrunt `tfr://` can resolve modules from
Gitea:

```hcl
module "vpc" {
  source  = "gitea.example.com/owner/vpc/aws"
  version = "~> 1.0"
}
```

- Modules are uploaded with `PUT
/api/packages/-/terraform/modules/{owner}/{name}/{provider}/{version}`
as a `.tar.gz` with the module at its root, stored verbatim and
immutable.
- `X-Terraform-Get` is a short-lived signed URL because Terraform sends
no credentials when downloading the archive.
- The package page shows install snippets, README, the root module's
inputs, outputs and providers, and `modules/*` submodules.
- Metadata is read by a small in-tree HCL scanner instead of
`hashicorp/hcl/v2`, which would add 5 modules and ~1.4 MB to the binary.

Docs: https://gitea.com/gitea/docs/pulls/433

---------

Signed-off-by: Michael Lopez <mickael.lopez@gmail.com>
Co-authored-by: TheFox0x7 <thefox0x7@gmail.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: silverwind <me@silverwind.io>
2026-11-07 10:45:05 +00:00
7efb5c055f fix(markup): recognize issue references next to CJK punctuation (#40097)
Issue references next to non-ASCII characters, common in Chinese and
Japanese text, are ignored: `修复#1`, `(#2)` or `Closes #3,` create no
link or cross reference.

Like on GitHub, any non-ASCII character may now precede `#123`, `!123`
or `owner/repo#123`, and anything but a word character may follow it.
Dead trailing-space handling in the reference and mention search is
removed.

I used Claude Code to write this change.

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
2026-11-07 10:14:47 +00:00
Mitrahsoftandsilverwind b6c291f87a fix(api): honor branch protection force push and allowlist options on create and edit (#39990)
The branch protection API handled push and force push options
inconsistently. Create dropped force push unless push was enabled, and
edit ignored allowlist fields unless their parent was set to true in the
same request.

- Create treats force push independently of push, like edit and the web
UI. Enforcement is unchanged.
- Edit applies `enable_push_whitelist`, `enable_force_push_allowlist`
and both deploy key flags against the rule's resulting state, like the
deletion fields. `{"enable_push_whitelist": false}` now disables the
whitelist instead of being ignored.
- Documents that `enable_force_push_allowlist` requires
`enable_force_push` on create.

Fixes https://github.com/go-gitea/gitea/issues/35121

---------

Co-authored-by: silverwind <me@silverwind.io>
2026-11-07 09:34:21 +00:00
Alan Hsuandwxiaoguang df4544a58b fix(web): handle TypeCastError when building form validation messages (#40212)
Fixes https://github.com/go-gitea/gitea/issues/40210

---------

Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
2026-11-06 23:27:06 +00:00
silverwind ede9ec3e10 fix: stop discarding file close and test setup errors (#39987)
- Fix
https://github.com/go-gitea/gitea/security/quality/rules/go%2Funhandled-writable-file-close,
ignored close errors hide failed flushes, which could lose rotated logs
and truncate authorized_keys
- Fix `TestProjects` fixture reset, from
https://github.com/go-gitea/gitea/security/quality/ai-findings,
`TruncateBeans` rejected the table names and the ignored error let the
test run against fixture data
2026-11-06 20:45:17 +00:00
silverwind 7e18e81c7d refactor: remove duplicated and dead Go code (#40244)
Pure refactors with no behavior change, mostly reusing existing helpers
and dropping duplicated or dead code. Net −222 lines.

- Reuse existing helpers instead of inlined copies: `getIssueIndex`,
`NewLabel`, `ToCommitUser`, `GetPackageFileDescriptors`,
`util.SplitTrimSpace`
- Merge copy-pasted blocks in review comment deletion, project deletion
and the pre/post-receive hook templates
- Drop dead code: an error `toStringKeys` never returned, impossible
`bytes.Buffer` write errors, redundant nil-map branches, a `base64`
wrapper
- Use stdlib where it fits: `strings.Cut`, `bytes.IndexAny`,
`cmp.Compare`, `min`/`max`, `slices.Concat`, map lookups instead of key
scans
2026-11-06 11:59:49 +00:00
Shivansh Gargandsilverwind a5201dc427 feat(release): allow setting a release as the latest (#40214)
Gitea picks the latest release by commit date, while GitHub keeps an
explicit pointer, so repositories migrated from GitHub could show a
different latest release than their source. Fixes
https://github.com/go-gitea/gitea/issues/35273.

- Add a "Set as Latest Release" checkbox and GitHub's `make_latest` API
option. Without them, the newest stable release by commit date stays the
latest.
- Migrations from GitHub and Gitea carry over the source's latest
release.
- Migrated releases are dated by their commit like native ones, and
equally dated ones keep the source's order.

<img width="355" height="122" alt="Set as Latest Release checkbox"
src="https://github.com/user-attachments/assets/d35f5324-7ae0-4e9f-b73c-d3c90496fb00"
/>

---------

Co-authored-by: silverwind <me@silverwind.io>
2026-11-06 08:23:13 +00:00
silverwind 87ebf3b1ba feat(auth)!: remove support for obsolete OpenID 2.0 draft (#40231)
Remove OpenID 2.0 authentication. The spec is an obsolete draft, major
providers dropped it years ago, and the code keeps needing security
fixes like https://github.com/go-gitea/gitea/pull/39642. OpenID Connect
and OAuth2 are unaffected. Docs: https://gitea.com/gitea/docs/pulls/633.

- The `[openid]` settings, OpenID sign-in, sign-up and account
association are gone
- A migration drops the `user_open_id` table with all user OpenID URIs
- Accounts registered via OpenID have a random password and regain
access via password reset

Fixes: https://github.com/go-gitea/gitea/issues/1310
Fixes: https://github.com/go-gitea/gitea/issues/3521
2026-11-06 07:21:19 +00:00
wxiaoguang fd98ab5472 enhance(codeowners): support section / glob / file view display / skip review request (#40243)
Document: https://gitea.com/gitea/docs/pulls/634 ([doc PR
preview](https://gitea.com/gitea/docs/src/commit/955ae7d75c3377a15fafe465d85e484fc8dc7d2a/docs/usage/repository/code-owners.md))

1. If the pattern starts with `*` or contains `/*`, use our glob package
to parse it as glob to regexp
* Make it easier to use. Otherwise it's really ugly to keep writing a
lot of backslash escapes
2. Add GitLab-style "section" support
   * Fix #28926

```codeowners
[Section] @user
*.js
```

3. Add our annotation support, at the moment only need to support
review-request=true/false
    * Fix #40241

```codeowners
## review-request=false # this is global

*.js $user ## review-request=true # this is line-level

[Section] @user ## review-request=true # this is section-level
*.md
```

4. Add GitHub/GitLab-style "show codeowner when viewing a file"
    * Fix #28137
2026-11-06 07:19:51 +00:00
Andrew Barnesandsilverwind 4a9d49bb46 fix(dump): --file extension is ignored when --type is not set (#40235)
`gitea dump -f backup.tar.gz` without `--type` wrote a zip archive under
that name. Detecting the type from the file name was requested in
https://github.com/go-gitea/gitea/issues/24622 and intended in
https://github.com/go-gitea/gitea/pull/30240, but the check read the
still-empty result instead of `--file`, so every name fell back to zip.

A supported extension now selects the type, other names like `backup` or
`gitea.bak` still default to zip. An explicit `--type` still wins, and
its help text now mentions the detection.

AI disclosure: written with Claude Code (claude-opus-5-5).

---------

Signed-off-by: silverwind <me@silverwind.io>
Co-authored-by: silverwind <me@silverwind.io>
2026-11-05 18:30:31 +00:00
silverwind b7c1fb2a39 enhance: enable DEFAULT_DELETE_BRANCH_AFTER_MERGE by default for new repos (#39975)
Switch the `DEFAULT_DELETE_BRANCH_AFTER_MERGE` default from
https://github.com/go-gitea/gitea/pull/36917 to `true`, saving users a
click on merge for the most common action that deletes the PR branch on
merge.

Docs: https://gitea.com/gitea/docs/pulls/608
2026-11-05 18:26:32 +00:00
rafał przypek 3b9b8a8976 fix(packages): return empty Chef dependencies instead of null (#40237)
Fixes #40230

Cookbooks without dependencies are served with `"dependencies": null`
from the universe and version metadata endpoints. This happens because
`omitempty` drops the empty map when the metadata is stored. Chef
clients iterate over this value and Policyfile resolution crashes.

Supermarket returns `{}` for these cookbooks, Gitea now does too. The
fix checks whether dependencies are `nil` while building response,
returns an empty map if true. This way cookbooks that are already stored
are covered without a re-upload.

Tested with the Chef integration test and `chef-cli install`.

Assisted by Claude Code (claude-opus-5-5).
2026-11-05 15:19:09 +00:00
silverwind e87ac3a0f4 chore(deps): update go.yaml.in/yaml/v4 to v4.0.0 (#40222)
Update go-yaml from the rc.6 pseudo-version to the stable v4.0.0
release, and actionslib to v1.5.2, which does the same in
https://gitea.com/gitea/actionslib/pulls/32. The bump also brings in
actionslib v1.5.1.

v4 double-quotes the `on` key like yaml.v3 did, so one jobparser fixture
changes. Runner counterpart: https://gitea.com/gitea/runner/pulls/1381.

Fixes: https://github.com/go-gitea/gitea/issues/40145
2026-11-05 07:25:10 +00:00
Shivansh Gargandsilverwind be297b7e05 fix(webhook): fire repository event on repository transfer (#40200)
Transferring a repository fired no `repository` webhook. It now sends a
`transferred` action shaped like GitHub's, with the previous owner in
`changes.owner.from.user` or `changes.owner.from.organization`. Like
GitHub, it goes to the new owner's webhooks, plus the repository's own
and system webhooks.

- Chat webhooks render "Repository transferred from <owner>".
- Actions workflows are unaffected, no trigger matches `repository`
events.

Fixes https://github.com/go-gitea/gitea/issues/33584

---------

Co-authored-by: silverwind <me@silverwind.io>
2026-11-04 17:25:51 +00:00
Myers Carpenterandsilverwind 58279e39fd fix(actions): match pull_request unlabeled on label removal (#40215)
Fixes https://github.com/go-gitea/gitea/issues/34317

Removing a label from a pull request still started workflows with
`types: [labeled]` and never matched `types: [unlabeled]`.
https://github.com/go-gitea/gitea/pull/34316 derived
`labeled`/`unlabeled` from the added and removed labels for issues only,
while pull requests kept mapping every `label_updated` to `labeled`.
Both events now share one conversion, so they cannot drift apart again.

Two other label changes also triggered the wrong workflows:

- Clearing all labels started no `unlabeled` workflow, because the
Actions notifier ignored it
- Replacing labels reported every old label as removed, so a replace
that kept a label also matched `unlabeled`

AI disclosure: written with Claude Code (claude-opus-5-5), session
https://claude.ai/code/session_01Kw9ySGNd4ynmyX9GcVdUfw

---------

Co-authored-by: silverwind <me@silverwind.io>
2026-11-04 17:24:33 +00:00
ab295e62e4 fix(markup): make heading anchors match GitHub for whitespace and combining marks (#40195)
Heading anchors now keep the same characters as GitHub: letters, marks,
decimal and letter numbers, connector punctuation and alphabetic
symbols, with ASCII spaces turned into `-`. The rule follows
[github-slugger](https://github.com/Flet/github-slugger), whose fixtures
are generated from real GitHub renders.

- Other whitespace, including newlines in multi-line headings, is
dropped instead of becoming `-`, so `1<em space>ab` gets `#1ab`
- Combining marks are kept, so `हिन्दी` no longer becomes `हनद`
- Other numbers like `²` and `①` are dropped

Fixes https://github.com/go-gitea/gitea/issues/27754

This PR was written with Claude Code.

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: silverwind <me@silverwind.io>
2026-11-04 05:51:12 +00:00
wxiaoguangandsilverwind d919301d36 refactor: remove UnmarshalHandleDoubleEncode patch and fix repo unit TODO (#39998)
Remove the `UnmarshalHandleDoubleEncode` runtime workaround for an old
xorm bug, and normalize legacy double-encoded JSON in `repo_unit.config`
and `login_source.cfg` with a migration instead.

- Config `FromDB` no longer fails on corrupted values. A broken auth
source is deactivated, so admins can still fix it in the admin panel
- Remove `ProjectsConfig.GetProjectsMode`, `FromDB` already defaults
`ProjectsMode`

Actually it doesn't need so many changes, just because AI thinks it
should handle "corrupted database value" for auth sources.

---------

Signed-off-by: wxiaoguang <wxiaoguang@gmail.com>
Co-authored-by: silverwind <me@silverwind.io>
2026-11-04 05:28:49 +00:00
666e6e2d17 fix(web): allow clearing the full name in profile settings (#40186)
Clearing "Full Name" in the profile settings shows success but keeps the
old value: since #31959 it is only updated when non-empty, because the
input is disabled (not submitted) when `change_full_name` is disabled.

Use `*string` for the field, so a missing field keeps the value and an
empty one clears it. With `change_full_name` disabled, any submitted
value (including empty) is now rejected. Not `optional.Option[string]`,
because `MaxSize` would count slice elements instead of characters.

Fixes #40185

---
AI disclosure: written with Claude Code (claude-opus-5-5) and tested
locally.

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Co-authored-by: silverwind <me@silverwind.io>
2026-11-04 01:42:41 +00:00
Gaurav Dubeyandsilverwind f26a314636 fix(api): keep wiki page name when editing with an empty title (#40153)
Match `PATCH /repos/{owner}/{repo}/wiki/page/{pageName}` document "leave
empty to keep unchanged"

Fixes #39179

---------

Co-authored-by: silverwind <me@silverwind.io>
2026-11-03 16:20:39 +00:00
5c68ba3e0a fix(repo): avoid deadlock when updating language stats concurrently (#40167)
The `repo_stats_update` queue only deduplicates waiting items, so
several workers can index the same repository at once, then
`UpdateLanguageStats` can lead to transaction deadlock.

Use a global lock to avoid concurrent updates, and also helps
https://github.com/go-gitea/gitea/pull/39342 to avoid duplicate updates.

---------

Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
2026-11-03 16:18:27 +00:00
silverwindandwxiaoguang 5c723ee0fd refactor(markdown): remove goldmark-highlighting (#39751)
Render fenced code blocks with Gitea's own code block renderer instead
of `goldmark-highlighting`, using the managed lexer lookup from
`modules/highlight`. Indented and fenced blocks now share one rendering
path.

Rendered output is unchanged. The trailing newline is stripped on copy
in the frontend since https://github.com/go-gitea/gitea/pull/39755.

---------

Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
2026-11-03 12:25:31 +00:00
bircni d3021b69ee enhance: replace tea CLI with gt (#40036)
tea has been replaced by [gitea-cli](https://gitea.com/gitea/cli)
(`gt`), which reuses tea's OAuth2 client ID.

- The repository clone panel now offers `gt repo clone owner/repo` under
a "Gitea CLI" tab.
- The built-in OAuth2 application is renamed from `tea` to `gitea-cli`.
`tea` in `[oauth2] DEFAULT_APPLICATIONS` is still accepted as an alias,
so existing configs keep working.
- Instances that already registered the app keep its stored display name
"tea".
2026-11-01 12:47:10 +00:00
da7b81d407 feat: add commitstatus access token scope (#40144)
Add `read:commitstatus` and `write:commitstatus` token scopes, so CI and
other integrations can report commit statuses without a token that
grants full repository access.

- The commit status endpoints (`/statuses/{sha}`,
`/commits/{ref}/status` and `/commits/{ref}/statuses`) accept the new
scopes, and the repository scopes keep working as they include them
- Creating a status still requires code write permission on the
repository, the scope only narrows what the token may do
- `public-only` tokens still cannot reach private repositories
- `PathGroup` middlewares now run only for a matched path, so unrelated
methods and paths that fall back to the group are not rejected by its
scope check

Fixes: https://github.com/go-gitea/gitea/issues/32625
Ref: https://github.com/go-gitea/gitea/pull/35383
Docs: https://gitea.com/gitea/docs/pulls/622
Signed-off-by: Norbert Szulc <norbert@not7cd.net>
Co-authored-by: Aiden Scandella <git@sca.ndella.com>
Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
2026-11-01 06:27:12 +00:00
Lunny Xiaoandsilverwind 40507491f7 perf(pull): load the repository once for all commit statuses (#39930)
Pages showing commit statuses loaded the repository of every status
separately, so a PR with ~75 statuses ran ~75 identical repository
queries per merge box render (about 3.4s in a production trace).
`statusRepoCanReadActions` only loaded the repository inside the
permission cache loader, which never runs once `RepoAssignment` has
published the permission.

- `CommitStatus.loadRepository` resolves through the request context
cache
- `statusRepoCanReadActions` loads the repository before the permission
lookup
- `RepoAssignment` publishes its repository to the context cache next to
the permission
- `GetCommitActionsStatusMap` drops its own repository map

Queries per request with 50 statuses (45 Actions, 5 external) on the
head commit, SQLite:

| Page | Repository queries | Total queries |
|---|---|---|
| PR view | 61 → 11 | 157 → 107 |
| Commit | 6 → 5 | 24 → 23 |
| Branches | 6 → 5 | 33 → 32 |
| Commits | 6 → 5 | 23 → 22 |
| Repo home | 8 → 7 | 35 → 34 |
| `/pulls` | 15 → 15 | 37 → 37 |

---------

Co-authored-by: silverwind <me@silverwind.io>
2026-10-31 17:32:03 +01:00
9cd06bf57f fix(migrations): wait out GitHub rate limits and tolerate failed patch downloads (#40012)
Large GitHub migrations failed once the API budget ran out. A rejected
request never updated the downloader's rate state, so go-github refused
every retry locally.

- Record the rate limit from error responses too, so the next request
waits for the reset
- Retry repository-wide comment pages like the other downloader calls
- Stop `waitAndPickClient` spinning when the rate refresh fails
- Skip reaction requests when the reaction rollup reports none
- Log a failed patch download instead of failing the migration

---------

Co-authored-by: bircni <bircni@icloud.com>
Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: Giteabot <teabot@gitea.io>
2026-10-31 17:31:51 +01:00
silverwind fc4d490b35 fix(ssh): let pushes finish when the client disconnects early (#40105)
With the built-in SSH server, closing the client connection cancelled
the `gitea serv` process tree. go-git based clients close it right after
the push report, so post-receive was killed and branches, pull requests,
webhooks and Actions were not updated.

The command now runs under the server's hammer context like with
OpenSSH, where it ends once its pipes close or at shutdown.
2026-10-31 15:24:13 +00:00