Skip to content

chore: release version 2.0.7#14338

Merged
chenjiahan merged 2 commits into
mainfrom
chore/release-2026-06-10
Jun 10, 2026
Merged

chore: release version 2.0.7#14338
chenjiahan merged 2 commits into
mainfrom
chore/release-2026-06-10

Conversation

@intellild

Copy link
Copy Markdown
Contributor

Release Information

  • Released By: intellild
  • Release Date: 2026-06-10
  • JavaScript Packages Version: 2.0.7
  • Rust Crates Version: 0.100.7

by OpenAI Codex

rspack@0.100.7
rspack_allocator@0.100.7
rspack_binding_api@0.100.7
rspack_binding_build@0.100.7
rspack_binding_builder@0.100.7
rspack_binding_builder_macros@0.100.7
rspack_browserslist@0.100.7
rspack_cacheable@0.100.7
rspack_cacheable_macros@0.100.7
rspack_collections@0.100.7
rspack_core@0.100.7
rspack_error@0.100.7
rspack_fs@0.100.7
rspack_hash@0.100.7
rspack_hook@0.100.7
rspack_ids@0.100.7
rspack_javascript_compiler@0.100.7
rspack_loader_lightningcss@0.100.7
rspack_loader_preact_refresh@0.100.7
rspack_loader_react_refresh@0.100.7
rspack_loader_runner@0.100.7
rspack_loader_swc@0.100.7
rspack_loader_testing@0.100.7
rspack_location@0.100.7
rspack_macros@0.100.7
rspack_napi@0.100.7
rspack_napi_macros@0.100.7
rspack_parallel@0.100.7
rspack_paths@0.100.7
rspack_plugin_asset@0.100.7
rspack_plugin_banner@0.100.7
rspack_plugin_case_sensitive@0.100.7
rspack_plugin_circular_dependencies@0.100.7
rspack_plugin_copy@0.100.7
rspack_plugin_css@0.100.7
rspack_plugin_css_chunking@0.100.7
rspack_plugin_devtool@0.100.7
rspack_plugin_dll@0.100.7
rspack_plugin_dynamic_entry@0.100.7
rspack_plugin_ensure_chunk_conditions@0.100.7
rspack_plugin_entry@0.100.7
rspack_plugin_esm_library@0.100.7
rspack_plugin_externals@0.100.7
rspack_plugin_extract_css@0.100.7
rspack_plugin_hmr@0.100.7
rspack_plugin_html@0.100.7
rspack_plugin_ignore@0.100.7
rspack_plugin_javascript@0.100.7
rspack_plugin_json@0.100.7
rspack_plugin_lazy_compilation@0.100.7
rspack_plugin_library@0.100.7
rspack_plugin_lightning_css_minimizer@0.100.7
rspack_plugin_limit_chunk_count@0.100.7
rspack_plugin_merge_duplicate_chunks@0.100.7
rspack_plugin_mf@0.100.7
rspack_plugin_module_info_header@0.100.7
rspack_plugin_module_replacement@0.100.7
rspack_plugin_no_emit_on_errors@0.100.7
rspack_plugin_progress@0.100.7
rspack_plugin_real_content_hash@0.100.7
rspack_plugin_remove_duplicate_modules@0.100.7
rspack_plugin_remove_empty_chunks@0.100.7
rspack_plugin_rsc@0.100.7
rspack_plugin_rsdoctor@0.100.7
rspack_plugin_rslib@0.100.7
rspack_plugin_rstest@0.100.7
rspack_plugin_runtime@0.100.7
rspack_plugin_runtime_chunk@0.100.7
rspack_plugin_schemes@0.100.7
rspack_plugin_size_limits@0.100.7
rspack_plugin_split_chunks@0.100.7
rspack_plugin_sri@0.100.7
rspack_plugin_swc_js_minimizer@0.100.7
rspack_plugin_wasm@0.100.7
rspack_plugin_worker@0.100.7
rspack_regex@0.100.7
rspack_sources@0.100.7
rspack_storage@0.100.7
rspack_swc_plugin_import@0.100.7
rspack_swc_plugin_ts_collector@0.100.7
rspack_tasks@0.100.7
rspack_tracing@0.100.7
rspack_tracing_perfetto@0.100.7
rspack_util@0.100.7
rspack_watcher@0.100.7
rspack_workspace@0.100.7

Generated by cargo-workspaces
@github-actions

github-actions Bot commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

📝 Rspack Ecosystem CI: Open

suite result
rspress ✅ success
rstest ❌ failure
rslib ✅ success
modernjs ✅ success
rsbuild-rsc-plugin ✅ success
rsbuild ✅ success
devserver ✅ success
plugin ✅ success
rsdoctor ❌ failure
examples ✅ success
lynx-stack ❌ failure

@github-actions

Copy link
Copy Markdown
Contributor

📦 Binary Size-limit

Comparing c36ea7f to feat: support rspack magic comment prefix (#14323) by AsyncIter

🙈 Size remains the same at 62.60MB

@github-actions

Copy link
Copy Markdown
Contributor

Rsdoctor Bundle Diff Analysis

⚠️ Note: The latest commit (3796ad37ce) does not have baseline artifacts. Using commit a954cf2d3f for baseline comparison instead. If this seems incorrect, please wait a few minutes and try rerunning the workflow.

Found 5 projects in monorepo, 0 projects with changes.

📊 Quick Summary
Project Total Size Gzip Size Change Gzip Change
popular-libs 1.7 MB 551.3 KB 0 0
react-10k 5.6 MB 1.3 MB 0 0
react-1k 822.8 KB 218.3 KB 0 0
react-5k 2.7 MB 669.1 KB 0 0
ui-components 4.8 MB 1.4 MB 0 0

Generated by Rsdoctor GitHub Action

@codspeed-hq

codspeed-hq Bot commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Merging this PR will not alter performance

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

⚡ 2 improved benchmarks
❌ 1 regressed benchmark
✅ 49 untouched benchmarks
⏩ 40 skipped benchmarks1

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
Simulation sources@cached_source_hash 2.9 µs 3.1 µs -5.61%
Simulation rust@create_full_hash 6.1 ms 6 ms +2.4%
Simulation rust@mangle_exports 7.2 ms 7 ms +2.12%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.


Comparing chore/release-2026-06-10 (c36ea7f) with main (a954cf2)

Open in CodSpeed

Footnotes

  1. 40 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

@chenjiahan chenjiahan merged commit 2e16749 into main Jun 10, 2026
86 of 92 checks passed
@chenjiahan chenjiahan deleted the chore/release-2026-06-10 branch June 10, 2026 13:28
@hardfist

Copy link
Copy Markdown
Contributor

@cursoragent find the root cause of failing ci in eco ci #14338 (comment)

1 similar comment
@hardfist

Copy link
Copy Markdown
Contributor

@cursoragent find the root cause of failing ci in eco ci #14338 (comment)

@hardfist

Copy link
Copy Markdown
Contributor

@codex find the root cause of failing ci in eco ci #14338 (comment)

@chatgpt-codex-connector

Copy link
Copy Markdown

Investigation result

I investigated the linked Ecosystem CI run for PR #14338 (chore: release version 2.0.7). The failing suites in the PR comment were:

  • rstest
  • rsdoctor
  • lynx-stack

The most concrete root cause visible from the public CI annotations is not a Rust/Rspack bundling failure, but a downstream compatibility failure in lynx-stack against @rspack/test-tools.

Root cause

1. lynx-stack is importing @rspack/test-tools APIs that are no longer exported

The lynx-stack job fails during TypeScript compilation with errors like:

  • Module '"@rspack/test-tools"' has no exported member 'TCompilerOptions'.
  • Module '"@rspack/test-tools"' has no exported member 'getSimpleProcessorRunner'.
  • Module '"@rspack/test-tools"' has no exported member 'ECompilerType'.
  • Module '"@rspack/test-tools"' has no exported member 'DiagnosticProcessor'.
  • Module '"@rspack/test-tools"' has no exported member 'NormalProcessor'.

Those exact annotations are visible on the Ecosystem CI run summary for rspack-ecosystem-ci-from-pr #80.

In the current Rspack source, the root @rspack/test-tools barrel exports only these module groups: case, helper, plugin, reporter, runner, test/context, test/creator, test/tester, and type. It does not directly define or restore the missing symbols.

The case barrel exports creator functions and selected config types, but not NormalProcessor, DiagnosticProcessor, ECompilerType, TCompilerOptions, or getSimpleProcessorRunner.

The type barrel exports the newer test-tool interfaces/types such as ITestContext, ITestCompilerManager, ITestProcessor, and related types; the missing legacy symbols are not present there either.

The package exports map also exposes only the root entry plus selected helper/reporter subpaths; it does not expose internal case/* modules as public subpath imports.

So the actionable root cause is:

lynx-stack still depends on old/private @rspack/test-tools APIs that are not part of the current exported surface. Ecosystem CI links the locally built Rspack packages into downstream repos, so lynx-stack sees the new @rspack/test-tools declarations and fails type-checking.

2. The PR itself was a release/version bump, not a code change in test-tools

The PR being investigated is chore: release version 2.0.7. In the local repo history, the corresponding merged commit only changes release/package version metadata; for @rspack/test-tools, it is only a package.json version change, not implementation/export logic. The current repo is already at 2.0.8, confirming this area is release-version metadata.

That means the CI failure is most likely an ecosystem compatibility exposure from the released/local package set, not a logic change introduced by the release commit itself.

Notes on the other failing suites

rstest

The public annotations show timeout failures from workspace/rstest/rstest/e2e/test-api/fixtures/timeout.test.ts, but that fixture is intentionally designed to time out:

  • One test sleeps 100ms but has a 50ms timeout.
  • Another sleeps 5100ms with the default 5000ms timeout.

The upstream Rstest e2e wrapper expects the child CLI to exit with code 1 and expects timeout logs. So these annotations alone are not sufficient to prove a Rspack regression; they may simply be child-process failure output surfaced as GitHub annotations.

rsdoctor

The public GitHub page only exposes Process completed with exit code 1 for the rsdoctor job, without the signed-in raw logs. I could not confirm a deeper root cause from public annotations alone. The rsdoctor ecosystem suite runs the Rsdoctor repo’s test:all command after installing/linking local Rspack packages.

Recommended follow-up

There are two possible fixes depending on intended ownership:

  1. Downstream fix in lynx-stack — migrate its test code away from @rspack/test-tools internal/removed APIs and use the currently exported creator/config interfaces.
  2. Rspack compatibility fix — if these symbols are intended to remain public, re-export compatibility aliases from @rspack/test-tools root and ensure they are included in generated declarations.

Given the current package exports and source barrels, I would treat this as a downstream lynx-stack compatibility issue unless maintainers consider those test-tool internals part of the supported public API.

Commands used

Testing / checks

  • pwd && rg --files -g 'AGENTS.md' -g '!node_modules' -g '!target' | xargs -r -I{} sh -c 'echo --- {}; sed -n "1,220p" {}'
  • git status --short && gh --version && gh run view 27249648948 --repo rstackjs/rstack-ecosystem-ci --json status,conclusion,url,jobsgh was not installed, but this confirmed local status and tool availability.
  • git rev-parse --short HEAD && git log --oneline -5 && git branch --show-current && git diff --stat
  • rg "TCompilerOptions|getSimpleProcessorRunner|ECompilerType|DiagnosticProcessor|NormalProcessor" -n packages tests crates website .agents | head -100
  • sed -n '1,220p' packages/rspack-test-tools/src/index.ts
  • sed -n '1,220p' packages/rspack-test-tools/src/case/index.ts
  • sed -n '1,220p' packages/rspack-test-tools/src/type.ts
  • sed -n '1,80p' packages/rspack-test-tools/package.json
  • git log --oneline --decorate -- packages/rspack-test-tools/src packages/rspack-test-tools/package.json | head -40
  • git show --stat --oneline 2e167490 && git show --name-only --format='' 2e167490 | sed -n '1,200p'
  • nl -ba packages/rspack-test-tools/src/index.ts | sed -n '1,40p'
  • nl -ba packages/rspack-test-tools/src/case/index.ts | sed -n '1,80p'
  • nl -ba packages/rspack-test-tools/src/type.ts | sed -n '1,120p'
  • nl -ba packages/rspack-test-tools/package.json | sed -n '1,45p'

I did not make code changes, so I did not create a commit or PR.

View task →

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants