Skip to content

chore(deps): update registry.fedoraproject.org/fedora docker tag to v46 - #633

Closed
mergeraptor[bot] wants to merge 1 commit into
mainfrom
renovate/registry.fedoraproject.org-fedora-46.x
Closed

mergeraptor[bot] wants to merge 1 commit into
mainfrom
renovate/registry.fedoraproject.org-fedora-46.x

Conversation

@mergeraptor

@mergeraptor mergeraptor Bot commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
registry.fedoraproject.org/fedora major 44 → 46

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 Mend Renovate CLI.

@jeefy
jeefy requested review from bketelsen and daegalus November 6, 2026 06:20
@jeefy

jeefy commented Nov 6, 2026

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign ahmedadan after the PR has been reviewed.
You can assign the PR to them by writing /assign @ahmedadan in a comment when ready.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@hivecommons-hive

hivecommons-hive Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor
d1dc0ea

ℹ️ Sentinel notice — informational; author is trusted (allow-listed bot), merge is not blocked

Hive flagged this PR (author @mergeraptor[bot], head d1dc0ea9f741) because it matches behaviors that can override security controls, escalate privileges or damage the codebase. This is a heuristic, not an accusation — a maintainer should confirm the change is intended before it merges.

  • sensitive_path — changes 1 sensitive path(s) (Touches a sensitive path (OWNERS, workflows, policies, hive config, security docs, …))
    • Justfile

Hive did not add the sentinel-alert label because this author is trusted. The finding remains recorded for audit and the dashboard Security tab; set sentinel.trusted_authors_block: true to require the blocking label for trusted authors too.

@hivecommons-hive

hivecommons-hive Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

🐝 Superseded regeneration series

mergeraptor[bot] has 2 open PRs regenerating the same file(s). This one is the newest, so the 1 older one(s) are superseded by construction:

Posted once on the newest PR rather than on each of them, so a daily regeneration does not produce a daily comment on every PR in the series.

Evidence — identical changed-file set (1 file(s)):

  • Justfile

This is a suggestion, not a verdict. Hive will not close, label, approve or merge anything here — a human decides.

It was produced by comparing changed-file sets across open PRs, which is a candidate generator: PRs that share a file are not necessarily the same work. Here the patches DIFFER, so this is the weaker tier: dependency-bump PRs that edit one shared manifest, and unrelated fixes to one busy file, both land in it. Read the diffs before acting.

@mergeraptor
mergeraptor Bot force-pushed the renovate/registry.fedoraproject.org-fedora-46.x branch from b52497f to d1dc0ea Compare November 6, 2026 09:16
@jeefy

jeefy commented Nov 6, 2026

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign ahmedadan after the PR has been reviewed.
You can assign the PR to them by writing /assign @ahmedadan in a comment when ready.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@Danathar

Danathar commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Heads-up before anyone /lgtms this: the fedora:46 digest pinned here (sha256:02031526…e2ff) is the same digest the registry currently serves for fedora:rawhide. Fedora 46 isn't released yet; fedora:45 is the current release (same digest as fedora:latest, sha256:5ad38625…bbb0). So this would move the just check-image tool base onto Rawhide. Leaving the call (close, or retarget to 45 plus a Renovate rule against unreleased Fedora) to the maintainers.

Checked 2026-11-06 with manifest HEAD requests to registry.fedoraproject.org for the latest, rawhide, 45 and 46 tags.

@castrojo

castrojo commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

Closing per the maintainer decision to keep just check-image tooling on stable Fedora 44. This pinned Fedora 46 image uses Rawhide repositories; #637 remains the stable-44 digest refresh. Revisit Fedora 46 with a stable image and a fresh digest after its release.

@castrojo castrojo closed this Nov 8, 2026
@mergeraptor

mergeraptor Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 46.x releases. But if you manually upgrade to 46.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@mergeraptor
mergeraptor Bot deleted the renovate/registry.fedoraproject.org-fedora-46.x branch November 9, 2026 00:27
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.

3 participants