Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update @elastic/appex-qa dependencies (main) #200791

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update @elastic/appex-qa dependencies (main) #200791

wants to merge 1 commit into from
+306 −182

Conversation

elastic-renovate-prod[bot]
Copy link
Contributor

@elastic-renovate-prod elastic-renovate-prod bot commented Nov 19, 2024 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
@playwright/test (source) devDependencies minor 1.49.0 -> 1.50.1
@types/chance (source) devDependencies minor ^1.0.0 -> ^1.1.6
@types/pixelmatch (source) devDependencies patch ^5.2.4 -> ^5.2.6
@types/react-test-renderer (source) devDependencies major ~18.0.0 -> ~19.0.0
callsites devDependencies major ^3.1.0 -> ^4.2.0
chance (source) devDependencies minor 1.0.18 -> 1.1.12
cheerio (source) dependencies patch ^1.0.0-rc.12 -> ^1.0.0
pixelmatch devDependencies major ^5.3.0 -> ^7.1.0
playwright (source) devDependencies minor 1.49.0 -> 1.50.1
playwright-chromium (source) devDependencies minor 1.49.0 -> 1.50.1
react-test-renderer (source) devDependencies major ~18.2.0 -> ~19.0.0
sharp (source, changelog) resolutions minor 0.32.6 -> 0.33.5
sharp (source, changelog) devDependencies minor 0.32.6 -> 0.33.5

Release Notes

microsoft/playwright (@​playwright/test)

v1.50.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/34483 - [Feature]: single aria snapshot for different engines/browsershttps://github.com/microsoft/playwright/issues/344977 - [Bug]: Firefox not handling keepalive: true fetch requesthttps://github.com/microsoft/playwright/issues/3450404 - [Bug]: update snapshots not creating good difhttps://github.com/microsoft/playwright/issues/34507507 - [Bug]: snapshotPathTemplate doesnt work when multiple projehttps://github.com/microsoft/playwright/issues/344624462 - [Bug]: updateSnapshots "changed" throws an error

Browser Versions
  • Chromium 133.0.6943.16
  • Mozilla Firefox 134.0
  • WebKit 18.2

This version was also tested against the following stable channels:

  • Google Chrome 132
  • Microsoft Edge 132

v1.50.0

Compare Source

Test runner

  • New option timeout allows specifying a maximum run time for an individual test step. A timed-out step will fail the execution of the test.

    test('some test', async ({ page }) => {
  await test.step('a step', async () => {
    // This step can time out separately from the test
  }, { timeout: 1000 });
});

  • New method test.step.skip() to disable execution of a test step.

    test('some test', async ({ page }) => {
  await test.step('before running step', async () => {
    // Normal step
  });

  await test.step.skip('not yet ready', async () => {
    // This step is skipped
  });

  await test.step('after running step', async () => {
    // This step still runs even though the previous one was skipped
  });
});

  • Expanded expect(locator).toMatchAriaSnapshot() to allow storing of aria snapshots in separate YAML files.

  • Added method expect(locator).toHaveAccessibleErrorMessage() to assert the Locator points to an element with a given aria errormessage.

  • Option testConfig.updateSnapshots added the configuration enum changed. changed updates only the snapshots that have changed, whereas all now updates all snapshots, regardless of whether there are any differences.

  • New option testConfig.updateSourceMethod defines the way source code is updated when testConfig.updateSnapshots is configured. Added overwrite and 3-way modes that write the changes into source code, on top of existing patch mode that creates a patch file.

    npx playwright test --update-snapshots=changed --update-source-method=3way

  • Option testConfig.webServer added a gracefulShutdown field for specifying a process kill signal other than the default SIGKILL.

  • Exposed testStep.attachments from the reporter API to allow retrieval of all attachments created by that step.

  • New option pathTemplate for toHaveScreenshot and toMatchAriaSnapshot assertions in the testConfig.expect configuration.

UI updates
  • Updated default HTML reporter to improve display of attachments.
  • New button for picking elements to produce aria snapshots.
  • Additional details (such as keys pressed) are now displayed alongside action API calls in traces.
  • Display of canvas content in traces is error-prone. Display is now disabled by default, and can be enabled via the Display canvas content UI setting.
  • Call and Network panels now display additional time information.
Breaking
Browser Versions
  • Chromium 133.0.6943.16
  • Mozilla Firefox 134.0
  • WebKit 18.2

This version was also tested against the following stable channels:

  • Google Chrome 132
  • Microsoft Edge 132

v1.49.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/33802 - [Bug]: Codegen's Clear button doesn't work if not recordinghttps://github.com/microsoft/playwright/issues/338066 - [Bug]: playwright hangs while waiting for pending navigationhttps://github.com/microsoft/playwright/issues/3378787 - [Bug]: VSC extension isn't capturing all entered tehttps://github.com/microsoft/playwright/issues/33788788 - [Regression]: Double clicking the steps in trace viewer doesn't filter actihttps://github.com/microsoft/playwright/issues/337723772 - [Bug]: aria_snapshot generates invalid yaml when combined with an aria-label attrhttps://github.com/microsoft/playwright/issues/3379133791 - [Bug]: text input with number value raises "container is not iterable" with to_match_aria_snahttps://github.com/microsoft/playwright/issues/33644/33644 - [Bug]: getByRole can't find element with the accessible name from label element when aria-labelledby is nothttps://github.com/microsoft/playwright/issues/33660s/33660 - [Regression]: Unable to open Playwright UI in Dark Mode

Browser Versions
  • Chromium 131.0.6778.33
  • Mozilla Firefox 132.0
  • WebKit 18.2

This version was also tested against the following stable channels:

  • Google Chrome 130
  • Microsoft Edge 130
sindresorhus/callsites (callsites)

v4.2.0

Compare Source

  • Add methods for async stack traces to the types (#​22) f294a7e

v4.1.0

Compare Source

v4.0.0

Compare Source

Breaking
chancejs/chancejs (chance)

v1.1.12

Compare Source

v1.1.11

Compare Source

v1.1.10

Compare Source

v1.1.9

Compare Source

v1.1.8

Compare Source

v1.1.7

Compare Source

v1.1.6

Compare Source

v1.1.5

Compare Source

v1.1.4

Compare Source

v1.1.3

Compare Source

v1.1.2

Compare Source

v1.1.0

Compare Source

cheeriojs/cheerio (cheerio)

v1.0.0

Compare Source

Cheerio 1.0 is here! 🎉

Announcement Blog Post

Breaking Changes

New Features

Fixes

Other

Full Changelog: cheeriojs/cheerio@v1.0.0-rc.12...v1.0.0

mapbox/pixelmatch (pixelmatch)

v7.1.0

Compare Source

  • Add first-class TypeScript types to the project. They'll be maintained in the repo from now on. #​139
  • Improve matching performance by ~22%. #​150

v7.0.0

Compare Source

  • Potentially breaking: improve handling of semitransparent pixels. Previously, they were blended with white, so a transparent pixel vs white pixel would show zero difference; now pixels are blended with an irregular pattern, making it easier to catch regressions. (h/t @​NathanMOlson #​142)
  • Improve match performance by ~6%. #​147
  • Significantly improve diff generation performance. (h/t @​kawanet #​105)
  • Fix options handling to use the default value when undefined is passed explicitly. (h/t @​denis-sokolov #​146)
  • Fix ESLint failing on Windows when working on the library locally. (h/t @​haraldreingruber-dedalus #​123)

v6.0.0

Compare Source

⚠️ Breaking: publish pixelmatch as a ES module. Use the older v5.3.0 if you need to support CommonJS environments.

facebook/react (react-test-renderer)

v19.0.0

Compare Source

Below is a list of all new features, APIs, deprecations, and breaking changes. Read React 19 release post and React 19 upgrade guide for more information.

Note: To help make the upgrade to React 19 easier, we’ve published a [email protected] release that is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19. We recommend upgrading to React 18.3.1 first to help identify any issues before upgrading to React 19.

New Features
React
  • Actions: startTransition can now accept async functions. Functions passed to startTransition are called “Actions”. A given Transition can include one or more Actions which update state in the background and update the UI with one commit. In addition to updating state, Actions can now perform side effects including async requests, and the Action will wait for the work to finish before finishing the Transition. This feature allows Transitions to include side effects like fetch() in the pending state, and provides support for error handling, and optimistic updates.
  • useActionState: is a new hook to order Actions inside of a Transition with access to the state of the action, and the pending state. It accepts a reducer that can call Actions, and the initial state used for first render. It also accepts an optional string that is used if the action is passed to a form action prop to support progressive enhancement in forms.
  • useOptimistic: is a new hook to update state while a Transition is in progress. It returns the state, and a set function that can be called inside a transition to “optimistically” update the state to expected final value immediately while the Transition completes in the background. When the transition finishes, the state is updated to the new value.
  • use: is a new API that allows reading resources in render. In React 19, use accepts a promise or Context. If provided a promise, use will suspend until a value is resolved. use can only be used in render but can be called conditionally.
  • ref as a prop: Refs can now be used as props, removing the need for forwardRef.
  • Suspense sibling pre-warming: When a component suspends, React will immediately commit the fallback of the nearest Suspense boundary, without waiting for the entire sibling tree to render. After the fallback commits, React will schedule another render for the suspended siblings to “pre-warm” lazy requests.
React DOM Client
  • <form> action prop: Form Actions allow you to manage forms automatically and integrate with useFormStatus. When a <form> action succeeds, React will automatically reset the form for uncontrolled components. The form can be reset manually with the new requestFormReset API.
  • <button> and <input> formAction prop: Actions can be passed to the formAction prop to configure form submission behavior. This allows using different Actions depending on the input.
  • useFormStatus: is a new hook that provides the status of the parent <form> action, as if the form was a Context provider. The hook returns the values: pending, data, method, and action.
  • Support for Document Metadata: We’ve added support for rendering document metadata tags in components natively. React will automatically hoist them into the <head> section of the document.
  • Support for Stylesheets: React 19 will ensure stylesheets are inserted into the <head> on the client before revealing the content of a Suspense boundary that depends on that stylesheet.
  • Support for async scripts: Async scripts can be rendered anywhere in the component tree and React will handle ordering and deduplication.
  • Support for preloading resources: React 19 ships with preinit, preload, prefetchDNS, and preconnect APIs to optimize initial page loads by moving discovery of additional resources like fonts out of stylesheet loading. They can also be used to prefetch resources used by an anticipated navigation.
React DOM Server
  • Added prerender and prerenderToNodeStream APIs for static site generation. They are designed to work with streaming environments like Node.js Streams and Web Streams. Unlike renderToString, they wait for data to load for HTML generation.
React Server Components
  • RSC features such as directives, server components, and server functions are now stable. This means libraries that ship with Server Components can now target React 19 as a peer dependency with a react-server export condition for use in frameworks that support the Full-stack React Architecture. The underlying APIs used to implement a React Server Components bundler or framework do not follow semver and may break between minors in React 19.x. See docs for how to support React Server Components.
Deprecations
  • Deprecated: element.ref access: React 19 supports ref as a prop, so we’re deprecating element.ref in favor of element.props.ref. Accessing will result in a warning.
  • react-test-renderer: In React 19, react-test-renderer logs a deprecation warning and has switched to concurrent rendering for web usage. We recommend migrating your tests to @​testing-library/react or @​testing-library/react-native
Breaking Changes

React 19 brings in a number of breaking changes, including the removals of long-deprecated APIs. We recommend first upgrading to 18.3.1, where we've added additional deprecation warnings. Check out the upgrade guide for more details and guidance on codemodding.

React
  • New JSX Transform is now required: We introduced a new JSX transform in 2020 to improve bundle size and use JSX without importing React. In React 19, we’re adding additional improvements like using ref as a prop and JSX speed improvements that require the new transform.
  • Errors in render are not re-thrown: Errors that are not caught by an Error Boundary are now reported to window.reportError. Errors that are caught by an Error Boundary are reported to console.error. We’ve introduced onUncaughtError and onCaughtError methods to createRoot and hydrateRoot to customize this error handling.
  • Removed: propTypes: Using propTypes will now be silently ignored. If required, we recommend migrating to TypeScript or another type-checking solution.
  • Removed: defaultProps for functions: ES6 default parameters can be used in place. Class components continue to support defaultProps since there is no ES6 alternative.
  • Removed: contextTypes and getChildContext: Legacy Context for class components has been removed in favor of the contextType API.
  • Removed: string refs: Any usage of string refs need to be migrated to ref callbacks.
  • Removed: Module pattern factories: A rarely used pattern that can be migrated to regular functions.
  • Removed: React.createFactory: Now that JSX is broadly supported, all createFactory usage can be migrated to JSX components.
  • Removed: react-test-renderer/shallow: This has been a re-export of react-shallow-renderer since React 18. If needed, you can continue to use the third-party package directly. We recommend using @​testing-library/react or @​testing-library/react-native instead.
React DOM
  • Removed: react-dom/test-utils: We’ve moved act from react-dom/test-utils to react. All other utilities have been removed.
  • Removed: ReactDOM.render, ReactDOM.hydrate: These have been removed in favor of the concurrent equivalents: ReactDOM.createRoot and ReactDOM.hydrateRoot.
  • Removed: unmountComponentAtNode: Removed in favor of root.unmount().
  • Removed: ReactDOM.findDOMNode: You can replace ReactDOM.findDOMNode with DOM Refs.
Notable Changes
React
  • <Context> as a provider: You can now render <Context> as a provider instead of <Context.Provider>.
  • Cleanup functions for refs: When the component unmounts, React will call the cleanup function returned from the ref callback.
  • useDeferredValue initial value argument: When provided, useDeferredValue will return the initial value for the initial render of a component, then schedule a re-render in the background with the deferredValue returned.
  • Support for Custom Elements: React 19 now passes all tests on Custom Elements Everywhere.
  • StrictMode changes: useMemo and useCallback will now reuse the memoized results from the first render, during the second render. Additionally, StrictMode will now double-invoke ref callback functions on initial mount.
  • UMD builds removed: To load React 19 with a script tag, we recommend using an ESM-based CDN such as esm.sh.
React DOM
  • Diffs for hydration errors: In the case of a mismatch, React 19 logs a single error with a diff of the mismatched content.
  • Compatibility with third-party scripts and extensions: React will now force a client re-render to fix up any mismatched content caused by elements inserted by third-party JS.
TypeScript Changes

The most common changes can be codemodded with npx types-react-codemod@latest preset-19 ./path-to-your-react-ts-files.

  • Removed deprecated TypeScript types:
    • ReactChild (replacement: React.ReactElement | number | string)
    • ReactFragment (replacement: Iterable<React.ReactNode>)
    • ReactNodeArray (replacement: ReadonlyArray<React.ReactNode>)
    • ReactText (replacement: number | string)
    • VoidFunctionComponent (replacement: FunctionComponent)
    • VFC (replacement: FC)
    • Moved to prop-types: Requireable, ValidationMap, Validator, WeakValidationMap
    • Moved to create-react-class: ClassicComponentClass, ClassicComponent, ClassicElement, ComponentSpec, Mixin, ReactChildren, ReactHTML, ReactSVG, SFCFactory
  • Disallow implicit return in refs: refs can now accept cleanup functions. When you return something else, we can’t tell if you intentionally returned something not meant to clean up or returned the wrong value. Implicit returns of anything but functions will now error.
  • Require initial argument to useRef: The initial argument is now required to match useState, createContext etc
  • Refs are mutable by default: Ref objects returned from useRef() are now always mutable instead of sometimes being immutable. This feature was too confusing for users and conflicted with legit cases where refs were managed by React and manually written to.
  • Strict ReactElement typing: The props of React elements now default to unknown instead of any if the element is typed as ReactElement
  • JSX namespace in TypeScript: The global JSX namespace is removed to improve interoperability with other libraries using JSX. Instead, the JSX namespace is available from the React package: import { JSX } from 'react'
  • Better useReducer typings: Most useReducer usage should not require explicit type arguments.
    For example, 
    -useReducer<React.Reducer<State, Action>>(reducer)
+useReducer(reducer)
    or 
    -useReducer<React.Reducer<State, Action>>(reducer)
+useReducer<State, Action>(reducer)
All Changes
React
React DOM

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@elastic-renovate-prod elastic-renovate-prod bot added backport:all-open Backport to all branches that could still receive a release release_note:skip Skip the PR/issue when compiling release notes Team:QA Team label for QA Team labels Nov 19, 2024
@elastic-renovate-prod elastic-renovate-prod bot requested a review from a team November 19, 2024 18:24
@elasticmachine
Copy link
Contributor

Pinging @elastic/appex-qa (Team:QA)

@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-@elasticappex-qa-dependencies branch from 4afa0f0 to ded27f0 Compare November 19, 2024 20:53
@dmlemeshko dmlemeshko self-assigned this Nov 20, 2024
@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-@elasticappex-qa-dependencies branch 2 times, most recently from c1fb9ec to 45a565f Compare November 20, 2024 15:48
@dmlemeshko
Copy link
Member

/ci

@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-@elasticappex-qa-dependencies branch from 45a565f to fbdbd66 Compare November 21, 2024 08:03
@elasticmachine
Copy link
Contributor

elasticmachine commented Nov 21, 2024 •
edited
Loading

⏳ Build in-progress, with failures

Failed CI Steps

History

cc @dmlemeshko

@dmlemeshko dmlemeshko mentioned this pull request Nov 21, 2024
Closed
@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-@elasticappex-qa-dependencies branch 4 times, most recently from e658183 to 516def1 Compare November 29, 2024 13:07
@dmlemeshko dmlemeshko mentioned this pull request Dec 2, 2024
Merged
dmlemeshko added a commit that referenced this pull request Dec 2, 2024
@dmlemeshko @kibanamachine
[chore] update appex-qa owned dependencies (#202360)
1a864ac 
## Summary

This PR updates some dev dependencies owned by appex-qa.
[PR](#200791) by renovate is
trying to update to many things at once 🚋

---------

Co-authored-by: kibanamachine <[email protected]>
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Dec 2, 2024
@dmlemeshko
[chore] update appex-qa owned dependencies (elastic#202360)
e62c070 
## Summary

This PR updates some dev dependencies owned by appex-qa.
[PR](elastic#200791) by renovate is
trying to update to many things at once 🚋

---------

Co-authored-by: kibanamachine <[email protected]>
(cherry picked from commit 1a864ac)
@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-@elasticappex-qa-dependencies branch from 516def1 to c2046e9 Compare December 2, 2024 13:50
kibanamachine added a commit that referenced this pull request Dec 2, 2024
@kibanamachine @dmlemeshko
[8.17] [chore] update appex-qa owned dependencies (#202360) (#202470)
d47dded 
# Backport

This will backport the following commits from `main` to `8.17`:
- [[chore] update appex-qa owned dependencies
(#202360)](#202360)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-02T13:38:03Z","message":"[chore]
update appex-qa owned dependencies (#202360)\n\n## Summary\r\n\r\nThis
PR updates some dev dependencies owned by
appex-qa.\r\n[PR](#200791) by
renovate is\r\ntrying to update to many things at once
🚋\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<[email protected]>","sha":"1a864ace2fb3049bc3ec229ef1cbdbac44b6d211","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","v8.17.0"],"title":"[chore]
update appex-qa owned
dependencies","number":202360,"url":"https://github.com/elastic/kibana/pull/202360","mergeCommit":{"message":"[chore]
update appex-qa owned dependencies (#202360)\n\n## Summary\r\n\r\nThis
PR updates some dev dependencies owned by
appex-qa.\r\n[PR](#200791) by
renovate is\r\ntrying to update to many things at once
🚋\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<[email protected]>","sha":"1a864ace2fb3049bc3ec229ef1cbdbac44b6d211"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202360","number":202360,"mergeCommit":{"message":"[chore]
update appex-qa owned dependencies (#202360)\n\n## Summary\r\n\r\nThis
PR updates some dev dependencies owned by
appex-qa.\r\n[PR](#200791) by
renovate is\r\ntrying to update to many things at once
🚋\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<[email protected]>","sha":"1a864ace2fb3049bc3ec229ef1cbdbac44b6d211"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Dzmitry Lemechko <[email protected]>
@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-@elasticappex-qa-dependencies branch 2 times, most recently from e5eb9fe to f38eb4c Compare December 3, 2024 14:55
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this pull request Dec 9, 2024
@dmlemeshko @kibanamachine @CAWilson94
[chore] update appex-qa owned dependencies (elastic#202360)
450483d 
## Summary

This PR updates some dev dependencies owned by appex-qa.
[PR](elastic#200791) by renovate is
trying to update to many things at once 🚋

---------

Co-authored-by: kibanamachine <[email protected]>
@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-@elasticappex-qa-dependencies branch from f38eb4c to 150785b Compare December 10, 2024 09:50
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this pull request Dec 12, 2024
@dmlemeshko @kibanamachine @CAWilson94
[chore] update appex-qa owned dependencies (elastic#202360)
6d7c3fc 
## Summary

This PR updates some dev dependencies owned by appex-qa.
[PR](elastic#200791) by renovate is
trying to update to many things at once 🚋

---------

Co-authored-by: kibanamachine <[email protected]>
@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-@elasticappex-qa-dependencies branch 2 times, most recently from b855e36 to cce60db Compare December 17, 2024 04:51
@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-@elasticappex-qa-dependencies branch from cce60db to 53d5ee2 Compare January 10, 2025 02:35
@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-@elasticappex-qa-dependencies branch 2 times, most recently from 8920081 to 23113f8 Compare January 15, 2025 09:46
@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-@elasticappex-qa-dependencies branch 5 times, most recently from 3212d41 to c669da2 Compare January 28, 2025 19:34
@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-@elasticappex-qa-dependencies branch from c669da2 to e71883d Compare January 31, 2025 20:37
@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-@elasticappex-qa-dependencies branch from e71883d to 28f5f4b Compare February 11, 2025 07:54
@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-@elasticappex-qa-dependencies branch 4 times, most recently from 979ebac to c4717cd Compare February 25, 2025 15:00
@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-@elasticappex-qa-dependencies branch from c4717cd to 330025f Compare March 3, 2025 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@dmlemeshko dmlemeshko

Labels
backport:all-open Backport to all branches that could still receive a release release_note:skip Skip the PR/issue when compiling release notes Team:QA Team label for QA Team
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@elasticmachine @dmlemeshko