Skip to content

chore(web): update dependencies version of web-explorer#1839

Merged
PupilTong merged 4 commits intolynx-family:mainfrom
Sherry-hue:chore/web-explorer-update
Oct 10, 2025
Merged

chore(web): update dependencies version of web-explorer#1839
PupilTong merged 4 commits intolynx-family:mainfrom
Sherry-hue:chore/web-explorer-update

Conversation

@Sherry-hue
Copy link
Copy Markdown
Collaborator

@Sherry-hue Sherry-hue commented Sep 28, 2025

Summary by CodeRabbit

  • Chores
    • Updated internal dependencies to the latest patch versions to keep the app current and stable.
    • Prepared a patch release for the web explorer package.
  • Notes
    • No user-facing features or API changes in this release.

Checklist

  • Tests updated (or not required).
  • Documentation updated (or not required).
  • Changeset added, and when a BREAKING CHANGE occurs, it needs to be clearly marked (or not required).

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Sep 28, 2025

🦋 Changeset detected

Latest commit: 911aeb0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@lynx-js/web-explorer Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Sep 28, 2025

📝 Walkthrough

Walkthrough

Adds a changeset file to declare a patch release for @lynx-js/web-explorer and chore updates for @lynx-js/lynx-core (0.1.3) and @lynx-js/web-core (0.17.1). No source code or public API changes.

Changes

Cohort / File(s) Summary
Release metadata
\.changeset/deep-weeks-dream.md
Adds a patch changeset for @lynx-js/web-explorer and records package version bumps for @lynx-js/lynx-core to 0.1.3 and @lynx-js/web-core to 0.17.1; no code changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

  • PupilTong

Poem

A bunny taps the version drum, hop-hop—release in sight!
No code to tweak, just tags to bump, the numbers snug and tight.
I nibble on a changelog leaf, content beneath the sun,
Patchy clouds of versions drift—another hop, well done! 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title follows the conventional commit style and succinctly highlights the main change—a version bump for the web-explorer package—without extraneous details, making it easy for reviewers to understand the primary purpose of this chore.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 316da85 and fc52ad1.

📒 Files selected for processing (1)
  • .changeset/deep-weeks-dream.md (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
.changeset/*.md

📄 CodeRabbit inference engine (AGENTS.md)

For contributions, always generate a changeset and commit the resulting markdown file(s)

Files:

  • .changeset/deep-weeks-dream.md
🧠 Learnings (5)
📓 Common learnings
Learnt from: gaoachao
PR: lynx-family/lynx-stack#1736
File: .changeset/spotty-experts-smoke.md:1-3
Timestamp: 2025-09-12T09:43:04.847Z
Learning: In the lynx-family/lynx-stack repository, empty changeset files (containing only `---\n\n---`) are used for internal changes that modify src/** files but don't require meaningful release notes, such as private package changes or testing-only modifications. This satisfies CI requirements without generating user-facing release notes.
Learnt from: colinaaa
PR: lynx-family/lynx-stack#1330
File: .changeset/olive-animals-attend.md:1-3
Timestamp: 2025-07-22T09:23:07.797Z
Learning: In the lynx-family/lynx-stack repository, changesets are only required for meaningful changes to end-users such as bugfixes and features. Internal/development changes like chores, refactoring, or removing debug info do not need changeset entries.
Learnt from: colinaaa
PR: lynx-family/lynx-stack#1330
File: .changeset/olive-animals-attend.md:1-3
Timestamp: 2025-07-22T09:26:16.722Z
Learning: In the lynx-family/lynx-stack repository, CI checks require changesets when files matching the pattern "src/**" are modified (as configured in .changeset/config.json). For internal changes that don't need meaningful changesets, an empty changeset file is used to satisfy the CI requirement while not generating any release notes.
Learnt from: gaoachao
PR: lynx-family/lynx-stack#1736
File: .changeset/spotty-experts-smoke.md:1-3
Timestamp: 2025-09-12T09:43:04.847Z
Learning: In the lynx-family/lynx-stack repository, private packages (marked with "private": true in package.json) like lynx-js/react-transform don't require meaningful changeset entries even when their public APIs change, since they are not published externally and only affect internal development.
Learnt from: colinaaa
PR: lynx-family/lynx-stack#1454
File: pnpm-workspace.yaml:46-46
Timestamp: 2025-08-07T04:00:59.645Z
Learning: In the lynx-family/lynx-stack repository, the webpack patch (patches/webpack5.101.0.patch) was created to fix issues with webpack5.99.9 but only takes effect on webpack5.100.0 and later versions. The patchedDependencies entry should use "webpack@^5.100.0" to ensure the patch applies to the correct version range.
Learnt from: upupming
PR: lynx-family/lynx-stack#1370
File: .changeset/brave-melons-add.md:1-7
Timestamp: 2025-08-14T12:54:51.143Z
Learning: In the lynx-family/lynx-stack repository, packages use 0.x.x versioning where minor version bumps indicate breaking changes (not major bumps), following pre-1.0 semantic versioning conventions.
📚 Learning: 2025-09-12T09:43:04.847Z
Learnt from: gaoachao
PR: lynx-family/lynx-stack#1736
File: .changeset/spotty-experts-smoke.md:1-3
Timestamp: 2025-09-12T09:43:04.847Z
Learning: In the lynx-family/lynx-stack repository, empty changeset files (containing only `---\n\n---`) are used for internal changes that modify src/** files but don't require meaningful release notes, such as private package changes or testing-only modifications. This satisfies CI requirements without generating user-facing release notes.

Applied to files:

  • .changeset/deep-weeks-dream.md
📚 Learning: 2025-07-22T09:23:07.797Z
Learnt from: colinaaa
PR: lynx-family/lynx-stack#1330
File: .changeset/olive-animals-attend.md:1-3
Timestamp: 2025-07-22T09:23:07.797Z
Learning: In the lynx-family/lynx-stack repository, changesets are only required for meaningful changes to end-users such as bugfixes and features. Internal/development changes like chores, refactoring, or removing debug info do not need changeset entries.

Applied to files:

  • .changeset/deep-weeks-dream.md
📚 Learning: 2025-09-12T09:43:04.847Z
Learnt from: gaoachao
PR: lynx-family/lynx-stack#1736
File: .changeset/spotty-experts-smoke.md:1-3
Timestamp: 2025-09-12T09:43:04.847Z
Learning: In the lynx-family/lynx-stack repository, private packages (marked with "private": true in package.json) like lynx-js/react-transform don't require meaningful changeset entries even when their public APIs change, since they are not published externally and only affect internal development.

Applied to files:

  • .changeset/deep-weeks-dream.md
📚 Learning: 2025-08-07T04:00:59.645Z
Learnt from: colinaaa
PR: lynx-family/lynx-stack#1454
File: pnpm-workspace.yaml:46-46
Timestamp: 2025-08-07T04:00:59.645Z
Learning: In the lynx-family/lynx-stack repository, the webpack patch (patches/webpack5.101.0.patch) was created to fix issues with webpack5.99.9 but only takes effect on webpack5.100.0 and later versions. The patchedDependencies entry should use "webpack@^5.100.0" to ensure the patch applies to the correct version range.

Applied to files:

  • .changeset/deep-weeks-dream.md

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@Sherry-hue Sherry-hue enabled auto-merge (squash) September 28, 2025 07:15
@Sherry-hue Sherry-hue requested a review from PupilTong October 9, 2025 08:38
@Sherry-hue Sherry-hue disabled auto-merge October 10, 2025 07:27
@Sherry-hue Sherry-hue enabled auto-merge (squash) October 10, 2025 07:27
@PupilTong PupilTong disabled auto-merge October 10, 2025 09:27
@PupilTong PupilTong merged commit 7e06ca9 into lynx-family:main Oct 10, 2025
4 checks passed
colinaaa pushed a commit that referenced this pull request Oct 12, 2025
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## @lynx-js/web-core@0.18.0

### Minor Changes

-   fix: ([#1837](#1837))

    1.  `LynxView.updateData()` cannot trigger `dataProcessor`.

2. **This is a break change:** The second parameter of
`LynxView.updateData()` has been changed from `UpdateDataType` to
`string`, which is the `processorName` (default is `default` which will
use `defaultDataProcessor`). This change is to better align with Native.
The current complete type is as follows:

    ```ts
LynxView.updateData(data: Cloneable, processorName?: string | undefined,
callback?: (() => void) | undefined): void
    ```

### Patch Changes

- Updated dependencies
\[[`77397fd`](77397fd),
[`7d90ed5`](7d90ed5)]:
    -   @lynx-js/web-worker-runtime@0.18.0
    -   @lynx-js/web-constants@0.18.0
    -   @lynx-js/web-mainthread-apis@0.18.0
    -   @lynx-js/web-worker-rpc@0.18.0

## @lynx-js/react@0.114.2

### Patch Changes

- fix: main thread functions created during the initial render cannot
correctly call `runOnBackground()` after hydration
([#1878](#1878))

## @lynx-js/rspeedy@0.11.6

### Patch Changes

- Should apply `dev.hmr` and `dev.liveReload` to Rsbuild config.
([#1882](#1882))

- Support CLI flag `--root` to specify the root of the project.
([#1836](#1836))

## @lynx-js/react-rsbuild-plugin@0.11.2

### Patch Changes

- Fix using wrong version of `@lynx-js/react/refresh`.
([#1756](#1756))

-   Updated dependencies \[]:
    -   @lynx-js/react-alias-rsbuild-plugin@0.11.2
    -   @lynx-js/use-sync-external-store@1.5.0
    -   @lynx-js/react-refresh-webpack-plugin@0.3.4
    -   @lynx-js/react-webpack-plugin@0.7.1

## @lynx-js/web-constants@0.18.0

### Patch Changes

-   fix: ([#1837](#1837))

    1.  `LynxView.updateData()` cannot trigger `dataProcessor`.

2. **This is a break change:** The second parameter of
`LynxView.updateData()` has been changed from `UpdateDataType` to
`string`, which is the `processorName` (default is `default` which will
use `defaultDataProcessor`). This change is to better align with Native.
The current complete type is as follows:

    ```ts
LynxView.updateData(data: Cloneable, processorName?: string | undefined,
callback?: (() => void) | undefined): void
    ```

-   Updated dependencies \[]:
    -   @lynx-js/web-worker-rpc@0.18.0

## @lynx-js/web-elements@0.8.8

### Patch Changes

-   fix: ([#1837](#1837))

    1.  `LynxView.updateData()` cannot trigger `dataProcessor`.

2. **This is a break change:** The second parameter of
`LynxView.updateData()` has been changed from `UpdateDataType` to
`string`, which is the `processorName` (default is `default` which will
use `defaultDataProcessor`). This change is to better align with Native.
The current complete type is as follows:

    ```ts
LynxView.updateData(data: Cloneable, processorName?: string | undefined,
callback?: (() => void) | undefined): void
    ```

-   Updated dependencies \[]:
    -   @lynx-js/web-elements-template@0.8.8

## @lynx-js/web-explorer@0.0.10

### Patch Changes

- chore: update `@lynx-js/lynx-core` to `0.1.3`, `@lynx-js/web-core` to
`0.17.1`. ([#1839](#1839))

## @lynx-js/web-mainthread-apis@0.18.0

### Patch Changes

-   fix: ([#1837](#1837))

    1.  `LynxView.updateData()` cannot trigger `dataProcessor`.

2. **This is a break change:** The second parameter of
`LynxView.updateData()` has been changed from `UpdateDataType` to
`string`, which is the `processorName` (default is `default` which will
use `defaultDataProcessor`). This change is to better align with Native.
The current complete type is as follows:

    ```ts
LynxView.updateData(data: Cloneable, processorName?: string | undefined,
callback?: (() => void) | undefined): void
    ```

- feat: mouse event output structures remain aligned
([#1820](#1820))

- Updated dependencies
\[[`77397fd`](77397fd)]:
    -   @lynx-js/web-constants@0.18.0
    -   @lynx-js/web-style-transformer@0.18.0

## @lynx-js/web-worker-runtime@0.18.0

### Patch Changes

-   fix: ([#1837](#1837))

    1.  `LynxView.updateData()` cannot trigger `dataProcessor`.

2. **This is a break change:** The second parameter of
`LynxView.updateData()` has been changed from `UpdateDataType` to
`string`, which is the `processorName` (default is `default` which will
use `defaultDataProcessor`). This change is to better align with Native.
The current complete type is as follows:

    ```ts
LynxView.updateData(data: Cloneable, processorName?: string | undefined,
callback?: (() => void) | undefined): void
    ```

- Updated dependencies
\[[`77397fd`](77397fd),
[`7d90ed5`](7d90ed5)]:
    -   @lynx-js/web-constants@0.18.0
    -   @lynx-js/web-mainthread-apis@0.18.0
    -   @lynx-js/web-worker-rpc@0.18.0

## create-rspeedy@0.11.6



## @lynx-js/react-alias-rsbuild-plugin@0.11.2



## upgrade-rspeedy@0.11.6



## @lynx-js/web-core-server@0.18.0



## @lynx-js/web-elements-template@0.8.8



## @lynx-js/web-rsbuild-server-middleware@0.18.0



## @lynx-js/web-style-transformer@0.18.0



## @lynx-js/web-worker-rpc@0.18.0

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@coderabbitai coderabbitai bot mentioned this pull request Nov 26, 2025
3 tasks
@coderabbitai coderabbitai bot mentioned this pull request Mar 26, 2026
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants