leonardBang opened a new pull request, #4569:
URL: https://github.com/apache/flink-cdc/pull/4569

   ## What is the purpose of this pull request?
   
   The `release-3.7` branch has been created, so the master branch should move 
to the next development version, `3.8-SNAPSHOT`.
   
   This PR also updates the documentation deployment configuration so that the 
`release-3.7` documentation is built from the corresponding release branch 
instead of being aliased from master.
   
   Since Flink CDC 3.7.0 has not been officially released yet, the `stable` 
documentation alias remains on `release-3.6`.
   
   ## Brief change log
   
   - Update the Maven project version from `3.7-SNAPSHOT` to `3.8-SNAPSHOT`.
   - Update the default Flink CDC version in the Dockerfile to `3.8-SNAPSHOT`.
   - Update the master documentation version to `3.8-SNAPSHOT`.
   - Add the `release-3.7` documentation to the previous-version list.
   - Build documentation for `release-3.7` instead of `release-3.5`.
   - Update the master documentation alias from `release-3.7` to `release-3.8`.
   - Keep the `stable` documentation alias on `release-3.6` until 3.7.0 is 
officially released.
   
   ---
   
   ## Verifying this change
   
   This change is a build and documentation configuration update without 
additional test coverage.
   
   The change was verified as follows:
   
   - Ran `git diff --check`.
   - Parsed `docs/config.toml` successfully.
   - Parsed `.github/workflows/build_docs.yml` successfully.
   - Verified the Maven project version resolves to `3.8-SNAPSHOT`.
   - Verified that build and configuration files no longer reference 
`3.7-SNAPSHOT`.
   
   ## Documentation
   
   - Does this pull request introduce a new feature? no
   - If yes, how is the feature documented? not applicable
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (OpenAI Codex)
   
   Generated-by: OpenAI Codex


-- 
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]

Reply via email to