[AUTO] Increment version to 3.6.0.0#731
Open
opensearch-trigger-bot[bot] wants to merge 7 commits into
Open
Conversation
opensearch-trigger-bot
Bot
commented
Apr 4, 2026
opensearch-trigger-bot
Bot
commented
Contributor
- Incremented version to 3.6.0.0.
Bumps [bn.js](https://github.com/indutny/bn.js) from 4.12.0 to 4.12.3. - [Release notes](https://github.com/indutny/bn.js/releases) - [Changelog](https://github.com/indutny/bn.js/blob/master/CHANGELOG.md) - [Commits](indutny/bn.js@v4.12.0...v4.12.3) --- updated-dependencies: - dependency-name: bn.js dependency-version: 4.12.3 dependency-type: indirect ... (cherry picked from commit ef83492) Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
(cherry picked from commit f4a84d9) Signed-off-by: Joshua Li <joshuali925@gmail.com> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Peter Zhu <zhujiaxi@amazon.com>
Signed-off-by: ps48 <pshenoy36@gmail.com>
* Fix Reporting context menu not appearing on Discover page in OSD 3.6 The Reporting in-context menu (#downloadReport) was not injected on the Discover page because the nav menu detection functions used brittle children-count checks that broke when OSD 3.6 changed the nav layout. Replace children-count + breadcrumb detection with URL path matching, which is stable across nav layout changes and already used elsewhere in the same file (isDiscover function). * Bump actions/setup-node to v4 and actions/setup-java to v4 in CI workflows setup-node@v1 and setup-java@v1 cannot install Node 22+ or modern JDKs. OSD main requires Node 22.22.0, causing all Cypress E2E, FTR E2E, and Lint CI checks to fail since the Node 22 bump in Jan 2026. * Remove duplicate local Cypress tests in favor of FTR E2E suite The local .cypress/ tests are duplicates of the tests in the opensearch-dashboards-functional-test repo. Remove the local copies, the cypress-e2e-reporting-test.yml workflow, the Cypress config, and related dependencies to eliminate redundancy. * Fix FTR E2E readiness check race condition The 'Check If OpenSearch Dashboards Is Ready' step uses tail -f on dashboard.log, but the file may not exist yet when the step starts (created by the previous background step via tee). This causes tail to fail immediately, grep sees EOF, and the check exits with code 1 in ~2 seconds instead of waiting. Fix: wait for dashboard.log to exist before tailing, and use tail -f instead of tail -n0 -f so already-written lines are also checked. * revert the cypress changes * update ci workflows * fix linter workflow --------- (cherry picked from commit 9bf940f) Signed-off-by: Tyler Ohlsen <ohltyler@amazon.com> Signed-off-by: ps48 <pshenoy36@gmail.com> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: ps48 <pshenoy36@gmail.com>
opensearch-trigger-bot
Bot
requested review from
Swiddis,
TackAdam,
anirudha,
dai-chen,
joshuali925,
mengweieric,
penghuo,
ps48,
sumukhswamy and
vamsimanohar
as code owners
opensearch-trigger-bot
Bot
force-pushed
the
create-pull-request/3.6.0.0
branch
from
e00c79a to
c7a27bf
Compare
Signed-off-by: opensearch-ci <opensearch-infra@amazon.com>
opensearch-trigger-bot
Bot
force-pushed
the
create-pull-request/3.6.0.0
branch
from
c7a27bf to
2dd0060
Compare
opensearch-trigger-bot
Bot
force-pushed
the
create-pull-request/3.6.0.0
branch
4 times, most recently
from
6a19ce1 to
8dba74f
Compare
Signed-off-by: opensearch-ci-bot <opensearch-infra@amazon.com>
opensearch-trigger-bot
Bot
force-pushed
the
create-pull-request/3.6.0.0
branch
from
8dba74f to
07012c3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.