diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index a9da0969..6efb8e66 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -17,7 +17,7 @@ jobs: runs-on: ubuntu-latest steps: - - uses: actions/checkout@v4 + - uses: actions/checkout@v5 # workaround for npm registry key change # ref. `pnpm@10.1.0` / `pnpm@9.15.4` cannot be installed due to key id mismatch · Issue #612 · nodejs/corepack # - https://github.com/nodejs/corepack/issues/612#issuecomment-2629496091 diff --git a/.github/workflows/docker.yml b/.github/workflows/docker.yml index 47793600..c5689d9c 100644 --- a/.github/workflows/docker.yml +++ b/.github/workflows/docker.yml @@ -16,7 +16,7 @@ jobs: packages: write steps: - name: Checkout - uses: actions/checkout@v4 + uses: actions/checkout@v5 - name: Docker meta id: metal uses: docker/metadata-action@v5 diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index b733190d..46b26f81 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -12,7 +12,7 @@ jobs: release: runs-on: ubuntu-latest steps: - - uses: actions/checkout@v4 + - uses: actions/checkout@v5 with: fetch-depth: 0 diff --git a/.github/workflows/semantic-pull-request.yml b/.github/workflows/semantic-pull-request.yml index f3e6813a..6948034e 100644 --- a/.github/workflows/semantic-pull-request.yml +++ b/.github/workflows/semantic-pull-request.yml @@ -19,6 +19,6 @@ jobs: name: Semantic Pull Request steps: - name: Validate PR title - uses: amannn/action-semantic-pull-request@v5.5.3 + uses: amannn/action-semantic-pull-request@v6.1.1 env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} diff --git a/README.md b/README.md index 3d90a5da..a790712b 100644 --- a/README.md +++ b/README.md @@ -45,7 +45,7 @@ One could put Elk behind popular reverse proxies with SSL Handling like Traefik, 1. got into new source dir: ```cd elk``` 1. create local storage directory for settings: ```mkdir elk-storage``` 1. adjust permissions of storage dir: ```sudo chown 911:911 ./elk-storage``` -1. start container: ```docker-compose up --build -d``` +1. start container: ```docker compose up --build -d``` > [!NOTE] > The provided Dockerfile creates a container which will eventually run Elk as non-root user and create a persistent named Docker volume upon first start (if that volume does not yet exist). This volume is always created with root permission. Failing to change the permissions of ```/elk/data``` inside this volume to UID:GID 911 (as specified for Elk in the Dockerfile) will prevent Elk from storing it's config for user accounts. You either have to fix the permission in the created named volume, or mount a directory with the correct permission to ```/elk/data``` into the container. diff --git a/app/components/common/CommonScrollIntoView.vue b/app/components/common/CommonScrollIntoView.vue index 841f8484..2ac9b5c5 100644 --- a/app/components/common/CommonScrollIntoView.vue +++ b/app/components/common/CommonScrollIntoView.vue @@ -1,6 +1,6 @@