spuru9 opened a new pull request, #69: URL: https://github.com/apache/flink-connector-mongodb/pull/69
## Purpose of the change Aligns the connector with the latest `flink-connector-parent` (2.0.0) and Flink core releases, per [FLINK-40066](https://issues.apache.org/jira/browse/FLINK-40066). Same update as done for Kafka (FLINK-39138), OpenSearch (FLINK-39707), Elasticsearch (FLINK-39809) and AWS (FLINK-40065). - Bump `flink-connector-parent` 1.1.0 → 2.0.0 (raises base Java version from 8 to 11, enables the RAT license check by default) - Bump `flink.version` 2.1.0 → 2.1.2 (latest patch of the 2.1 line) - Switch the `japicmp-maven-plugin` groupId to `com.github.siom79.japicmp`, as managed by the new parent - Adjust the `JavadocMethod` checkstyle configuration in `tools/maven/checkstyle.xml` (the properties removed here no longer exist under the newer Checkstyle version) - Add the missing ASF license header to `flink-connector-mongodb-table-tests/pom.xml`, flagged by the RAT check the new parent enables by default - Update CI: `push_pr.yml` matrix `[2.1-SNAPSHOT, 2.2-SNAPSHOT]` → `[2.1.2, 2.2.1]`; `weekly.yml` main entries → `2.1-SNAPSHOT`/`2.2-SNAPSHOT` (main no longer builds against Flink 1.x) and moved the `1.20.1` entry to branch `v2.0` - Regenerated the ArchUnit frozen violation store (a rule was renamed upstream) ## Verifying this change This change is a trivial rework / code cleanup without any test coverage. Verified locally: full `mvn verify` passes, including the module's unit and integration test suites (57 unit + 48 IT tests, testcontainers-based). ## Significant changes - [x] Dependencies have been added or upgraded - [ ] Public API has been changed (Public API is any class annotated with `@Public(Evolving)`) - [ ] Serializers have been changed - [ ] New feature has been introduced ## AI Usage Disclosure - [x] This contribution was developed with AI assistance (Claude Code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
