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

chore: kubefed version to v0.11.1 #1545

Merged
merged 4 commits into from
Jan 27, 2025
Merged

Conversation

SandhyaRavi2403
Copy link
Contributor

What type of PR is this?
chore

What this PR does/ why we need it:
bump kubefed version to v0.11.1

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?:


Checklist

  • If a chart is changed, the chart version is correctly incremented.
  • The commit message explains the changes and why are needed.
  • The code builds and passes lint/style checks locally.
  • The relevant subset of integration tests pass locally.
  • The core changes are covered by tests.
  • The documentation is updated where needed.

@SandhyaRavi2403 SandhyaRavi2403 self-assigned this Jan 27, 2025
@SandhyaRavi2403 SandhyaRavi2403 requested review from a team as code owners January 27, 2025 12:07
@SandhyaRavi2403 SandhyaRavi2403 changed the title chore: bump kubefed version to v0.11.1 chore: kubefed version to v0.11.1 Jan 27, 2025
@mhrabovcin mhrabovcin merged commit 3f0e83c into master Jan 27, 2025
5 checks passed
@mhrabovcin mhrabovcin deleted the sandy/kubefed-update-v0.11.1 branch January 27, 2025 14:05
github-actions bot pushed a commit that referenced this pull request Jan 27, 2025
…on to v0.11.1 * Update stable/kommander-cert-federation/templates/cert-federation.yaml Co-authored-by: Martin Hrabovcin <[email protected]> * chore: update image in values.yaml * chore: update the version --------- Co-authored-by: Martin Hrabovcin <[email protected]>
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.

2 participants