[PR #957] [MERGED] build(deps): bump docker/metadata-action from 4.1.0 to 4.1.1 #1064

New issue

Closed

opened 2026-03-03 12:32:53 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 12:32:53 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/fsouza/fake-gcs-server/pull/957
Author: @dependabot[bot]
Created: 10/18/2022
Status: ✅ Merged
Merged: 10/18/2022
Merged by: @fsouza

Base: main ← Head: dependabot/github_actions/docker/metadata-action-4.1.1

📝 Commits (1)

3f66ae1 build(deps): bump docker/metadata-action from 4.1.0 to 4.1.1

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 .github/workflows/docker-push.yml (+1 -1)

📄 Description

Bumps docker/metadata-action from 4.1.0 to 4.1.1.

Release notes

Sourced from docker/metadata-action's releases.

v4.1.1

What's Changed

Revert changes to set associated head sha on pull request event by @crazy-max (#239)

User can still set associated head sha on PR by setting the env var DOCKER_METADATA_PR_HEAD_SHA=true

Bump csv-parse from 5.3.0 to 5.3.1 (#237)

Full Changelog: https://github.com/docker/metadata-action/compare/v4.1.0...v4.1.1

Commits

5739616 Merge pull request #237 from docker/dependabot/npm_and_yarn/csv-parse-5.3.1
473bdc5 update generated content
ebedea2 Bump csv-parse from 5.3.0 to 5.3.1
d00b20e Merge pull request #239 from crazy-max/github-sha
a99e71c revert changes to set associated head sha on pull request event
See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/fsouza/fake-gcs-server/pull/957 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 10/18/2022 **Status:** ✅ Merged **Merged:** 10/18/2022 **Merged by:** [@fsouza](https://github.com/fsouza) **Base:** `main` ← **Head:** `dependabot/github_actions/docker/metadata-action-4.1.1` --- ### 📝 Commits (1) - [`3f66ae1`](https://github.com/fsouza/fake-gcs-server/commit/3f66ae1ec63c0651595e20dc8ed65d49694a2006) build(deps): bump docker/metadata-action from 4.1.0 to 4.1.1 ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/docker-push.yml` (+1 -1) </details> ### 📄 Description Bumps [docker/metadata-action](https://github.com/docker/metadata-action) from 4.1.0 to 4.1.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/docker/metadata-action/releases">docker/metadata-action's releases</a>.</em></p> <blockquote> <h2>v4.1.1</h2> <h2>What's Changed</h2> <ul> <li>Revert changes to set associated head sha on pull request event by <a href="https://github.com/crazy-max"><code>@crazy-max</code></a> (<a href="https://github-redirect.dependabot.com/docker/metadata-action/issues/239">#239</a>) <ul> <li>User can still set associated head sha on PR by setting the env var <code>DOCKER_METADATA_PR_HEAD_SHA=true</code></li> </ul> </li> <li>Bump csv-parse from 5.3.0 to 5.3.1 (<a href="https://github-redirect.dependabot.com/docker/metadata-action/issues/237">#237</a>)</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/docker/metadata-action/compare/v4.1.0...v4.1.1">https://github.com/docker/metadata-action/compare/v4.1.0...v4.1.1</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/docker/metadata-action/commit/57396166ad8aefe6098280995947635806a0e6ea"><code>5739616</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/docker/metadata-action/issues/237">#237</a> from docker/dependabot/npm_and_yarn/csv-parse-5.3.1</li> <li><a href="https://github.com/docker/metadata-action/commit/473bdc561ce7d8aaa1dd9a2636c258980f0a4843"><code>473bdc5</code></a> update generated content</li> <li><a href="https://github.com/docker/metadata-action/commit/ebedea2c18ac929c1071f50f41cf30b13e00b482"><code>ebedea2</code></a> Bump csv-parse from 5.3.0 to 5.3.1</li> <li><a href="https://github.com/docker/metadata-action/commit/d00b20e38f3a2ec65ea14a534b9d110692edc08a"><code>d00b20e</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/docker/metadata-action/issues/239">#239</a> from crazy-max/github-sha</li> <li><a href="https://github.com/docker/metadata-action/commit/a99e71cdc788d640e6bef12d5381f770db27bbbc"><code>a99e71c</code></a> revert changes to set associated head sha on pull request event</li> <li>See full diff in <a href="https://github.com/docker/metadata-action/compare/v4.1.0...v4.1.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=docker/metadata-action&package-manager=github_actions&previous-version=4.1.0&new-version=4.1.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>