Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update docker/metadata-action action to v5 #165

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 12, 2023

This PR contains the following updates:

Package Type Update Change
docker/metadata-action action major v4 -> v5

Release Notes

docker/metadata-action (docker/metadata-action)

v5

Compare Source


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 is behind base branch, or you tick the rebase/retry checkbox.

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


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/docker-metadata-action-5.x branch 4 times, most recently from 5bb5ccd to 40c7ca4 Compare October 18, 2023 03:31
@renovate renovate bot force-pushed the renovate/docker-metadata-action-5.x branch 6 times, most recently from fdd2e8c to 1f17932 Compare April 17, 2024 09:50
@renovate renovate bot force-pushed the renovate/docker-metadata-action-5.x branch 3 times, most recently from 92aa3ab to 7632948 Compare June 17, 2024 18:48
@renovate renovate bot force-pushed the renovate/docker-metadata-action-5.x branch from 7632948 to c77ef75 Compare September 26, 2024 21:45

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[actionlint] reported by reviewdog 🐶
the runner of "actions-rs/toolchain@v1" action is too old to run on GitHub Actions. update the action's version to fix this issue [action]

uses: actions-rs/toolchain@v1

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[actionlint] reported by reviewdog 🐶
input "working-directory" is not defined in action "Swatinem/rust-cache@v2". available inputs are "cache-all-crates", "cache-directories", "cache-on-failure", "cache-provider", "cache-targets", "env-vars", "key", "prefix-key", "save-if", "shared-key", "workspaces" [action]

working-directory: server

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[actionlint] reported by reviewdog 🐶
the runner of "actions-rs/cargo@v1" action is too old to run on GitHub Actions. update the action's version to fix this issue [action]

uses: actions-rs/cargo@v1

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[actionlint] reported by reviewdog 🐶
the runner of "actions-rs/cargo@v1" action is too old to run on GitHub Actions. update the action's version to fix this issue [action]

uses: actions-rs/cargo@v1

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[actionlint] reported by reviewdog 🐶
the runner of "actions-rs/cargo@v1" action is too old to run on GitHub Actions. update the action's version to fix this issue [action]

uses: actions-rs/cargo@v1

@renovate renovate bot force-pushed the renovate/docker-metadata-action-5.x branch 3 times, most recently from 18ba707 to 61ef6e1 Compare September 27, 2024 06:22
@renovate renovate bot force-pushed the renovate/docker-metadata-action-5.x branch from 61ef6e1 to e5e4658 Compare September 27, 2024 10:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants