-
Notifications
You must be signed in to change notification settings - Fork 225
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.
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
update 4.x from main for v4.5.1 docs build #3967
Conversation
- use more reliable 'elastic' org membership test for triage, etc. labels - bypass 'action-add-labels' action to avoid another dep - drop agent-nodejs label that we no longer require for use in GH projects Fixes: #3884
This adds the require zookeeper volume refs. Closes: #3922
…outside of CI (#3928) Running 'npm test' outside of CI will start all test services in docker *then wait for them to all be healthy*. Without a healthcheck for zk the 'wait_for_healthy' in test/script/run_tests.sh would never pass.
Specifying the mssql image platform is necessary on *arm* Macs because the mssql Docker image only provides binaries for the amd64 architecture. My understanding is that Rosetta emulation on recent macOS supports running the amd binary just fine.
Updates `eslint-plugin-license-header` from 0.6.0 to 0.6.1
…etrics/fixtures (#3952)
…nt flat file config (#3954) In eslint@9 there is a new suggested config file format ("flat") https://github.com/eslint/rfcs/tree/main/designs/2019-config-simplification https://eslint.org/docs/latest/use/configure/configuration-files Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: David Luna <luna.bistuer@gmail.com> Co-authored-by: Trent Mick <trent.mick@elastic.co>
This is a first attempt at this, rather than the force-push update we used to use. Commands used to create this:
|
Sanity test that this branch is the same state as "main":
That diff should have no output.
|
Failing workflows:
Unfortunate added workflow runs to the release process:
|
The process here should be that I wait for the "buildkite/docs-build-pr" check to pass before merging. However, I thought that would have been a "required check" to be allowed to merge. hrm. |
No description provided.