Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: openrewrite/java-object-diff
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.0.1
Choose a base ref
...
head repository: openrewrite/java-object-diff
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.0.2
Choose a head ref
  • 4 commits
  • 7 files changed
  • 2 contributors

Commits on Apr 23, 2025

  1. Configuration menu
    Copy the full SHA
    f0ce8c9 View commit details
    Browse the repository at this point in the history

Commits on Apr 28, 2025

  1. Gradle 8.14

    greg-at-moderne committed Apr 28, 2025
    Configuration menu
    Copy the full SHA
    376a723 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    b1a0e99 View commit details
    Browse the repository at this point in the history

Commits on Aug 17, 2026

  1. Publish releases to the Code Genome Project alongside Maven Central (#1)

    * Publish releases to the Code Genome Project instead of Maven Central
    
    Bump `org.openrewrite.build.recipe-library` from 1.8.1 to `latest.release`,
    which is what applies `org.openrewrite.build.publish-cgp`. That plugin needs
    Groovy 4, so the Gradle wrapper moves from 8.14 to 9.7.0 to match the rest of
    the org.
    
    Disable the Sonatype repository and staging tasks so `publish` targets only
    the `cgp` repository, while the shared publish workflow can keep invoking
    `closeAndReleaseSonatypeStagingRepository`.
    
    Forward the cgp_* publishing and resolution secrets in both workflows, and
    rename ossrh_username/ossrh_token to sonatype_username/sonatype_token, which
    is what the shared gh-automation workflows now declare. Also point ci.yml at
    `master`, the repository's actual default branch, so CI runs at all.
    
    * Keep publishing to Maven Central alongside the Code Genome Project
    
    * Publish snapshots from master
    
    ci-gradle.yml gates its snapshot step on `refs/heads/main`, so this repository
    never published snapshots. Add a job that runs the same publish-snapshots
    action on pushes to master, and opt out of the shared step so the two cannot
    both fire if that condition is later broadened.
    
    * Revert to the shared snapshot publishing now that the branch is main
    
    The default branch was renamed from master to main, so ci-gradle.yml's own
    snapshot step matches again and the repository-local job it needed is gone.
    timtebeek authored Aug 17, 2026
    Configuration menu
    Copy the full SHA
    c5033b4 View commit details
    Browse the repository at this point in the history
Loading