Repository navigation
Comparing changes
Open a pull request
base repository: operator-framework/java-operator-sdk
base: v5.6.2
head repository: operator-framework/java-operator-sdk
compare: main
- 11 commits
- 25 files changed
- 3 contributors
Commits on Sep 22, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 70988d1 - Browse repository at this point
Copy the full SHA 70988d1View commit details
Commits on Sep 25, 2026
-
chore(deps): bump com.github.ben-manes.caffeine:caffeine (#3633)
Bumps [com.github.ben-manes.caffeine:caffeine](https://github.com/ben-manes/caffeine) from 3.2.4 to 3.3.0. - [Release notes](https://github.com/ben-manes/caffeine/releases) - [Commits](ben-manes/caffeine@v3.2.4...v3.3.0) --- updated-dependencies: - dependency-name: com.github.ben-manes.caffeine:caffeine dependency-version: 3.3.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 53f2170 - Browse repository at this point
Copy the full SHA 53f2170View commit details -
fix: harden the release workflow against irreversible failures (#3632)
Once artifacts are deployed to Maven Central they cannot be changed, so anything that would make the release fail afterwards is now checked before deploying, and the final push can no longer overwrite someone else's changes. Before deploying: - Check that the release tag, if it already exists, points into the history of the branch being released. This needs a full checkout with tags. - Refuse to release a version older than the one the branch is already developing. That means the wrong branch was picked for the tag, and finalize would otherwise move the branch back onto versions that are already released. Finalize: - Repeat the backwards-version check on the computed next -SNAPSHOT version. - Push the tag with --force-with-lease against the value seen during the ancestry check, instead of force-pushing it. With --atomic, a tag or branch moved by someone else during the release now fails the whole push and nothing is overwritten. - Explain in a comment how to finish the release by hand if that push is rejected. Also: - Move the pom version parser into a shared inline POM_VERSION_PY script, used by both jobs, that fails clearly when the pom has no version. It stays inline because older maintenance branches would not have a script file in the repo. - Keep the concurrency group, with a comment explaining why two releases must not run at the same time. Signed-off-by: Attila Mészáros <a_meszaros@apple.com>Configuration menu - View commit details
-
Copy full SHA for 7c3ec5e - Browse repository at this point
Copy the full SHA 7c3ec5eView commit details
Commits on Sep 28, 2026
-
chore(deps): bump org.mockito:mockito-core from 5.23.0 to 5.24.0 (#3638)
Bumps [org.mockito:mockito-core](https://github.com/mockito/mockito) from 5.23.0 to 5.24.0. - [Release notes](https://github.com/mockito/mockito/releases) - [Commits](mockito/mockito@v5.23.0...v5.24.0) --- updated-dependencies: - dependency-name: org.mockito:mockito-core dependency-version: 5.24.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for cd98a11 - Browse repository at this point
Copy the full SHA cd98a11View commit details -
chore(deps): bump org.slf4j:slf4j-api from 2.0.19 to 2.0.20 (#3637)
Bumps org.slf4j:slf4j-api from 2.0.19 to 2.0.20. --- updated-dependencies: - dependency-name: org.slf4j:slf4j-api dependency-version: 2.0.20 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for d2e9cf5 - Browse repository at this point
Copy the full SHA d2e9cf5View commit details -
test: fix flaky TriggerReconcilerOnAllEventIT.additionalEventDuringRe…
…tryOnDeleteEvent (#3634) The test assumed at least 3 reconciliations happen before the reconciler starts waiting on the first retry. If the delete event arrives before the first reconciliation reads the resource, the finalizer-adding reconciliation is skipped, the reconciler starts waiting at count 2, and the test and the reconciler block on each other until timeout. Wait for the reconciler to be waiting and snapshot the event count then instead.
Configuration menu - View commit details
-
Copy full SHA for 49eda9f - Browse repository at this point
Copy the full SHA 49eda9fView commit details -
chore(deps): bump manusa/actions-setup-minikube from 2.18.0 to 2.19.0 (…
…#3635) Bumps [manusa/actions-setup-minikube](https://github.com/manusa/actions-setup-minikube) from 2.18.0 to 2.19.0. - [Release notes](https://github.com/manusa/actions-setup-minikube/releases) - [Commits](manusa/actions-setup-minikube@v2.18.0...v2.19.0) --- updated-dependencies: - dependency-name: manusa/actions-setup-minikube dependency-version: 2.19.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 29d60fc - Browse repository at this point
Copy the full SHA 29d60fcView commit details -
chore(ci): test against Kubernetes 1.37, drop EOL 1.32 and 1.33 (#3602)
Bump minikube to v1.39.0 (newest supported Kubernetes version is v1.37.0) and update the tested Kubernetes versions to the four currently supported upstream minors: 1.34, 1.35, 1.36 and 1.37.
Configuration menu - View commit details
-
Copy full SHA for aff1c64 - Browse repository at this point
Copy the full SHA aff1c64View commit details
Commits on Sep 30, 2026
-
chore(deps): bump org.apache.commons:commons-lang3 from 3.20.0 to 3.2…
…1.0 (#3640) Bumps org.apache.commons:commons-lang3 from 3.20.0 to 3.21.0. --- updated-dependencies: - dependency-name: org.apache.commons:commons-lang3 dependency-version: 3.21.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 97d0036 - Browse repository at this point
Copy the full SHA 97d0036View commit details
Commits on Oct 2, 2026
-
chore(deps): bump org.apache.maven:apache-maven from 3.9.16 to 3.10.0 (…
…#3642) Bumps org.apache.maven:apache-maven from 3.9.16 to 3.10.0. --- updated-dependencies: - dependency-name: org.apache.maven:apache-maven dependency-version: 3.10.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 15341c9 - Browse repository at this point
Copy the full SHA 15341c9View commit details -
chore(deps): bump org.apache.maven:maven-plugin-api (#3641)
Bumps [org.apache.maven:maven-plugin-api](https://github.com/apache/maven) from 3.9.16 to 3.10.0. - [Release notes](https://github.com/apache/maven/releases) - [Commits](apache/maven@maven-3.9.16...maven-3.10.0) --- updated-dependencies: - dependency-name: org.apache.maven:maven-plugin-api dependency-version: 3.10.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for b300073 - Browse repository at this point
Copy the full SHA b300073View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v5.6.2...main