Skip to content

chore(deps): update nextcloud-33:33.0.2 docker digest to 39b2ba2#693

Open
renovate-bot-cbcoutinho[bot] wants to merge 1 commit intomasterfrom
renovate/nextcloud-33-33.0.2
Open

chore(deps): update nextcloud-33:33.0.2 docker digest to 39b2ba2#693
renovate-bot-cbcoutinho[bot] wants to merge 1 commit intomasterfrom
renovate/nextcloud-33-33.0.2

Conversation

@renovate-bot-cbcoutinho
Copy link
Copy Markdown
Contributor

@renovate-bot-cbcoutinho renovate-bot-cbcoutinho Bot commented Apr 7, 2026

This PR contains the following updates:

Package Update Change
nextcloud-33 digest 661284c39b2ba2

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 has been generated by Renovate Bot.

@claude
Copy link
Copy Markdown

claude Bot commented Apr 7, 2026

PR Review: #693

This is a Renovate Bot digest update for the commented-out Nextcloud 33 image in .github/workflows/test.yml.

Change: nextcloud:33.0.2 digest 661284c -> 61dd3e5

No functional impact - the line is commented out (NC 33 support is intentionally disabled). Security practice is sound: pinning to digest prevents mutable-tag supply chain attacks, and keeping it current while disabled means it will be ready when NC 33 support is re-enabled.

Safe to merge. No blockers.

@renovate-bot-cbcoutinho renovate-bot-cbcoutinho Bot changed the title chore(deps): update nextcloud-33:33.0.2 docker digest to 61dd3e5 chore(deps): update nextcloud-33:33.0.2 docker digest to 03cab7c Apr 10, 2026
@renovate-bot-cbcoutinho renovate-bot-cbcoutinho Bot force-pushed the renovate/nextcloud-33-33.0.2 branch from cd945f2 to 1118b10 Compare April 10, 2026 04:15
@claude
Copy link
Copy Markdown

claude Bot commented Apr 10, 2026

PR Review: Dependency Digest Update

This is a routine Renovate Bot update bumping the Docker digest for nextcloud:33.0.2 from @sha256:661284c... to @sha256:03cab7c....

Assessment: Safe to merge

Key observations:

  1. Zero runtime impact — The changed line is in a commented-out section (# Disabled until all upstream apps support NC 33). This update has no effect on any currently executing CI jobs.

  2. Good hygiene — Keeping digest pins current even for disabled image references is sound practice. When NC 33 gets re-enabled, the digest will point to an up-to-date image rather than one that may have drifted.

  3. No logic changes — This is a pure digest rotation; the Nextcloud version (33.0.2) is unchanged.

No concerns. This can be merged whenever the rest of the NC 33 enablement work is ready, or simply merged now to keep the dependency graph tidy.

@renovate-bot-cbcoutinho renovate-bot-cbcoutinho Bot force-pushed the renovate/nextcloud-33-33.0.2 branch from 1118b10 to dce01a5 Compare April 10, 2026 10:15
@renovate-bot-cbcoutinho renovate-bot-cbcoutinho Bot changed the title chore(deps): update nextcloud-33:33.0.2 docker digest to 03cab7c chore(deps): update nextcloud-33:33.0.2 docker digest to 8eeeb6a Apr 10, 2026
@claude
Copy link
Copy Markdown

claude Bot commented Apr 10, 2026

PR Review: Dependency Update — Nextcloud 33 Docker Digest

This is a straightforward Renovate Bot dependency update. Here's the assessment:

What's changing

  • Updates the pinned SHA256 digest for nextcloud:33.0.2 from 661284c8eeeb6a in .github/workflows/test.yml

Assessment

No functional impact — the updated line remains commented out. The comment above it (# Disabled until all upstream apps support NC 33) still applies, so this change has zero effect on CI runs.

Security practice is correct — pinning Docker images to immutable SHA256 digests (rather than mutable tags) is best practice. This prevents tag-mutation supply chain attacks. Good that Renovate is keeping the digest current even while the line is commented out.

Safe to merge — since the line is inert (commented), there's no regression risk. The only reason to defer merging would be if you want to minimize noise in the commit history, but that's a style preference.

Suggestion (optional)

If NC 33 support is getting closer, it might be worth tracking that in a GitHub issue so the uncomment doesn't get forgotten. The digest will be current once you're ready to enable it.

Looks good — no issues found.

@renovate-bot-cbcoutinho renovate-bot-cbcoutinho Bot changed the title chore(deps): update nextcloud-33:33.0.2 docker digest to 8eeeb6a chore(deps): update nextcloud-33:33.0.2 docker digest to 3e676af Apr 13, 2026
@renovate-bot-cbcoutinho renovate-bot-cbcoutinho Bot force-pushed the renovate/nextcloud-33-33.0.2 branch from dce01a5 to 6bc9abe Compare April 13, 2026 04:16
@claude
Copy link
Copy Markdown

claude Bot commented Apr 13, 2026

PR Review

This is a Renovate Bot dependency update that bumps the Docker image digest for nextcloud:33.0.2 from sha256:661284c... to sha256:3e676af... in .github/workflows/test.yml.

Assessment

Safe to merge. A few observations:

  1. No functional impact: The updated line is still commented out (# - nextcloud_image: ...). NC33 testing remains disabled per the comment "Disabled until all upstream apps support NC 33", so this change has zero effect on CI runs.

  2. Good hygiene: Keeping the commented digest current is still worthwhile — when NC33 support is eventually enabled, the pinned digest will reflect a more recent (likely patched) image rather than an older one from when the comment was first written.

  3. Digest pinning: Continuing to use @sha256:... digest pinning is the correct security practice — it guarantees reproducibility and protects against tag-mutable image pulls.

No code, logic, or test changes to review. This can be merged at any time or batched with other Renovate updates.

@renovate-bot-cbcoutinho renovate-bot-cbcoutinho Bot force-pushed the renovate/nextcloud-33-33.0.2 branch from 6bc9abe to 2b39079 Compare April 23, 2026 04:24
@renovate-bot-cbcoutinho renovate-bot-cbcoutinho Bot changed the title chore(deps): update nextcloud-33:33.0.2 docker digest to 3e676af chore(deps): update nextcloud-33:33.0.2 docker digest to 6e1029b Apr 23, 2026
@claude
Copy link
Copy Markdown

claude Bot commented Apr 23, 2026

PR Review

Routine Renovate digest update for nextcloud:33.0.2 (661284c6e1029b).

The changed line remains commented out — no CI impact. Digest pinning hygiene is correct. Safe to merge.

(Previous reviews on 2026-04-07, 04-10, 04-13 reached the same conclusion — no new concerns.)

@renovate-bot-cbcoutinho renovate-bot-cbcoutinho Bot changed the title chore(deps): update nextcloud-33:33.0.2 docker digest to 6e1029b chore(deps): update nextcloud-33:33.0.2 docker digest to 39b2ba2 Apr 27, 2026
@renovate-bot-cbcoutinho renovate-bot-cbcoutinho Bot force-pushed the renovate/nextcloud-33-33.0.2 branch from 2b39079 to 5fcbe12 Compare April 27, 2026 04:21
@claude
Copy link
Copy Markdown

claude Bot commented Apr 27, 2026

PR Review

Routine Renovate digest update for nextcloud:33.0.2 (661284c39b2ba2).

The changed line remains commented out — no CI impact. Digest pinning hygiene is correct. Safe to merge whenever NC33 readiness is being tracked.

(Consistent with prior reviews — no new concerns.)

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