Skip to content

chore(deps): update nginx docker tag to v18.3.6 #1617

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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 2, 2024

This PR contains the following updates:

Package Update Change
nginx (source) minor 18.2.5 -> 18.3.6

Release Notes

bitnami/charts (nginx)

v18.3.6

v18.3.5

v18.3.4

v18.3.3

v18.3.2

v18.3.1

v18.3.0

v18.2.6


Configuration

📅 Schedule: Branch creation - "before 5am on Monday" (UTC), 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/nginx-18.x branch 4 times, most recently from b2c87df to 7bcce49 Compare December 5, 2024 11:20
@renovate renovate bot changed the title chore(deps): update nginx docker tag to v18.2.6 chore(deps): update nginx docker tag to v18.3.0 Dec 11, 2024
@renovate renovate bot force-pushed the renovate/nginx-18.x branch 4 times, most recently from 52d6962 to 92a1fbf Compare December 13, 2024 10:27
@renovate renovate bot changed the title chore(deps): update nginx docker tag to v18.3.0 chore(deps): update nginx docker tag to v18.3.1 Dec 13, 2024
@renovate renovate bot force-pushed the renovate/nginx-18.x branch 2 times, most recently from 78be0e8 to b2434e6 Compare December 16, 2024 08:46
@renovate renovate bot force-pushed the renovate/nginx-18.x branch 3 times, most recently from c5039d2 to 18d6835 Compare December 28, 2024 11:29
@renovate renovate bot changed the title chore(deps): update nginx docker tag to v18.3.1 chore(deps): update nginx docker tag to v18.3.2 Jan 1, 2025
@renovate renovate bot force-pushed the renovate/nginx-18.x branch 4 times, most recently from 1745cdf to 1f2741c Compare January 3, 2025 10:49
@renovate renovate bot force-pushed the renovate/nginx-18.x branch from 1f2741c to ec837c9 Compare January 8, 2025 23:03
@renovate renovate bot changed the title chore(deps): update nginx docker tag to v18.3.2 chore(deps): update nginx docker tag to v18.3.3 Jan 8, 2025
@renovate renovate bot force-pushed the renovate/nginx-18.x branch from ec837c9 to a19ff10 Compare January 9, 2025 03:23
@renovate renovate bot changed the title chore(deps): update nginx docker tag to v18.3.3 chore(deps): update nginx docker tag to v18.3.4 Jan 9, 2025
@renovate renovate bot force-pushed the renovate/nginx-18.x branch from a19ff10 to 5b36c60 Compare January 11, 2025 01:42
@renovate renovate bot changed the title chore(deps): update nginx docker tag to v18.3.4 chore(deps): update nginx docker tag to v18.3.5 Jan 11, 2025
@Mokto
Copy link
Contributor

Mokto commented Jan 11, 2025

👋 Hi, @renovate,
I detected conflicts against the base branch 🙊
You'll want to sync 🔄 your branch with upstream!

@renovate renovate bot force-pushed the renovate/nginx-18.x branch from 5b36c60 to de9d1e7 Compare January 11, 2025 19:40
@Mokto Mokto removed the conflicts label Jan 11, 2025
@renovate renovate bot force-pushed the renovate/nginx-18.x branch 6 times, most recently from f71fbaa to 11fc7ae Compare February 6, 2025 13:52
@renovate renovate bot changed the title chore(deps): update nginx docker tag to v18.3.5 chore(deps): update nginx docker tag to v18.3.6 Feb 6, 2025
@renovate renovate bot force-pushed the renovate/nginx-18.x branch 2 times, most recently from a19666a to 29fbaa3 Compare February 17, 2025 10:46
@renovate renovate bot force-pushed the renovate/nginx-18.x branch 3 times, most recently from 8ee6325 to 446a98f Compare March 3, 2025 20:38
@renovate renovate bot force-pushed the renovate/nginx-18.x branch 3 times, most recently from a3daca3 to aa04f74 Compare March 7, 2025 12:27
@renovate renovate bot force-pushed the renovate/nginx-18.x branch 3 times, most recently from ff5e708 to 9c60710 Compare April 15, 2025 04:54
@renovate renovate bot force-pushed the renovate/nginx-18.x branch 8 times, most recently from e8f0fcb to 5d5b657 Compare May 13, 2025 10:43
Copy link
Contributor Author

renovate bot commented May 21, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: charts/sentry/Chart.lock
Command failed: helm registry login --username mdpprodrenovate --password **redacted** registry-1.docker.io/bitnamicharts
WARNING: Using --password via the CLI is insecure. Use --password-stdin.
Error: invalid reference: invalid registry "registry-1.docker.io/bitnamicharts"

@renovate renovate bot force-pushed the renovate/nginx-18.x branch from 5d5b657 to 97282ab Compare May 21, 2025 08:11
@renovate renovate bot force-pushed the renovate/nginx-18.x branch from 97282ab to 25de77f Compare May 23, 2025 03:40
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.

1 participant