Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MySQL 9.0 and MariaDB 11.4 are released #1610

Merged
merged 1 commit into from
Jul 19, 2024
Merged

Conversation

shogo82148
Copy link
Contributor

@shogo82148 shogo82148 commented Jul 18, 2024

Description

update MySQL and MariaDB versions for testing.

  • Add MySQL 9.0, MySQL 8.4 (LTS) and MariaDB 11.4 (LTS)
  • Remove MySQL 8.3 and MariaDB 11.3. they end their life.

Checklist

  • Code compiles correctly
  • Created tests which fail without the change (if possible)
  • All tests passing
  • Extended the README / documentation, if necessary
  • Added myself / the copyright holder to the AUTHORS file

Summary by CodeRabbit

  • Chores
    • Updated MySQL and MariaDB versions used in workflows, including the addition of new versions and marking certain versions as LTS (Long-Term Support).

MySQL 8.3 and MariaDB 11.3 end their life.
Copy link

coderabbitai bot commented Jul 18, 2024

Walkthrough

The recent updates to the .github/workflows/test.yml file primarily focus on updating the versions of MySQL and MariaDB used in the workflows. This includes adding new versions and marking some as Long-Term Support (LTS). These changes ensure the workflows leverage recent and stable database versions, improving reliability and compatibility.

Changes

File Change Summary
.github/workflows/test.yml Updated MySQL versions to include '8.4' and '9.0'. Updated MariaDB versions, marking '11.4', '11.2', and '10.5' as LTS, and included '11.3', '11.1', and '10.6' without the LTS designation.

Poem

In workflows deep within our code,
New versions now will lighten the load.
MySQL and MariaDB in line,
LTS stamps, oh so fine.
Our tests will run with greater might,
Ensuring everything works just right.
Cheers to futures shining bright! ✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3484db1 and ab0a7d7.

Files selected for processing (1)
  • .github/workflows/test.yml (1 hunks)
Additional comments not posted (5)
.github/workflows/test.yml (5)

44-49: Verify compatibility with MariaDB 11.4 (LTS), 11.2, 11.1, 10.11 (LTS), 10.6 (LTS), and 10.5 (LTS).

Ensure that the codebase is compatible with these MariaDB versions, as they might introduce new features or deprecate old ones.

Verification successful

No compatibility issues found with MariaDB 11.4 (LTS), 11.2, 11.1, 10.11 (LTS), 10.6 (LTS), and 10.5 (LTS).

The codebase does not contain any version-specific code that would cause compatibility issues with the newly added MariaDB versions.

  • packets.go: General reference to MariaDB client/server protocol.
  • driver_test.go: Commented-out code related to MariaDB.
  • auth.go: General reference to a MariaDB GitHub repository.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify compatibility with MariaDB 11.4 (LTS), 11.2, 11.1, 10.11 (LTS), 10.6 (LTS), and 10.5 (LTS).

# Test: Search for MariaDB version-specific code. Expect: No issues with new versions.
rg --type go 'mariadb' -A 5

Length of output: 795


Line range hint 70-77:
Verify setup-mysql action usage.

Ensure the setup-mysql action correctly uses the matrix and there are no issues with the MySQL setup.


Line range hint 50-58:
Verify matrix generation logic.

Ensure the matrix generation logic correctly includes all necessary versions and there are no issues with the generated matrix.

Verification successful

Let's extract and inspect the matrix generation logic from the YAML file using shell utilities.


Let's adjust the script to extract a broader range of lines to capture the complete matrix generation logic.


Let's adjust the script to extract lines 30-70 to ensure we capture the complete matrix generation logic.


Matrix generation logic verified.

The matrix generation logic correctly includes all necessary versions of Go and MySQL/MariaDB. The matrix is constructed with the latest Go version (1.22) and all specified MySQL/MariaDB versions. Additionally, compatibility checks for older Go versions (1.21 and 1.20) are included with the latest MySQL version (9.0).

  • The os field includes ubuntu-latest, macos-latest, and windows-latest.
  • The go field includes 1.22.
  • The mysql field includes all specified MySQL/MariaDB versions.
  • The includes field correctly pairs older Go versions with the latest MySQL version.

No issues found with the matrix generation logic.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify matrix generation logic.

# Test: Run the matrix generation logic. Expect: Correct matrix output.
cat .github/workflows/test.yml | python -c "
import json
import os
go = ['1.22', '1.21', '1.20']
mysql = ['9.0', '8.4', '8.0', '5.7', 'mariadb-11.4', 'mariadb-11.2', 'mariadb-11.1', 'mariadb-10.11', 'mariadb-10.6', 'mariadb-10.5']
includes = []
for v in go[1:]:
    includes.append({'os': 'ubuntu-latest', 'go': v, 'mysql': mysql[0]})
matrix = {'os': ['ubuntu-latest', 'macos-latest', 'windows-latest'], 'go': [go[0]], 'mysql': mysql, 'include': includes}
output = json.dumps(matrix, separators=(',', ':'))
print(output)
"

Length of output: 754


Script:

#!/bin/bash
# Extract lines 37-52 from .github/workflows/test.yml to inspect the matrix generation logic
sed -n '37,52p' .github/workflows/test.yml

Length of output: 435


Script:

#!/bin/bash
# Extract lines 30-60 from .github/workflows/test.yml to ensure we capture the complete matrix generation logic
sed -n '30,60p' .github/workflows/test.yml

Length of output: 966


Script:

#!/bin/bash
# Extract lines 30-70 from .github/workflows/test.yml to ensure we capture the complete matrix generation logic
sed -n '30,70p' .github/workflows/test.yml

Length of output: 1276


Line range hint 78-88:
Verify test steps.

Ensure the test steps correctly use the matrix and there are no issues with the tests.

Verification successful

Let's modify the shell script to search for the test steps without filtering by file type and include more context lines to ensure we capture the complete steps.


Let's modify the shell script to search for all run commands in the YAML files to gather more context about the test steps.


Let's create a new script that uses fd to find all YAML files and then uses rg to search for run: commands within those files.


Let's create a script to display the contents of the .github/workflows/test.yml file to manually inspect the test steps.


Verify test steps.

The test steps correctly use the matrix and there are no issues with the tests.

  • The go test command is present and configured to run with appropriate flags.
  • The matrix configuration is correctly set up to test different versions of Go and MySQL/MariaDB.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify test steps.

# Test: Check the test steps. Expect: No issues with the tests.
rg --type yaml 'run: go test' -A 5

Length of output: 185


Script:

#!/bin/bash
# Description: Verify test steps.

# Test: Check the test steps. Expect: No issues with the tests.
rg 'run: go test' -A 10

Length of output: 25


Script:

#!/bin/bash
# Description: Verify test steps.

# Test: Check all run commands in YAML files. Expect: No issues with the tests.
rg 'run:' -A 10 --type yaml

Length of output: 176


Script:

#!/bin/bash
# Description: Verify test steps.

# Find all YAML files and search for run commands within them.
fd -e yml -e yaml -x rg 'run:' -A 10 {}

Length of output: 41


Script:

#!/bin/bash
# Display the contents of the .github/workflows/test.yml file to inspect the test steps.
cat .github/workflows/test.yml

Length of output: 3249


40-41: Verify compatibility with MySQL 9.0 and 8.4 (LTS).

Ensure that the codebase is compatible with MySQL 9.0 and 8.4 (LTS), as these versions might introduce new features or deprecate old ones.

Verification successful

Verify compatibility with MySQL 9.0 and 8.4 (LTS).

The codebase does not contain any version-specific conditions or features that would prevent compatibility with MySQL 9.0 and 8.4 (LTS). The MySQL versions are set in the GitHub Actions workflow matrix, and the tests executed by the workflow will ensure compatibility.

  • .github/workflows/test.yml: MySQL version set in the matrix.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify compatibility with MySQL 9.0 and 8.4 (LTS).

# Test: Search for MySQL version-specific code. Expect: No issues with new versions.
rg --type go 'mysql' -A 5

Length of output: 54637


Script:

#!/bin/bash
# Description: Search for MySQL version-specific conditions or features.

# Search for version-specific conditions in Go files.
rg --type go 'mysql.*version' -A 5

# Search for version-specific conditions in YAML files.
rg --type yaml 'mysql.*version' -A 5

Length of output: 224


Script:

#!/bin/bash
# Description: Search for MySQL version-specific conditions or features with debug mode enabled.

# Search for version-specific conditions in Go files with debug mode.
rg --type go 'mysql.*version' -A 5 --debug

# Search for version-specific conditions in YAML files with debug mode.
rg --type yaml 'mysql.*version' -A 5 --debug

# Search for version-specific conditions in all files.
rg 'mysql.*version' -A 5 --debug

Length of output: 26811


Script:

#!/bin/bash
# Description: Search for MySQL version-specific conditions or features, including hidden files and directories.

# Search for version-specific conditions in Go files, including hidden files.
rg --type go 'mysql.*version' -A 5 --hidden

# Search for version-specific conditions in YAML files, including hidden files.
rg --type yaml 'mysql.*version' -A 5 --hidden

# Search for version-specific conditions in all files, including hidden files.
rg 'mysql.*version' -A 5 --hidden

Length of output: 1996

@coveralls
Copy link

Coverage Status

coverage: 82.446%. remained the same
when pulling ab0a7d7 on bump-mysql-for-testing
into 3484db1 on master.

@shogo82148 shogo82148 requested a review from a team July 18, 2024 16:41
@shogo82148 shogo82148 merged commit f6a18cf into master Jul 19, 2024
73 checks passed
@shogo82148 shogo82148 deleted the bump-mysql-for-testing branch July 19, 2024 04:20
methane pushed a commit to methane/mysql that referenced this pull request Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants