Skip to content

chore(deps): bump @scality/data-browser-library to 1.1.25#1216

Merged
bert-e merged 1 commit into
development/4from
feature/ZKUI-501-implement
May 29, 2026
Merged

chore(deps): bump @scality/data-browser-library to 1.1.25#1216
bert-e merged 1 commit into
development/4from
feature/ZKUI-501-implement

Conversation

@eve-scality

@eve-scality eve-scality commented May 29, 2026

Copy link
Copy Markdown

Summary

Bumps @scality/data-browser-library from 1.1.24 to 1.1.25 in package.json and regenerates package-lock.json to reflect the new resolved version. Pure patch-level dependency update — no source-code changes required.

Tracking

  • JIRA: ZKUI-501
  • Issue: scality/agent-task#231

Step Adherence

  • Step 1: Bump @scality/data-browser-library to 1.1.25 (package.json, package-lock.json)

Mirrors the canonical pattern from prior bump commit 7fad53f7 (ZKUI-477: Bump data-browser-library to 1.1.24) — same two-file change shape.

Test Strategy Executed

  • npm test — exit code 0 (Jest config allows "no tests found" success).
  • npm run check-types — TypeScript compiles cleanly against 1.1.25. One pre-existing TS2307 error unrelated to this change was observed (no regression introduced).

Risks

Any unexpected breaking change in 1.1.25 (despite SemVer patch level) would surface via npm run check-types or Jest failures — none observed.

Part of the implementation plan from scality/agent-task#231.
@eve-scality

Copy link
Copy Markdown
Author

/approve

@bert-e

bert-e commented May 29, 2026

Copy link
Copy Markdown
Contributor

Hello eve-scality,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval
/bypass_build_status Bypass the build and test status
/bypass_commit_size Bypass the check on the size of the changeset TBA
/bypass_incompatible_branch Bypass the check on the source branch prefix
/bypass_jira_check Bypass the Jira issue check
/bypass_peer_approval Bypass the pull request peers' approval
/bypass_leader_approval Bypass the pull request leaders' approval
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request TBA
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@bert-e

bert-e commented May 29, 2026

Copy link
Copy Markdown
Contributor

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following options are set: approve

@claude

claude Bot commented May 29, 2026

Copy link
Copy Markdown

LGTM

Review by Claude Code

@bert-e

bert-e commented May 29, 2026

Copy link
Copy Markdown
Contributor

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/4

The following branches have NOT changed:

  • development/1.4
  • development/1.5
  • development/1.6
  • development/2.0
  • development/2.1
  • development/2.2
  • development/3.0
  • development/3.1
  • development/3.2
  • development/4.0
  • development/4.1
  • development/4.2

Please check the status of the associated issue ZKUI-501.

Goodbye eve-scality.

The following options are set: approve

@bert-e bert-e merged commit 0c857d9 into development/4 May 29, 2026
10 checks passed
@bert-e bert-e deleted the feature/ZKUI-501-implement branch May 29, 2026 13:46
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