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: v3.4.0 CHANGELOG and config update #6860

Merged
merged 3 commits into from
Dec 18, 2024
Merged

Conversation

mlavacca
Copy link
Member

What this PR does / why we need it:

CHANGELOG update for v1.4.0.

Which issue this PR fixes:

Part of #6844

Special notes for your reviewer:

PR Readiness Checklist:

Complete these before marking the PR as ready to review:

  • the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

@mlavacca mlavacca force-pushed the prepare-release/3.4.0 branch 3 times, most recently from 6d3468d to 4970492 Compare December 18, 2024 10:34
Copy link
Member

@pmalek pmalek left a comment

Choose a reason for hiding this comment

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

v1.4.0 -> v3.4.0

Copy link

codecov bot commented Dec 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.0%. Comparing base (655e921) to head (9f741a6).
Report is 4 commits behind head on main.

Additional details and impacted files
@@          Coverage Diff          @@
##            main   #6860   +/-   ##
=====================================
  Coverage   77.0%   77.0%           
=====================================
  Files        211     211           
  Lines      25484   25491    +7     
=====================================
+ Hits       19623   19649   +26     
+ Misses      4847    4835   -12     
+ Partials    1014    1007    -7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

CHANGELOG.md Show resolved Hide resolved
@mlavacca mlavacca force-pushed the prepare-release/3.4.0 branch from 4970492 to cd2c2ca Compare December 18, 2024 12:33
@mlavacca mlavacca changed the title chore: v1.4.0 CHANGELOG chore: v1.4.0 CHANGELOG and config update Dec 18, 2024
@mlavacca mlavacca changed the title chore: v1.4.0 CHANGELOG and config update chore: v3.4.0 CHANGELOG and config update Dec 18, 2024
Signed-off-by: Mattia Lavacca <[email protected]>
Signed-off-by: Mattia Lavacca <[email protected]>
@mlavacca mlavacca force-pushed the prepare-release/3.4.0 branch from cd2c2ca to e10fa2f Compare December 18, 2024 12:51
@mlavacca mlavacca marked this pull request as ready for review December 18, 2024 12:56
@mlavacca mlavacca requested a review from a team as a code owner December 18, 2024 12:56
@mlavacca mlavacca requested a review from pmalek December 18, 2024 13:11
CHANGELOG.md Outdated Show resolved Hide resolved
Co-authored-by: Grzegorz Burzyński <[email protected]>
@mlavacca mlavacca merged commit 92a6761 into main Dec 18, 2024
39 checks passed
@mlavacca mlavacca deleted the prepare-release/3.4.0 branch December 18, 2024 14:50
@team-k8s-bot
Copy link
Collaborator

The backport to release/3.4.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release/3.4.x release/3.4.x
# Navigate to the new working tree
cd .worktrees/backport-release/3.4.x
# Create a new branch
git switch --create backport-6860-to-release/3.4.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 92a6761ac1c94ecd202571cbf84de860336664f3
# Push it to GitHub
git push --set-upstream origin backport-6860-to-release/3.4.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release/3.4.x

Then, create a pull request where the base branch is release/3.4.x and the compare/head branch is backport-6860-to-release/3.4.x.

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.

4 participants