BOTCAHX / RTXZY-MD

WhatsApp Bot Multi Device Latest Version. Jangan lupa tap bintang nya!🌟
https://api.botcahx.eu.org
MIT License
297 stars 376 forks source link

Update docker/login-action action to v2 #17

Closed renovate[bot] closed 2 years ago

renovate[bot] commented 2 years ago

Mend Renovate

This PR contains the following updates:

Package Type Update Change
docker/login-action action major v1.10.0 -> v2.0.0

Release Notes

docker/login-action ### [`v2.0.0`](https://togithub.com/docker/login-action/releases/tag/v2.0.0) [Compare Source](https://togithub.com/docker/login-action/compare/v1.14.1...v2.0.0) - Node 16 as default runtime by [@​crazy-max](https://togithub.com/crazy-max) ([#​161](https://togithub.com/docker/login-action/issues/161)) - This requires a minimum [Actions Runner](https://togithub.com/actions/runner/releases/tag/v2.285.0) version of v2.285.0, which is by default available in GHES 3.4 or later. - chore: update dev dependencies and workflow by [@​crazy-max](https://togithub.com/crazy-max) ([#​170](https://togithub.com/docker/login-action/issues/170)) - Bump [@​actions/exec](https://togithub.com/actions/exec) from 1.1.0 to 1.1.1 ([#​167](https://togithub.com/docker/login-action/issues/167)) - Bump [@​actions/io](https://togithub.com/actions/io) from 1.1.1 to 1.1.2 ([#​168](https://togithub.com/docker/login-action/issues/168)) - Bump minimist from 1.2.5 to 1.2.6 ([#​176](https://togithub.com/docker/login-action/issues/176)) - Bump https-proxy-agent from 5.0.0 to 5.0.1 ([#​182](https://togithub.com/docker/login-action/issues/182)) **Full Changelog**: https://github.com/docker/login-action/compare/v1.14.1...v2.0.0 ### [`v1.14.1`](https://togithub.com/docker/login-action/releases/tag/v1.14.1) [Compare Source](https://togithub.com/docker/login-action/compare/v1.14.0...v1.14.1) - Revert to Node 12 as default runtime to fix issue for GHE users ([#​160](https://togithub.com/docker/login-action/issues/160)) ### [`v1.14.0`](https://togithub.com/docker/login-action/releases/tag/v1.14.0) [Compare Source](https://togithub.com/docker/login-action/compare/v1.13.0...v1.14.0) - Update to node 16 ([#​158](https://togithub.com/docker/login-action/issues/158)) - Bump [@​aws-sdk/client-ecr](https://togithub.com/aws-sdk/client-ecr) from 3.45.0 to 3.53.0 ([#​157](https://togithub.com/docker/login-action/issues/157)) - Bump [@​aws-sdk/client-ecr-public](https://togithub.com/aws-sdk/client-ecr-public) from 3.45.0 to 3.53.0 ([#​156](https://togithub.com/docker/login-action/issues/156)) ### [`v1.13.0`](https://togithub.com/docker/login-action/releases/tag/v1.13.0) [Compare Source](https://togithub.com/docker/login-action/compare/v1.12.0...v1.13.0) - Handle proxy settings for aws-sdk ([#​152](https://togithub.com/docker/login-action/issues/152)) - Workload identity based authentication docs for GCR and GAR ([#​112](https://togithub.com/docker/login-action/issues/112)) - Test login against ACR ([#​49](https://togithub.com/docker/login-action/issues/49)) - Bump [@​aws-sdk/client-ecr](https://togithub.com/aws-sdk/client-ecr) from 3.44.0 to 3.45.0 ([#​132](https://togithub.com/docker/login-action/issues/132)) - Bump [@​aws-sdk/client-ecr-public](https://togithub.com/aws-sdk/client-ecr-public) from 3.43.0 to 3.45.0 ([#​131](https://togithub.com/docker/login-action/issues/131)) ### [`v1.12.0`](https://togithub.com/docker/login-action/releases/tag/v1.12.0) [Compare Source](https://togithub.com/docker/login-action/compare/v1.11.0...v1.12.0) - ECR: only set credentials if username and password are specified ([#​128](https://togithub.com/docker/login-action/issues/128)) - Refactor to use aws-sdk v3 ([#​128](https://togithub.com/docker/login-action/issues/128)) ### [`v1.11.0`](https://togithub.com/docker/login-action/releases/tag/v1.11.0) [Compare Source](https://togithub.com/docker/login-action/compare/v1.10.0...v1.11.0) - ECR: switch implementation to use the AWS SDK ([#​126](https://togithub.com/docker/login-action/issues/126)) - `ecr` input to specify whether the given registry is ECR ([#​123](https://togithub.com/docker/login-action/issues/123)) - Test against Windows runner ([#​126](https://togithub.com/docker/login-action/issues/126)) - Update instructions for Google registry ([#​127](https://togithub.com/docker/login-action/issues/127)) - Update dev workflow ([#​111](https://togithub.com/docker/login-action/issues/111)) - Small changes for GHCR doc ([#​86](https://togithub.com/docker/login-action/issues/86)) - Update dev dependencies ([#​85](https://togithub.com/docker/login-action/issues/85)) - Bump ansi-regex from 5.0.0 to 5.0.1 ([#​101](https://togithub.com/docker/login-action/issues/101)) - Bump tmpl from 1.0.4 to 1.0.5 ([#​100](https://togithub.com/docker/login-action/issues/100)) - Bump [@​actions/core](https://togithub.com/actions/core) from 1.4.0 to 1.6.0 ([#​94](https://togithub.com/docker/login-action/issues/94) [#​103](https://togithub.com/docker/login-action/issues/103)) - Bump codecov/codecov-action from 1 to 2 ([#​88](https://togithub.com/docker/login-action/issues/88)) - Bump hosted-git-info from 2.8.8 to 2.8.9 ([#​83](https://togithub.com/docker/login-action/issues/83)) - Bump node-notifier from 8.0.0 to 8.0.2 ([#​82](https://togithub.com/docker/login-action/issues/82)) - Bump ws from 7.3.1 to 7.5.0 ([#​81](https://togithub.com/docker/login-action/issues/81)) - Bump lodash from 4.17.20 to 4.17.21 ([#​80](https://togithub.com/docker/login-action/issues/80)) - Bump y18n from 4.0.0 to 4.0.3 ([#​79](https://togithub.com/docker/login-action/issues/79))

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.



This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] commented 2 years ago

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 2.x releases. However, if you upgrade to 2.x manually then Renovate will reenable minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.