Skip to content

chore(deps): update ghcr.io/anitrend/on-the-edge docker tag to v1.6.6 - #596

Merged
anitrend[bot] merged 2 commits into
devfrom
deps/ghcr.io-anitrend-on-the-edge-1.x
Aug 7, 2026
Merged

chore(deps): update ghcr.io/anitrend/on-the-edge docker tag to v1.6.6#596
anitrend[bot] merged 2 commits into
devfrom
deps/ghcr.io-anitrend-on-the-edge-1.x

Conversation

@renovate

@renovate renovate Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
ghcr.io/anitrend/on-the-edge patch 1.6.51.6.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 7, 2026
@renovate
renovate Bot requested a review from wax911 August 7, 2026 21:27
@renovate renovate Bot added the 🗡️ dependencies Pull requests that update a dependency file label Aug 7, 2026
@anitrend

anitrend Bot commented Aug 7, 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 proposes bumping ghcr.io/anitrend/on-the-edge from 1.6.5 to 1.6.6 (patch). The source compose and the generated stack are both modified. No release notes are available to verify the change, and the generated stack file is a deployment artifact, so the update is classified as neutral per policy.

Changed runtime artifacts

Image / dependency From To Risk note
ghcr.io/anitrend/on-the-edge 1.6.5 1.6.6 patch bump for project-owned image; no release notes available to confirm safety

Runtime impact

Expected rolling service update only; on-the-edge is not a stateful or gateway service.

Breaking change assessment

No release notes available; patch bump unlikely to introduce breaking changes.

Required checks

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

Manual follow-up

  • Verify that stacks/platform.yml regeneration matches the compose change (stackctl generate).

Sources checked

  • Renovate PR metadata
  • PR diff
  • PR body and labels

@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 7, 2026 21:27
@anitrend

anitrend Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

OpenCode risk gate: neutral. Manual review required. Risk: low. Reason: Renovate proposes bumping ghcr.io/anitrend/on-the-edge from 1.6.5 to 1.6.6 (patch). The source compose and the generated stack are both modified. No release notes are available to verify the change, and the generated stack file is a deployment artifact, so the update is classified as neutral per policy.

@anitrend
anitrend Bot merged commit 60f19b0 into dev Aug 7, 2026
6 checks passed
@anitrend
anitrend Bot deleted the deps/ghcr.io-anitrend-on-the-edge-1.x branch August 7, 2026 21:28
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