Skip to content

chore(deps): update grafana/loki docker tag to v3.7.6 - #592

Open
renovate[bot] wants to merge 2 commits into
devfrom
deps/grafana-loki-3.x
Open

chore(deps): update grafana/loki docker tag to v3.7.6#592
renovate[bot] wants to merge 2 commits into
devfrom
deps/grafana-loki-3.x

Conversation

@renovate

@renovate renovate Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
grafana/loki patch 3.7.53.7.6

Configuration

📅 Schedule: (UTC)

  • 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.


  • 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 added the 🗡️ dependencies Pull requests that update a dependency file label Aug 6, 2026
@renovate
renovate Bot requested a review from wax911 August 6, 2026 13:50
@anitrend

anitrend Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

OpenCode Dependabot Risk Review

Schema: local-stack.dependabot-risk.v1

Decision: NEUTRAL
Risk: LOW
Automerge allowed: false
Update type: semver-patch
Ecosystem: docker

Summary

Renovate PR updates grafana/loki from 3.7.5 to 3.7.6 (patch). The source compose file and three generated stack files are modified. Loki is a stateful service requiring extra scrutiny. Generated stacks are changed with matching source changes, so the REQUEST_CHANGES condition for orphaned stack edits is not triggered. However, deployment files (stacks/*.yml) are modified, which blocks unconditional APPROVE per policy. No release notes context is available to confirm absence of migration risk for this stateful service.

Changed runtime artifacts

Image / dependency From To Risk note
grafana/loki 3.7.5 3.7.6 patch update for stateful service loki; no release notes available to confirm absence of migration changes

Runtime impact

Expected rolling service update for loki. Generated stacks will be redeployed. Stateful service (loki) may require volume/data compatibility verification.

Breaking change assessment

No release notes context available; patch bump from 3.7.5 to 3.7.6 is unlikely to contain breaking changes, but cannot be confirmed without release notes.

Required checks

  • ./stackctl.sh sync
  • ./stackctl.sh up --dry-run --no-logs

Manual follow-up

  • Verify loki 3.7.6 release notes for any migration or config changes
  • Confirm generated stack diffs are consistent with the source compose change only

Sources checked

  • Renovate PR metadata
  • PR diff
  • PR title and body

@anitrend anitrend Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

OpenCode risk gate: low risk detected. Update type: semver-patch. Ecosystem: docker.

@anitrend anitrend Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

OpenCode risk gate: second approval for auto-merge.

@anitrend
anitrend Bot enabled auto-merge (rebase) August 6, 2026 13:51
@anitrend

anitrend Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

OpenCode risk gate: neutral. Manual review required. Risk: low. Reason: Renovate PR updates grafana/loki from 3.7.5 to 3.7.6 (patch). The source compose file and three generated stack files are modified. Loki is a stateful service requiring extra scrutiny. Generated stacks are changed with matching source changes, so the REQUEST_CHANGES condition for orphaned stack edits is not triggered. However, deployment files (stacks/*.yml) are modified, which blocks unconditional APPROVE per policy. No release notes context is available to confirm absence of migration risk for this stateful service.

@renovate

renovate Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🗡️ dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants