2 Commits

Author SHA1 Message Date
renovate-bot 6bf5144780 chore(deps): update node.js to v24.18.0
renovate/artifacts Artifact file update failure
CI / full-gate (push) Failing after 11s
Release-Bump: minor
2026-07-18 21:13:04 +00:00
renovate-bot aea568ea1c chore(deps): update renovate/renovate docker tag to v43.252.1
CI / full-gate (push) Successful in 2m26s
Mirror / github-mirror (push) Successful in 3s
Release-Bump: minor
2026-07-06 04:17:39 +00:00
2 changed files with 3 additions and 3 deletions
+2 -2
View File
@@ -19,7 +19,7 @@ jobs:
-e RENOVATE_PLATFORM=gitea \
-e RENOVATE_REPOSITORIES=${{ github.repository }} \
-e RENOVATE_TOKEN \
renovate/renovate:43.251.0
renovate/renovate:43.252.1
# After the renovate job, cut ONE tag covering the renovate-bot commits merged to main since the
# last tag (batch per run). Targets origin/main — the real post-merge tip; the checkout SHA is the
@@ -52,7 +52,7 @@ jobs:
fi
BUMPS=$(git log "${LATEST}..origin/main" --author='renovate@larvit.se' \
--format='%(trailers:key=Release-Bump,valueonly)' | { grep -vx '' || true; })
NEXT=$(docker run --rm -v "$PWD:/repo" -w /repo node:24.16.0-alpine3.24 \
NEXT=$(docker run --rm -v "$PWD:/repo" -w /repo node:24.18.0-alpine3.24 \
node auto-release/next-version.ts "$LATEST" $BUMPS)
echo "Releasing $LATEST -> $NEXT"
git tag "$NEXT" origin/main
+1 -1
View File
@@ -24,7 +24,7 @@
},
"devDependencies": {
"@types/ejs": "3.1.5",
"@types/node": "24.13.2",
"@types/node": "24.13.3",
"typescript": "5.9.3"
}
}