nzw921rx opened a new pull request, #12950:
URL: https://github.com/apache/seatunnel/pull/12950
### Purpose of this pull request
Yes, this is a contribution to Apache SeaTunnel.
Bump the mainline version from `3.0.1-SNAPSHOT` to `3.1.0-SNAPSHOT` and
align the repository references with the new version:
- `pom.xml`: `<revision>` -> `3.1.0-SNAPSHOT`
- `bin/install-plugin.sh` / `install-plugin.cmd`: default connector version
-> `3.1.0`
- `docs/en` and `docs/zh`: download, Docker, Kubernetes, local deployment,
DolphinScheduler and REST API examples -> `3.1.0` / `3.1.0-SNAPSHOT`
- `seatunnel-cli` README and `setup.sh` examples -> `3.1.0`
- `seatunnel-dist` `InstallPluginScriptTest` fixture -> `3.1.0-SNAPSHOT`
- `deploy/kubernetes/seatunnel/Chart.yaml`: chart `version` -> `3.1.0`;
`appVersion` stays `3.0.0` because it is the default image tag and must point
to a published image
- `.github/workflows/upgrade_compatibility.yml` and
`tools/upgrade_compatibility`: baseline release -> `3.0.0`, so the check covers
`3.0.0 -> 3.1.0`; remove the obsolete multiple-distribution fixture
- `seatunnel.shade.version` remains `3.0.0` (separate project)
### Does this PR introduce _any_ user-facing change?
Yes. The development version and the download/install/Docker/Kubernetes
examples now reference `3.1.0`. The Helm chart `appVersion` remains `3.0.0`
until a `3.1.0` image is published. No configuration or API behavior changes.
### How was this patch tested?
- `bash tools/upgrade_compatibility/run_upgrade_compatibility_test.sh` ->
passed
- `./mvnw -q -pl seatunnel-dist spotless:check` -> passed
- `./mvnw -q -o -pl seatunnel-dist -Dtest=InstallPluginScriptTest test` ->
not run: the `3.1.0-SNAPSHOT` module artifacts are not installed in the local
repository for offline resolution
- Maven `verify` was not run
### Check list
* [ ] If any new Jar binary package adding in your PR, please add License
Notice according
[New License
Guide](https://github.com/apache/seatunnel/blob/dev/docs/en/developer/new-license.md)
* [x] If necessary, please update the documentation to describe the new
feature. https://github.com/apache/seatunnel/tree/dev/docs
* [ ] If necessary, please update `incompatible-changes.md` to describe the
incompatibility caused by this PR.
* [ ] If you are contributing the connector code, please check that the
following files are updated:
1. Update
[plugin-mapping.properties](https://github.com/apache/seatunnel/blob/dev/plugin-mapping.properties)
and add new connector information in it
2. Update the pom file of
[seatunnel-dist](https://github.com/apache/seatunnel/blob/dev/seatunnel-dist/pom.xml)
3. Add ci label in
[label-scope-conf](https://github.com/apache/seatunnel/blob/dev/.github/workflows/labeler/label-scope-conf.yml)
4. Add e2e testcase in
[seatunnel-e2e](https://github.com/apache/seatunnel/tree/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/)
5. Update connector
[plugin_config](https://github.com/apache/seatunnel/blob/dev/config/plugin_config)
--
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]
