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

tests: use mysql-k8s from 8.0/stable instead of 8.0/edge #243

Merged
merged 1 commit into from
Jun 20, 2024

Conversation

DnPlas
Copy link
Contributor

@DnPlas DnPlas commented Jun 19, 2024

In 8.0/edge a strict was introduced, making this charm impossible to deploy with a juju version == 3.5.{0,1}. Since this version is the one we use in our CI, we have to pin mysql-k8s to its stable version as it does not have these restrictions.

In 8.0/edge a strict  was introduced, making this charm impossible to deploy with
a juju version == 3.5.{0,1}. Since this version is the one we use in our CI, we have to pin
mysql-k8s to its stable version as it does not have these restrictions.
@DnPlas DnPlas requested a review from a team as a code owner June 19, 2024 17:28
@DnPlas DnPlas merged commit 9d1c50e into main Jun 20, 2024
8 checks passed
@DnPlas DnPlas deleted the KF-5567-use-myqsl-stable branch June 20, 2024 12:26
DnPlas added a commit that referenced this pull request Jun 27, 2024
In 8.0/edge a strict  was introduced, making this charm impossible to deploy with
a juju version == 3.5.{0,1}. Since this version is the one we use in our CI, we have to pin
mysql-k8s to its stable version as it does not have these restrictions.
DnPlas added a commit that referenced this pull request Jul 1, 2024
In 8.0/edge a strict  was introduced, making this charm impossible to deploy with
a juju version == 3.5.{0,1}. Since this version is the one we use in our CI, we have to pin
mysql-k8s to its stable version as it does not have these restrictions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants