[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
io.github.oshai:kotlin-logging-jvm	8.0.4 → 8.0.7

---

Release Notes

oshai/kotlin-logging (io.github.oshai:kotlin-logging-jvm)

v8.0.7

Compare Source

What's Changed

• Bump org.graalvm.sdk:nativeimage from 25.4.4.1.1 to 25.5.5.0.3 by @​dependabot[bot] in #​630
• Build, test, and CI dependency updates (gradle/actions v6, Spotless 8.11.0, Mockito 5.24.0) by @​dependabot[bot] in #​627, #​629, #​631

Full Changelog: oshai/kotlin-logging@8.0.6...8.0.7

v8.0.6

Compare Source

What's Changed

🐛 Bug Fixes & Improvements

• Keep withLoggingContextAsync entries off the thread MDC by @​timobraveweber in #​608
• Deprecate and ignore restorePrevious in withLoggingContextAsync by @​oshai in #​626

📖 Documentation & Maintenance

• Bump version to 8.0.6 and add release playbook by @​oshai

New Contributors

• @​timobraveweber made their first contribution in #​608

Full Changelog: oshai/kotlin-logging@8.0.5...8.0.6

v8.0.5

Compare Source

What's Changed

• fix for incorrect caller info in logger.at(...) by @​LiYing2010 in #​625
• docs: document JVM nested/inner class logger naming by @​oshai in #​622
• upgrade dokka to v2 by @​oshai in #​543
• ci: replace greetings workflow with templates and ignore Kotlin >=2.2 by @​oshai in #​619
• Dependency & GitHub Actions updates (slf4j 2.0.20, logback 1.6.6, log4j 2.26.1, nativeimage 25.4.4.1.1, junit-bom 6.1.3)

New Contributors

• @​LiYing2010 made their first contribution in #​625

Full Changelog: oshai/kotlin-logging@8.0.4...8.0.5

---

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.

[github-actions]

Terraform Plan

✅ No changes — infrastructure is up to date.

Plan output

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

[github-actions]

Terraform Plan

🚧 Changes detected — Plan: 1 to add, 0 to change, 1 to destroy.

Plan output

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # module.ecr.aws_ecr_lifecycle_policy.this must be replaced
-/+ resource "aws_ecr_lifecycle_policy" "this" {
      ~ id          = "cupcake-cupcake-backend" -> (known after apply)
      ~ policy      = jsonencode(
          ~ {
              ~ rules = [
                    {
                        action       = {
                            type = "expire"
                        }
                        description  = "Keep last 5 semver releases"
                        rulePriority = 1
                        selection    = {
                            countNumber   = 5
                            countType     = "imageCountMoreThan"
                            tagPrefixList = [
                                "v",
                            ]
                            tagStatus     = "tagged"
                        }
                    },
                  ~ {
                      ~ selection    = {
                          ~ tagPrefixList = [
                                "main-",
                              - "master-",
                            ]
                            # (3 unchanged attributes hidden)
                        }
                        # (3 unchanged attributes hidden)
                    },
                    {
                        action       = {
                            type = "expire"
                        }
                        description  = "Expire untagged images after 1 day(s)"
                        rulePriority = 3
                        selection    = {
                            countNumber = 1
                            countType   = "sinceImagePushed"
                            countUnit   = "days"
                            tagStatus   = "untagged"
                        }
                    },
                    # (1 unchanged element hidden)
                ]
            } # forces replacement
        )
      ~ registry_id = "553637109631" -> (known after apply)
        # (1 unchanged attribute hidden)
    }

Plan: 1 to add, 0 to change, 1 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

---

LLM Review

Risk: 🟢 LOW

Replaces the ECR lifecycle policy for cupcake-cupcake-backend, removing the "master-" tag prefix from the semver/main retention rule; no infrastructure exposure, cost, or data-loss risk beyond image cleanup behavior.

• 💥 [destruction] aws_ecr_lifecycle_policy.this is destroyed and recreated (forces replacement because the policy JSON changed). Only the lifecycle policy is replaced, not the ECR repository itself, so no images are deleted directly; the replacement takes effect immediately.
• ✅ [routine] The only functional change is removing "master-" from tagPrefixList in the rule that protects tagged images. Images tagged with the master- prefix will no longer be protected by that rule and may be expired once the policy is applied, unless they match another rule. Confirm that no active images rely on the master- prefix before applying.
• 🔒 [security] No IAM, security group, or public access changes in this plan.
• 💰 [cost] No new billable resources. Removing the master- prefix may reduce ECR storage costs by allowing older images to expire.