Upstream update available: esbuild 0.27.2 → 0.28.1 #3

New issue

Open

opened 2026-06-12 02:23:56 +03:00 by sbelikov · 0 comments

sbelikov commented

2026-06-12 02:23:56 +03:00

Owner

Upstream update available: `esbuild` `0.27.2` → `0.28.1`

Package

Package: esbuild
RPM name: esbuild
Branch: niceos-5.2
Current EVR: 0.27.2-1
Update class: minor
Compare method: python_rpm
Update policy: leaf
Risk tags: github-upstream

Upstream

Upstream type: github
Upstream project: evanw/esbuild
Upstream URL: github.com — esbuild
Detected version: 0.28.1
Tag/release: v0.28.1
Source: github_release_latest
Published: 2026-06-11T22:47:14Z
Release URL: github.com — v0.28.1
Source URL: api.github.com — v0.28.1
Pre-release: False

Signals

Security-relevant keywords detected: True
Policy blocked: False
Policy reason: -
Labels: ai-summary, bot, needs-build, needs-triage, priority/high, security-release, update/minor, upstream-update, upstream/github

NiceSOFT AI preliminary stability analysis

Анализ и рекомендации

1. Тип обновления

Тип: Minor-обновление (0.27.2 → 0.28.1)
Критичность: Низкая (не major-обновление, но содержит изменения в безопасности и функционале)

2. Основные изменения

Безопасность:
- Ограничение на использование \ в HTTP-запросах (устранение уязвимостей).
- Добавление проверок для интеграции с Deno API (улучшение безопасности).
Функционал:
- Устранение ошибок в минификации (например, потенциально неинициализированных переменных).
- Повышение производительности (описано в документации).

3. Риски для НАЙС.ОС

Риск RPM-сборки:
- Почему: Minor-обновление не содержит ABI-изменений, но может включать изменения в интерфейсе (например, улучшения API или интеграции с Deno). Нужно проверить:
  - Нет ли изменений в spec-файлах (например, добавление новых зависимостей или изменение порядка вызовов).
  - Влияние на существующие зависимости (например, Deno или PCL).
- Рекомендация: Проверить spec-файлы и убедиться, что все зависимости работают корректно.

4. Рекомендации

Обновление: Возможное обновление допустимо, так как изменения безопасны и не критичны.
Предупреждение: Рекомендуется ручная проверка RPM-сборки, особенно если в spec-файлах есть изменения в интерфейсе (например, добавление новых зависимостей или изменение порядка вызовов).
Дополнительно: Проверить интеграцию с Deno и убедиться, что все функционал работает корректно.

Вывод

Риск: Низкий, но требует ручной проверки RPM-сборки.
Рекомендация: Обновить пакет, но с предупреждением о возможной ручной проверке spec-файлов и интеграции с Deno.

Рекомендуемое действие: Обновить пакет, проверить spec-файлы и интеграцию с Deno, если есть изменения в интерфейсе.

Источники, найденные web_search

Upstream release notes / description

Disallow \ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \ are no longer allowed.

Thanks to @dellalibera for reporting this issue.
Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

Thanks to @sondt99 for reporting this issue.
Avoid inlining using and await using declarations (#4482)

Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:
```
// Original code
{
  using x = new Resource()
  x.activate()
}

// Old output (with --minify)
new Resource().activate();

// New output (with --minify)
{using e=new Resource;e.activate()}
```
Fix module evaluation when an error is thrown (#4461, #4467)

If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.
Fix some edge cases around the new operator (#4477)

Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:
```
// Original code
new (foo()`bar`)()
new (foo()?.bar)()

// Old output
new foo()`bar`();
new (foo())?.bar();

// New output
new (foo())`bar`();
new (foo()?.bar)();
```
Fix renaming of nested var declarations (#4471)

This release fixes a bug where var declarations in nested scopes that are hoisted up to module scope were not correctly being renamed during bundling. That could previously lead to name collisions when minification was disabled, which could potentially cause a behavior change. The bug has been fixed so that these hoisted declarations are now considered to be module-level symbols during the name collision avoidance pass.
Emit var instead of const for certain TypeScript-only constructs for ES5 (#4448)

While esbuild doesn't generally support converting const to var for ES5 due to nested scoping rules (which is currently a build-time error), esbuild previously incorrectly converted TypeScript-only import assignment constructs into a const declaration even when targeting ES5. With this release, esbuild will now use var for this case instead:
```
// Original code
import x = require('y')

// Old output (with --target=es5)
const x = require("y");

// New output (with --target=es5)
var x = require("y");
```

NiceOS maintainer checklist

Confirm that the detected version is a stable upstream release.
Check upstream changelog for security fixes, ABI/API changes and build-system changes.
Check ABI/API compatibility and reverse dependencies.
Download source into NiceOS lookaside storage.
Update Version and related fields in SPECS/*.spec only if policy allows it.
Regenerate SOURCES/sources.lock.json, manifests, metadata and SBOM.
Build SRPM/RPM in a clean NiceOS buildroot.
Run package smoke tests.
Link PR/build logs and close this issue after update or triage.

Bot metadata

Tool: niceos_upstream_monitor.py 2.1.3-local-websearch-github-release-pages
Generated at: 2026-06-12T23:25:23Z

# Upstream update available: `esbuild` `0.27.2` → `0.28.1` ## Package - Package: `esbuild` - RPM name: `esbuild` - Branch: `niceos-5.2` - Current EVR: `0.27.2-1` - Update class: `minor` - Compare method: `python_rpm` - Update policy: `leaf` - Risk tags: `github-upstream` ## Upstream - Upstream type: `github` - Upstream project: `evanw/esbuild` - Upstream URL: <a href="https://github.com/evanw/esbuild" target="_blank" rel="noopener noreferrer">github.com — esbuild</a> - Detected version: `0.28.1` - Tag/release: `v0.28.1` - Source: `github_release_latest` - Published: `2026-06-11T22:47:14Z` - Release URL: <a href="https://github.com/evanw/esbuild/releases/tag/v0.28.1" target="_blank" rel="noopener noreferrer">github.com — v0.28.1</a> - Source URL: <a href="https://api.github.com/repos/evanw/esbuild/tarball/v0.28.1" target="_blank" rel="noopener noreferrer">api.github.com — v0.28.1</a> - Pre-release: `False` ## Signals - Security-relevant keywords detected: `True` - Policy blocked: `False` - Policy reason: `-` - Labels: `ai-summary, bot, needs-build, needs-triage, priority/high, security-release, update/minor, upstream-update, upstream/github` ## NiceSOFT AI preliminary stability analysis ### Анализ и рекомендации #### 1. **Тип обновления** - **Тип:** Minor-обновление (0.27.2 → 0.28.1) - **Критичность:** Низкая (не major-обновление, но содержит изменения в безопасности и функционале) --- #### 2. **Основные изменения** - **Безопасность:** - Ограничение на использование `\` в HTTP-запросах (устранение уязвимостей). - Добавление проверок для интеграции с Deno API (улучшение безопасности). - **Функционал:** - Устранение ошибок в минификации (например, потенциально неинициализированных переменных). - Повышение производительности (описано в документации). --- #### 3. **Риски для НАЙС.ОС** - **Риск RPM-сборки:** - **Почему:** Minor-обновление не содержит ABI-изменений, но может включать изменения в интерфейсе (например, улучшения API или интеграции с Deno). Нужно проверить: - Нет ли изменений в `spec`-файлах (например, добавление новых зависимостей или изменение порядка вызовов). - Влияние на существующие зависимости (например, `Deno` или `PCL`). - **Рекомендация:** Проверить `spec`-файлы и убедиться, что все зависимости работают корректно. --- #### 4. **Рекомендации** - **Обновление:** Возможное обновление допустимо, так как изменения безопасны и не критичны. - **Предупреждение:** Рекомендуется ручная проверка RPM-сборки, особенно если в `spec`-файлах есть изменения в интерфейсе (например, добавление новых зависимостей или изменение порядка вызовов). - **Дополнительно:** Проверить интеграцию с Deno и убедиться, что все функционал работает корректно. --- ### Вывод - **Риск:** Низкий, но требует ручной проверки RPM-сборки. - **Рекомендация:** Обновить пакет, но с предупреждением о возможной ручной проверке `spec`-файлов и интеграции с Deno. **Рекомендуемое действие:** Обновить пакет, проверить `spec`-файлы и интеграцию с Deno, если есть изменения в интерфейсе. ### Источники, найденные web_search 1. <a href="https://github.com/evanw/esbuild/releases/tag/v0.28.1" target="_blank" rel="noopener noreferrer">GitHub release API: evanw/esbuild v0.28.1</a> 2. <a href="https://github.com/evanw/esbuild/tree/v0.28.1" target="_blank" rel="noopener noreferrer">GitHub tag page: evanw/esbuild v0.28.1</a> 3. <a href="https://github.com/evanw/esbuild/releases" target="_blank" rel="noopener noreferrer">GitHub releases page: evanw/esbuild</a> 4. <a href="https://github.com/evanw/esbuild/compare/v0.27.2...v0.28.1" target="_blank" rel="noopener noreferrer">GitHub compare page: evanw/esbuild v0.27.2...v0.28.1</a> 5. <a href="https://github.com/evanw/esbuild" target="_blank" rel="noopener noreferrer">evanw/esbuild: An extremely fast bundler for the web - GitHub</a> 6. <a href="https://techcommunity.microsoft.com/discussions/microsoft-entra/new-blog--how-to-break-the-token-theft-cyber-attack-chain/4173008" target="_blank" rel="noopener noreferrer">New Blog | How to break the token theft cyber-attack chain | Microsoft ...</a> 7. <a href="https://mirrors.dotsrc.org/opensuse/slowroll/repo/oss/ChangeLog" target="_blank" rel="noopener noreferrer">ChangeLog - dotsrc.org</a> 8. <a href="https://www.microsoft.com/en-us/microsoft-365/powerpoint?msockid=1e416c9c2fd6604e1d7d7bea2eee616e" target="_blank" rel="noopener noreferrer">PowerPoint | Presentations and Slides Online | Microsoft 365</a> 9. <a href="https://www.microsoft.com/ru-ru/microsoft-365/powerpoint?msockid=1e416c9c2fd6604e1d7d7bea2eee616e" target="_blank" rel="noopener noreferrer">PowerPoint | Презентации и слайды в сети | Microsoft 365</a> ## Upstream release notes / description * Disallow ``\`` in local development server HTTP requests (<a href="https://github.com/evanw/esbuild/security/advisories/GHSA-g7r4-m6w7-qqqr" target="_blank" rel="noopener noreferrer">GHSA-g7r4-m6w7-qqqr</a>) This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a ``\`` backslash character. It happened due to the use of Go's `path.Clean()` function, which only handles Unix-style `/` characters. HTTP requests with paths containing ``\`` are no longer allowed. Thanks to <a href="https://github.com/dellalibera" target="_blank" rel="noopener noreferrer">@dellalibera</a> for reporting this issue. * Add integrity checks to the Deno API (<a href="https://github.com/evanw/esbuild/security/advisories/GHSA-gv7w-rqvm-qjhr" target="_blank" rel="noopener noreferrer">GHSA-gv7w-rqvm-qjhr</a>) The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content. Note that esbuild's Deno API installs from `registry.npmjs.org` by default, but allows the `NPM_CONFIG_REGISTRY` environment variable to override this with a custom package registry. This change means that the esbuild executable served by `NPM_CONFIG_REGISTRY` must now match the expected content. Thanks to <a href="https://github.com/sondt99" target="_blank" rel="noopener noreferrer">@sondt99</a> for reporting this issue. * Avoid inlining `using` and `await using` declarations (<a href="https://github.com/evanw/esbuild/issues/4482" target="_blank" rel="noopener noreferrer">#4482</a>) Previously esbuild's minifier sometimes incorrectly inlined `using` and `await using` declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for `let` and `const` declarations by avoiding doing it for `var` declarations, which no longer worked when more declaration types were added. Here's an example: ```js // Original code { using x = new Resource() x.activate() } // Old output (with --minify) new Resource().activate(); // New output (with --minify) {using e=new Resource;e.activate()} ``` * Fix module evaluation when an error is thrown (<a href="https://github.com/evanw/esbuild/issues/4461" target="_blank" rel="noopener noreferrer">#4461</a>, <a href="https://github.com/evanw/esbuild/pull/4467" target="_blank" rel="noopener noreferrer">#4467</a>) If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if `import()` or `require()` is used to import a module multiple times. The thrown error is supposed to be thrown by every call to `import()` or `require()`, not just the first. With this release, esbuild will now throw the same error every time you call `import()` or `require()` on a module that throws during its evaluation. * Fix some edge cases around the `new` operator (<a href="https://github.com/evanw/esbuild/issues/4477" target="_blank" rel="noopener noreferrer">#4477</a>) Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a `new` expression (specifically an optional chain and/or a tagged template literal). The generated code for the `new` target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the `new` target in parentheses. Here is an example of some affected code: ```js // Original code new (foo()`bar`)() new (foo()?.bar)() // Old output new foo()`bar`(); new (foo())?.bar(); // New output new (foo())`bar`(); new (foo()?.bar)(); ``` * Fix renaming of nested `var` declarations (<a href="https://github.com/evanw/esbuild/issues/4471" target="_blank" rel="noopener noreferrer">#4471</a>) This release fixes a bug where `var` declarations in nested scopes that are hoisted up to module scope were not correctly being renamed during bundling. That could previously lead to name collisions when minification was disabled, which could potentially cause a behavior change. The bug has been fixed so that these hoisted declarations are now considered to be module-level symbols during the name collision avoidance pass. * Emit `var` instead of `const` for certain TypeScript-only constructs for ES5 (<a href="https://github.com/evanw/esbuild/issues/4448" target="_blank" rel="noopener noreferrer">#4448</a>) While esbuild doesn't generally support converting `const` to `var` for ES5 due to nested scoping rules (which is currently a build-time error), esbuild previously incorrectly converted TypeScript-only `import` assignment constructs into a `const` declaration even when targeting ES5. With this release, esbuild will now use `var` for this case instead: ```js // Original code import x = require('y') // Old output (with --target=es5) const x = require("y"); // New output (with --target=es5) var x = require("y"); ``` ## NiceOS maintainer checklist - [ ] Confirm that the detected version is a stable upstream release. - [ ] Check upstream changelog for security fixes, ABI/API changes and build-system changes. - [ ] Check ABI/API compatibility and reverse dependencies. - [ ] Download source into NiceOS lookaside storage. - [ ] Update `Version` and related fields in `SPECS/*.spec` only if policy allows it. - [ ] Regenerate `SOURCES/sources.lock.json`, manifests, metadata and SBOM. - [ ] Build SRPM/RPM in a clean NiceOS buildroot. - [ ] Run package smoke tests. - [ ] Link PR/build logs and close this issue after update or triage. ## Bot metadata - Tool: `niceos_upstream_monitor.py 2.1.3-local-websearch-github-release-pages` - Generated at: `2026-06-12T23:25:23Z`

sbelikov added the

labels

2026-06-12 02:23:56 +03:00