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.

Sign up for GitHub

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

Jump to bottom

Using juju 3.5 for (charm) integration tests #1826

Merged
merged 4 commits into from
Aug 5, 2024
Merged

Using juju 3.5 for (charm) integration tests #1826

merged 4 commits into from
Aug 5, 2024

Conversation

cbartz
Copy link
Collaborator

@cbartz cbartz commented Jul 24, 2024 •
edited
Loading

Applicable spec: n/a

Overview

Use juju 3.5 in integration tests.

Rationale

We use juju 3.5 in production, so test it.

Module Changes

n/a

Checklist

  • The contributing guide was applied
  • The documentation is generated using src-docs
  • The PR is tagged with appropriate label (urgent, trivial, complex)
  • Version has been incremented on pyproject.toml and rockcraft.yaml

@cbartz cbartz added the trivial label Aug 5, 2024
@cbartz cbartz marked this pull request as ready for review August 5, 2024 07:42
@cbartz cbartz requested a review from a team as a code owner August 5, 2024 07:42
@cbartz cbartz merged commit b92efd7 into main Aug 5, 2024
9 checks passed
@cbartz cbartz deleted the chore/use-juju-3.5 branch August 5, 2024 09:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@merkata merkata merkata approved these changes

@yanksyoon yanksyoon yanksyoon approved these changes

Assignees
No one assigned
Labels
trivial
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@cbartz @merkata @yanksyoon