chore(deps): update cloudoperators/juno digest to 48dd344

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cloudoperators/juno (changelog)	action	digest	f0c9d08 → 48dd344

---

Configuration

📅 Schedule: (in timezone Europe/Berlin)

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 880ba17

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Copilot]

Pull request overview

Note

Copilot could not run the full agentic suite for this review because it was automatically requested on a bot-authored pull request. Request a review from Copilot under Reviewers to retry with the full agentic suite. Improved support for bot-authored pull requests is coming soon.

Updates the pinned reference for the shared Slack notification reusable workflow used across multiple GitHub Actions workflows.

Changes:

• Bump cloudoperators/juno/.github/workflows/shared-slack-notification.yaml from f0c9d08… to cf79a1f… in release notifications.
• Bump the same reusable workflow reference in image build/push workflows (Supernova, Greenhouse, PR preview cleanup).

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.

File	Description
.github/workflows/release.yaml	Updates the reusable Slack notification workflow commit SHA for success/failure notifications.
.github/workflows/build-push-supernova-image.yaml	Updates the reusable Slack notification workflow commit SHA for failure notification.
.github/workflows/build-push-greenhouse-pr-preview.yaml	Updates the reusable Slack notification workflow commit SHA for cleanup-failure notification.
.github/workflows/build-push-greenhouse-image.yaml	Updates the reusable Slack notification workflow commit SHA for failure notification.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (3)

.github/workflows/release.yaml:79

• The inline comment # main is misleading when pinning to a specific commit SHA (it no longer reflects the main ref, but a snapshot). Consider changing it to something like # pinned / # commit (optionally include the upstream tag/version) to avoid confusion during future audits and updates.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@3a9760d43222cfa4912d61b052b1f062a7bfc48d # main

.github/workflows/release.yaml:90

• The inline comment # main is misleading when pinning to a specific commit SHA (it no longer reflects the main ref, but a snapshot). Consider changing it to something like # pinned / # commit (optionally include the upstream tag/version) to avoid confusion during future audits and updates.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@3a9760d43222cfa4912d61b052b1f062a7bfc48d # main

.github/workflows/build-push-supernova-image.yaml:204

• The same reusable workflow SHA is duplicated across multiple workflow files in this PR, which makes future bumps easy to miss and harder to review. Consider introducing a local wrapper reusable workflow (e.g., .github/workflows/slack-notify.yaml) that internally calls the upstream cloudoperators/juno workflow at the pinned SHA; then have all callers reference the local wrapper so the pin is updated in one place.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@3a9760d43222cfa4912d61b052b1f062a7bfc48d # main

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (3)

.github/workflows/release.yaml:1

• The same reusable workflow revision is duplicated (even within this file) and also repeated across multiple workflow files in this PR. This increases the chance of version drift and makes future bumps more error-prone. Consider centralizing the reference (e.g., create a local reusable workflow wrapper in this repo that pins cloudoperators/juno/...@<sha> once, then have workflows call the local wrapper), or use YAML anchors/aliases within a file to avoid repeating the same uses: string in multiple jobs.

name: Release

.github/workflows/release.yaml:93

• The same reusable workflow revision is duplicated (even within this file) and also repeated across multiple workflow files in this PR. This increases the chance of version drift and makes future bumps more error-prone. Consider centralizing the reference (e.g., create a local reusable workflow wrapper in this repo that pins cloudoperators/juno/...@<sha> once, then have workflows call the local wrapper), or use YAML anchors/aliases within a file to avoid repeating the same uses: string in multiple jobs.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@5ba36b2779a7a4af75cdfc20cfc5567865020fac # main
    with:
      title: "🚨 JUNO Packages Release Failed 🚨"
      body: "An error occurred while releasing JUNO Packages for the branch ${{ github.head_ref || github.ref_name }}. Please check the logs for more information. <${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}|Check the logs>"

.github/workflows/build-push-supernova-image.yaml:204

• The inline comment # main is misleading because the workflow is pinned to a specific commit SHA, not the main ref. Updating/removing this comment (and the same comment in other workflow files) would avoid confusion; for example, note the short SHA or a release tag if one exists.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@5ba36b2779a7a4af75cdfc20cfc5567865020fac # main

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (3)

.github/workflows/release.yaml:79

• The pinned reusable-workflow SHA is duplicated across multiple workflows/files, which increases the chance of inconsistent upgrades in the future. Consider introducing a local wrapper reusable workflow (e.g., uses: ./.github/workflows/shared-slack-notification-wrapper.yaml) that internally calls cloudoperators/juno/...@<sha> so future SHA bumps happen in one place.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@7aa14ad04fba12a67a33e8cbbad5f5ecb9422e1b # main

.github/workflows/release.yaml:90

• The pinned reusable-workflow SHA is duplicated across multiple workflows/files, which increases the chance of inconsistent upgrades in the future. Consider introducing a local wrapper reusable workflow (e.g., uses: ./.github/workflows/shared-slack-notification-wrapper.yaml) that internally calls cloudoperators/juno/...@<sha> so future SHA bumps happen in one place.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@7aa14ad04fba12a67a33e8cbbad5f5ecb9422e1b # main

.github/workflows/release.yaml:79

• The inline comment # main is potentially misleading since the workflow is pinned to a specific commit SHA (not the moving main ref). Suggest updating the comment to something unambiguous (e.g., # pinned or # juno <version/tag/commit>), or remove it to avoid implying it tracks the branch.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@7aa14ad04fba12a67a33e8cbbad5f5ecb9422e1b # main

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (2)

.github/workflows/release.yaml:79

• The inline comment # main is misleading when the workflow is pinned to a specific commit SHA (it may no longer reflect the current main). Consider removing the comment or replacing it with a versioned note (e.g., the intended upstream release/tag or a short reason for the bump) to avoid confusion during future audits.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@f2f7fde7ac0c3f351c179d54a22948d69872ef0f # main

.github/workflows/release.yaml:90

• The inline comment # main is misleading when the workflow is pinned to a specific commit SHA (it may no longer reflect the current main). Consider removing the comment or replacing it with a versioned note (e.g., the intended upstream release/tag or a short reason for the bump) to avoid confusion during future audits.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@f2f7fde7ac0c3f351c179d54a22948d69872ef0f # main

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (5)

.github/workflows/release.yaml:79

• The inline comment # main is misleading when pinning to a specific commit SHA (it’s not actually tracking the main ref). Consider updating the comment to reflect that this is a pinned commit (optionally include why/when it was bumped), or remove the # main marker to avoid confusion during future audits.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@1830872f583f5ef55824d2cddb3d48e14636ff9c # main

.github/workflows/release.yaml:90

• The inline comment # main is misleading when pinning to a specific commit SHA (it’s not actually tracking the main ref). Consider updating the comment to reflect that this is a pinned commit (optionally include why/when it was bumped), or remove the # main marker to avoid confusion during future audits.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@1830872f583f5ef55824d2cddb3d48e14636ff9c # main

.github/workflows/build-push-supernova-image.yaml:204

• Same as other workflows: # main is misleading alongside a pinned commit SHA. Update/remove the comment so it accurately reflects the pinning strategy.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@1830872f583f5ef55824d2cddb3d48e14636ff9c # main

.github/workflows/build-push-greenhouse-pr-preview.yaml:243

• The # main comment conflicts with the use of a pinned SHA. Recommend adjusting the comment to avoid implying this tracks the main branch.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@1830872f583f5ef55824d2cddb3d48e14636ff9c # main

.github/workflows/build-push-greenhouse-image.yaml:185

• The # main suffix is ambiguous/misleading when using a fixed commit SHA. Please update/remove the comment to match the actual reference being used.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@1830872f583f5ef55824d2cddb3d48e14636ff9c # main

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (5)

.github/workflows/release.yaml:79

• The inline comment # main is misleading when the workflow is pinned to a specific commit SHA (which may or may not be the current main). Consider updating the comment to reflect that it’s intentionally pinned (e.g., # pinned SHA) or switch to @main if the intent is to always track main.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@ff8f38b3ea91dc3e4d8a47f7a489bba0d4cb5995 # main

.github/workflows/release.yaml:90

• The inline comment # main is misleading when the workflow is pinned to a specific commit SHA (which may or may not be the current main). Consider updating the comment to reflect that it’s intentionally pinned (e.g., # pinned SHA) or switch to @main if the intent is to always track main.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@ff8f38b3ea91dc3e4d8a47f7a489bba0d4cb5995 # main

.github/workflows/build-push-supernova-image.yaml:204

• The comment # main is inaccurate/misleading when using a pinned commit SHA. Please update the comment to indicate the ref is pinned, or change the ref to @main if tracking main is intended.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@ff8f38b3ea91dc3e4d8a47f7a489bba0d4cb5995 # main

.github/workflows/build-push-greenhouse-pr-preview.yaml:243

• The # main comment conflicts with the pinned SHA ref. Adjust the comment to reflect the pinning (or switch to @main if that’s the desired behavior).

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@ff8f38b3ea91dc3e4d8a47f7a489bba0d4cb5995 # main

.github/workflows/build-push-greenhouse-image.yaml:185

• The inline # main comment is misleading when the workflow is pinned to a commit SHA. Update the comment to indicate the SHA is intentionally pinned, or use @main if the workflow should track the main branch.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@ff8f38b3ea91dc3e4d8a47f7a489bba0d4cb5995 # main

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (2)

.github/workflows/release.yaml:79

• The inline comment # main is misleading when the workflow is pinned to a specific commit SHA (it’s not actually tracking the main branch). Consider updating the comment to reflect that it’s intentionally pinned (e.g., # pinned) or switch to @main if you explicitly want to track the branch (with the associated supply-chain tradeoff).

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@45c75d02861631ab8282ea39e6dc41a5ab80ccaa # main

.github/workflows/release.yaml:90

• The inline comment # main is misleading when the workflow is pinned to a specific commit SHA (it’s not actually tracking the main branch). Consider updating the comment to reflect that it’s intentionally pinned (e.g., # pinned) or switch to @main if you explicitly want to track the branch (with the associated supply-chain tradeoff).

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@45c75d02861631ab8282ea39e6dc41a5ab80ccaa # main

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (5)

.github/workflows/release.yaml:79

• The inline comment # main is misleading when the workflow is pinned to a specific commit SHA (it won’t track main). Consider updating the comment to reflect that this is a pinned SHA (optionally with a short SHA or date), or switch to a protected version tag if you intentionally want main-like behavior.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@9e069b7593f2057131ef6487192f865768d2cf94 # main

.github/workflows/release.yaml:90

• Same issue as above: # main suggests the reference follows the main branch, but the uses: line is pinned to an immutable commit. Updating the comment will reduce confusion for future maintenance.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@9e069b7593f2057131ef6487192f865768d2cf94 # main

.github/workflows/build-push-supernova-image.yaml:204

• The # main comment is inaccurate for a pinned SHA reference. Recommend adjusting the comment to indicate it is pinned (or reference a version tag if you want an updatable pointer).

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@9e069b7593f2057131ef6487192f865768d2cf94 # main

.github/workflows/build-push-greenhouse-pr-preview.yaml:243

• The # main comment is misleading given the SHA pin. Updating the comment to something like # pinned (optionally with short SHA/date) makes intent clearer.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@9e069b7593f2057131ef6487192f865768d2cf94 # main

.github/workflows/build-push-greenhouse-image.yaml:185

• Same as other occurrences: # main doesn’t match a commit-pinned uses: reference. Consider updating the comment to reflect the pinning strategy.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@9e069b7593f2057131ef6487192f865768d2cf94 # main

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (1)

.github/workflows/release.yaml:79

• The inline comment # main is misleading when the workflow is pinned to a specific commit SHA (it’s not actually referencing the main branch). Consider updating the comment to reflect that it’s pinned (e.g., remove the comment, or replace with something like # pinned / # <commit>), and make the same adjustment for the other occurrences in this PR.

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@2870375c47353e2ee55f0c368a0e438a0af503b5 # main

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (1)

.github/workflows/release.yaml:79

• The inline comment # main is misleading because the workflow is pinned to a specific commit SHA, not tracking the main branch. Consider updating the comment to reflect that it’s pinned (e.g., # pinned / # <short-sha>) or remove the branch reference comment. (Same issue appears in the other updated workflows too.)

    uses: cloudoperators/juno/.github/workflows/shared-slack-notification.yaml@48dd3445891c5a3534ecf33d031b61165945f606 # main