docker/login-action
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

chore: Configure Renovate #1

Open
admin wants to merge 1 commits from renovate/configure into master
pull from: renovate/configure
merge into: docker:master
Conversation 0 Commits 1 Files Changed 1
+6
admin commented 2026-07-28 03:12:38 +00:00
Owner
Copy Link
Copy Source

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

Detected Package Files

  • dev.Dockerfile (dockerfile)
  • .github/workflows/ci.yml (github-actions)
  • .github/workflows/codeql.yml (github-actions)
  • .github/workflows/pr-assign-author.yml (github-actions)
  • .github/workflows/publish.yml (github-actions)
  • .github/workflows/test.yml (github-actions)
  • .github/workflows/update-dist.yml (github-actions)
  • .github/workflows/validate.yml (github-actions)
  • .github/workflows/zizmor.yml (github-actions)
  • package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title
  • Provide a link to octochangelog's improved breakdown for Renovate's changelogs

What to Expect

With your current configuration, Renovate will create 3 Pull Requests, up to a maximum of 13 over time (see docs for prConcurrentLimit):

chore(deps): update docker:29.3 docker digest to 686d2c5
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-29.3
  • Merge into: master
  • Upgrade docker to sha256:686d2c5464787b0ca42420e0aa03a94fc9781ff9bf8b5ff947614b9fa4c3c3e0
chore(deps): update eslint monorepo to v9.39.5
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-monorepo
  • Merge into: master
  • Upgrade @eslint/js to 9.39.5
  • Upgrade eslint to 9.39.5
chore(deps): update aws-sdk-js-v3 monorepo to v3.1130.0
chore(deps): update dependency js-yaml to v5.4.1
  • Schedule: ["at any time"]
  • Branch name: renovate/js-yaml-5.x-lockfile
  • Merge into: master
  • Upgrade js-yaml to 5.4.1
chore(deps): update dev-dependencies (non-major)
chore(deps): update docker docker tag to v29.8
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-29.x
  • Merge into: master
  • Upgrade docker to sha256:3f3c01aaaebf7cce837356b688b7c059a4749f10bd7660dec7c58fc454a283f0
chore(deps): update typescript-eslint monorepo to v8.70.0
chore(deps): update vitest monorepo to v4.1.11
  • Schedule: ["at any time"]
  • Branch name: renovate/vitest-monorepo
  • Merge into: master
  • Upgrade @vitest/coverage-v8 to 4.1.11
  • Upgrade vitest to 4.1.11
chore(deps): update yarn to v4.18.0
  • Schedule: ["at any time"]
  • Branch name: renovate/yarn-monorepo
  • Merge into: master
  • Upgrade yarn to sha512-TliFyL0XZP9qfjvfy9usc5ZUj+hpTh8TW2nHSrblgF/1yo+m9IkMeRkboMGNSVKZG36QQC5Ysq/XRrFWuPPlqg==
fix(deps): update dependency @​docker/actions-toolkit to ^0.98.0
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-actions-toolkit-0.x
  • Merge into: master
  • Upgrade @docker/actions-toolkit to sha512-o30bpNQmmHNrU1/BU5keysnHuAoJNt49SBynj4edPrzlgu/C+vSnllftN0I9PFoxdriJWjBkMa87wN+7ZKKqAQ==
chore(deps): update dependency typescript to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-7.x
  • Merge into: master
  • Upgrade typescript to sha512-8FYau96o3NKOhbjKi/qNvG/W5jhzxkbdm5sj9AbZ/5T5sWqn3hJgLfGx27sRKZWTvyzCP8dLRBTf5tBTSRVUNA==
chore(deps): update eslint monorepo to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/major-eslint-monorepo
  • Merge into: master
  • Upgrade @eslint/js to sha512-zeR9k5pd4gxjZ0abRoIaxdc7I3nDktoXZk2qOv9gCNWx3mVwEn32VRhyLaRsDiJjTs0xq/T8mfPtyuXu7GWBcA==
  • Upgrade eslint to sha512-NPXn6r5zl4uET1DAVPaOwzX3rut4c0wcmw3dWJAfOsTM5+TogXo0DDjz8pwm/hL8cyVNpHqeK4JpN0NjnyFFNw==
chore(deps): update vitest monorepo to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/major-vitest-monorepo
  • Merge into: master
  • Upgrade @vitest/coverage-v8 to sha512-toMg6PZGCIa/lQNCDoASrfb1ly4hsUKXFtFYC9kD4t78o5Y6LyNJU7AENt8eHPr3quYdxaxK7hj2mnbFfUk9NA==
  • Upgrade vitest to sha512-gpsMNoRhMjMktVxPtstOH4/PJuPyovVaMDr4oDilXaGH1EcqM2OE96SoHT2VIQ6fTGtTjqmHDrEu2X9RQiXf8Q==

🚸 PR creation will be limited to maximum 4 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

This PR has been generated by Mend Renovate CLI.

Welcome to [Renovate](https://github.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin. 🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged. 📚 See our [Reading List](https://docs.renovatebot.com/reading-list/) for relevant documentation you may be interested in reading. 🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to `renovate.json` in this branch. Renovate will update the Pull Request description the next time it runs. --- ### Detected Package Files * `dev.Dockerfile` (dockerfile) * `.github/workflows/ci.yml` (github-actions) * `.github/workflows/codeql.yml` (github-actions) * `.github/workflows/pr-assign-author.yml` (github-actions) * `.github/workflows/publish.yml` (github-actions) * `.github/workflows/test.yml` (github-actions) * `.github/workflows/update-dist.yml` (github-actions) * `.github/workflows/validate.yml` (github-actions) * `.github/workflows/zizmor.yml` (github-actions) * `package.json` (npm) ### Configuration Summary Based on the default config's presets, Renovate will: - Start dependency updates only once this onboarding PR is merged - Enable Renovate Dependency Dashboard creation. - Use semantic commit type `fix` for dependencies and `chore` for all others if semantic commits are in use. - Ignore `node_modules`, `bower_components`, `vendor` and various test/tests (except for nuget) directories. - Group known monorepo packages together. - Use curated list of recommended non-monorepo package groupings. - Show only the Age and Confidence Merge Confidence badges for pull requests. - Apply crowd-sourced package replacement rules. - Apply crowd-sourced workarounds for known problems with packages. - Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff - Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff - Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff - Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff - Correctly link to the source code for golang.org/x packages - Link to pkg.go.dev/... for golang.org/x packages' title - Provide a link to octochangelog's improved breakdown for Renovate's changelogs --- ### What to Expect With your current configuration, Renovate will create 3 Pull Requests, up to a maximum of 13 over time (see [docs for `prConcurrentLimit`](https://docs.renovatebot.com/configuration-options/#prconcurrentlimit)): <details> <summary>chore(deps): update docker:29.3 docker digest to 686d2c5</summary> - Schedule: ["at any time"] - Branch name: `renovate/docker-29.3` - Merge into: `master` - Upgrade [docker](https://github.com/docker-library/docker) to `sha256:686d2c5464787b0ca42420e0aa03a94fc9781ff9bf8b5ff947614b9fa4c3c3e0` </details> <details> <summary>chore(deps): update eslint monorepo to v9.39.5</summary> - Schedule: ["at any time"] - Branch name: `renovate/eslint-monorepo` - Merge into: `master` - Upgrade [@eslint/js](https://github.com/eslint/eslint) to `9.39.5` - Upgrade [eslint](https://github.com/eslint/eslint) to `9.39.5` </details> <details> <summary>chore(deps): update aws-sdk-js-v3 monorepo to v3.1130.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/aws-sdk-js-v3-monorepo` - Merge into: `master` - Upgrade [@aws-sdk/client-ecr](https://github.com/aws/aws-sdk-js-v3) to `3.1130.0` - Upgrade [@aws-sdk/client-ecr-public](https://github.com/aws/aws-sdk-js-v3) to `3.1130.0` </details> <details> <summary>chore(deps): update dependency js-yaml to v5.4.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/js-yaml-5.x-lockfile` - Merge into: `master` - Upgrade [js-yaml](https://github.com/nodeca/js-yaml) to `5.4.1` </details> <details> <summary>chore(deps): update dev-dependencies (non-major)</summary> - Schedule: ["at any time"] - Branch name: `renovate/dev-dependencies-(non-major)` - Merge into: `master` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `24.13.4` - Upgrade [@vitest/eslint-plugin](https://github.com/vitest-dev/eslint-plugin-vitest) to `1.6.27` - Upgrade [esbuild](https://github.com/evanw/esbuild) to `0.28.2` - Upgrade [eslint-plugin-prettier](https://github.com/prettier/eslint-plugin-prettier) to `5.5.6` - Upgrade [generate-license-file](https://github.com/TobyAndToby/generate-license-file) to `4.2.5` - Upgrade [globals](https://github.com/sindresorhus/globals) to `17.12.0` - Upgrade [prettier](https://github.com/prettier/prettier) to `3.9.6` </details> <details> <summary>chore(deps): update docker docker tag to v29.8</summary> - Schedule: ["at any time"] - Branch name: `renovate/docker-29.x` - Merge into: `master` - Upgrade [docker](https://github.com/docker-library/docker) to `sha256:3f3c01aaaebf7cce837356b688b7c059a4749f10bd7660dec7c58fc454a283f0` </details> <details> <summary>chore(deps): update typescript-eslint monorepo to v8.70.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/typescript-eslint-monorepo` - Merge into: `master` - Upgrade [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint) to `8.70.0` - Upgrade [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint) to `8.70.0` </details> <details> <summary>chore(deps): update vitest monorepo to v4.1.11</summary> - Schedule: ["at any time"] - Branch name: `renovate/vitest-monorepo` - Merge into: `master` - Upgrade [@vitest/coverage-v8](https://github.com/vitest-dev/vitest) to `4.1.11` - Upgrade [vitest](https://github.com/vitest-dev/vitest) to `4.1.11` </details> <details> <summary>chore(deps): update yarn to v4.18.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/yarn-monorepo` - Merge into: `master` - Upgrade [yarn](https://github.com/yarnpkg/berry) to `sha512-TliFyL0XZP9qfjvfy9usc5ZUj+hpTh8TW2nHSrblgF/1yo+m9IkMeRkboMGNSVKZG36QQC5Ysq/XRrFWuPPlqg==` </details> <details> <summary>fix(deps): update dependency @&#8203;docker/actions-toolkit to ^0.98.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/docker-actions-toolkit-0.x` - Merge into: `master` - Upgrade [@docker/actions-toolkit](https://github.com/docker/actions-toolkit) to `sha512-o30bpNQmmHNrU1/BU5keysnHuAoJNt49SBynj4edPrzlgu/C+vSnllftN0I9PFoxdriJWjBkMa87wN+7ZKKqAQ==` </details> <details> <summary>chore(deps): update dependency typescript to v7</summary> - Schedule: ["at any time"] - Branch name: `renovate/typescript-7.x` - Merge into: `master` - Upgrade [typescript](https://github.com/microsoft/TypeScript) to `sha512-8FYau96o3NKOhbjKi/qNvG/W5jhzxkbdm5sj9AbZ/5T5sWqn3hJgLfGx27sRKZWTvyzCP8dLRBTf5tBTSRVUNA==` </details> <details> <summary>chore(deps): update eslint monorepo to v10</summary> - Schedule: ["at any time"] - Branch name: `renovate/major-eslint-monorepo` - Merge into: `master` - Upgrade [@eslint/js](https://github.com/eslint/eslint) to `sha512-zeR9k5pd4gxjZ0abRoIaxdc7I3nDktoXZk2qOv9gCNWx3mVwEn32VRhyLaRsDiJjTs0xq/T8mfPtyuXu7GWBcA==` - Upgrade [eslint](https://github.com/eslint/eslint) to `sha512-NPXn6r5zl4uET1DAVPaOwzX3rut4c0wcmw3dWJAfOsTM5+TogXo0DDjz8pwm/hL8cyVNpHqeK4JpN0NjnyFFNw==` </details> <details> <summary>chore(deps): update vitest monorepo to v5</summary> - Schedule: ["at any time"] - Branch name: `renovate/major-vitest-monorepo` - Merge into: `master` - Upgrade [@vitest/coverage-v8](https://github.com/vitest-dev/vitest) to `sha512-toMg6PZGCIa/lQNCDoASrfb1ly4hsUKXFtFYC9kD4t78o5Y6LyNJU7AENt8eHPr3quYdxaxK7hj2mnbFfUk9NA==` - Upgrade [vitest](https://github.com/vitest-dev/vitest) to `sha512-gpsMNoRhMjMktVxPtstOH4/PJuPyovVaMDr4oDilXaGH1EcqM2OE96SoHT2VIQ6fTGtTjqmHDrEu2X9RQiXf8Q==` </details> 🚸 PR creation will be limited to maximum 4 per hour, so it doesn't swamp any CI resources or overwhelm the project. See [docs for `prHourlyLimit`](https://docs.renovatebot.com/configuration-options/#prhourlylimit) for details. --- ❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-config-hash:e80b4e42a3043bc12fa0640db4bac392d2bf770acf841360d7c8ceeeac2ec1a9-->
admin added 1 commit 2026-07-28 03:12:38 +00:00
Add renovate.json
test / test (pull_request) Failing after 2s
Details
update-dist / update-dist (pull_request) Has been skipped
Details
validate / prepare (pull_request) Failing after 2s
Details
zizmor / zizmor (pull_request) Failing after 0s
Details
pr-assign-author / run (pull_request_target) Failing after 0s
Details
validate / validate (pull_request) Has been skipped
Details
codeql / analyze (pull_request) Failing after 35s
Details
1ce20e4797
Some checks are pending
test / test (pull_request) Failing after 2s
Details
update-dist / update-dist (pull_request) Has been skipped
Details
validate / prepare (pull_request) Failing after 2s
Details
zizmor / zizmor (pull_request) Failing after 0s
Details
pr-assign-author / run (pull_request_target) Failing after 0s
Details
validate / validate (pull_request) Has been skipped
Details
codeql / analyze (pull_request) Failing after 35s
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/configure:renovate/configure
git checkout renovate/configure
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
admin (Simon Axelsson)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: docker/login-action#1
Delete Branch "renovate/configure"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?