Skip to content

chore(deps): apply low-risk Renovate dependency updates#41

Open
eric-forte-elastic wants to merge 1 commit into
mainfrom
june_updates
Open

chore(deps): apply low-risk Renovate dependency updates#41
eric-forte-elastic wants to merge 1 commit into
mainfrom
june_updates

Conversation

@eric-forte-elastic

@eric-forte-elastic eric-forte-elastic commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Related Issues

Resolves #32, #36, #39

Summary

Applies the subset of open Renovate (elastic-renovate-prod) dependency PRs that
carry little/no risk. Each was verified locally with npm run lint, a
parseRuleData TypeScript compile, and a full tsc --noEmit app typecheck.

Libraries updated

Dependency From To Type Notes
axios ^1.14.0 ^1.18.0 devDependency Minor bump within v1, no breaking changes. Only used at build time in parseRuleData.ts.
eslint-config-prettier ^8.10.2 ^10.0.0 devDependency Lint-only; merely disables ESLint rules that conflict with Prettier. Compatible with our ESLint 8.
trim 0.0.3 1.0.1 override/resolution Security-pin safety net only. trim is not actually present in the dependency tree (npm ls trim is empty); 1.0.1 is the ReDoS-fixed release.

Testing

Screenshots

image image

Local Test Steps

Use either the commands from the README if you wish to use your local node installation, or use the following Docker container to test.

Docker Instructions

  1. Clone detection-rules-explorer and cd into the newly cloned directory

  2. Create a Dockerfile with the following contents

    Dockerfile

    FROM node:20.19.3-alpine
    RUN mkdir -p /opt/app
    WORKDIR /opt/app
    COPY package.json package-lock.json /opt/app/
    RUN npm ci
    COPY . .
    RUN npm run build && npm run export
    CMD [ "npm", "start"]

  3. Run docker build -t rules_explorer_test . to build the container

  4. Run docker run rules_explorer_test to start the container

  5. Navigate to 10.10.0.2:3000 to view the explorer (note this is http NOT https)

    • Note this IP address may be different for you depending on your Docker setup or if you are running additional containers.

    • You can use the docker container list command to find your running container

      Example

      ❯ docker container list
      CONTAINER ID   IMAGE                                         COMMAND                  CREATED          STATUS          PORTS                                       NAMES
      c0a434dbfde6   rules_explorer_test                           "docker-entrypoint.s…"   37 seconds ago   Up 37 seconds   443/tcp                                     determined_lehmann
      
      

    • Now you can grab the CONTAINER ID and use it to get the IP address via the following docker inspect <container_id> | grep IPAddress

      Example

      detection-rules-explorer on  remove_ml_packages [!?] via  v20.9.0 on  eric.forte 
      ❯ docker inspect 1ae633496a1b | grep IPAddress
                  "SecondaryIPAddresses": null,
                  "IPAddress": "10.10.0.2",
                          "IPAddress": "10.10.0.2",

  6. Check to make sure the website renders as intended.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant