Skip to content

Update dependency org.jetbrains.kotlinx:kotlinx-serialization-json to v1.13.0 - autoclosed - #268

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/kotlinx.serialization
Closed

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/kotlinx.serialization

Conversation

@renovate

@renovate renovate Bot commented Nov 11, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
org.jetbrains.kotlinx:kotlinx-serialization-json 1.12.0 → 1.13.0 age confidence

Release Notes

Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-json)

v1.13.0

===================

This release is based on Kotlin 2.4.10 and reverts a breaking change introduced in 1.12.0.

Besides that, it improves JsonElement.toString performance.

Exceptions rework rollback

In 1.12.0, Json format start intercepting almost all exceptions thrown by serializers during serialization and
deserialization, and wrap them into a JsonException with additional information about JSON path and input.

The impact of the change was underestimated, and it was decided to revert the change.

Performance improvements

JsonElement.toString was rewritten and its improved twofold on some benchmarks.
See #​3296 and #​3299 for details.


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

Copy link
Copy Markdown

Terraform Plan

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

Plan output
Acquiring state lock. This may take a few moments...

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 (1 add, 1 destroy) because the policy JSON changed: the "main-" rule drops "master-" from its tag prefix list, which forces replacement.

  • 💥 [destruction] The aws_ecr_lifecycle_policy is destroyed and recreated rather than updated in place (the policy field forces replacement). Only the lifecycle policy resource is affected; no ECR repository or images are deleted. Expect a brief window where the lifecycle rules do not exist between destroy and create.
  • ✅ [routine] The only semantic change is removing the "master-" tag prefix from the rule that protects "main-" tagged images from expiry. Images tagged with the "master-" prefix will no longer be exempt, and the 'Keep last 5 semver releases' (v-prefix) and 'Expire untagged after 1 day' rules are unchanged. Confirm that no active images still use the master- prefix, otherwise they may be expired by the rule that now applies to them.
  • 💰 [cost] No new billable resources. Storage costs could change slightly depending on which images are expired by the updated rule.
  • 🔒 [security] No IAM, security group, or public access changes in this plan.

@renovate renovate Bot changed the title Update dependency org.jetbrains.kotlinx:kotlinx-serialization-json to v1.13.0 Update dependency org.jetbrains.kotlinx:kotlinx-serialization-json to v1.13.0 - autoclosed Nov 12, 2026
@renovate renovate Bot closed this Nov 12, 2026
@renovate
renovate Bot deleted the renovate/kotlinx.serialization branch November 12, 2026 08:39
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.

0 participants