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

[release-1.33.2] Bump to v1.33.2 #5189

Merged

Conversation

TomSweeneyRedHat
Copy link
Member

As the title says.

Rather than trying to insert the version bump to v1.33.2 into the main branch, I've created a branch that includes the changes to Docker and Buildkit that should reduce the noted bloat. This does not include changes added for upstream c/{project} bumps, XDG_RUNTIME changes, nor FreeBSD.

This approach was used after discussions in my prior PR #5188

This PR simply bumps the version appropriately in the branch so that we can create a release to vendor into Podman v4.8.

[NO NEW TESTS NEEDED]

What type of PR is this?

/kind api-change
/kind bug
/kind cleanup
/kind deprecation
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake
/kind other

What this PR does / why we need it:

How to verify it

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

None

As the title says.

Rather than trying to insert the version bump to v1.33.2
into the main branch, I've created a branch that includes
the changes to Docker and Buildkit that should reduce
the noted bloat.  This does not include changes added for
upstream c/{project} bumps, XDG_RUNTIME changes, nor
FreeBSD.

This approach was used after discussions in my prior PR

This PR simiply bumps the version appropriately in the
branch so that we can create a release to vendor into
Podman v4.8.

[NO NEW TESTS NEEDED]

Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>
Copy link
Collaborator

@flouthoc flouthoc left a comment

Choose a reason for hiding this comment

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

LGTM should we rename branch for release-1.33 when this gets merged ?

@flouthoc
Copy link
Collaborator

/lgtm
/approve

Copy link
Contributor

openshift-ci bot commented Nov 26, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: flouthoc, TomSweeneyRedHat

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [TomSweeneyRedHat,flouthoc]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 8be6786 into containers:release-1.33.2 Nov 26, 2023
36 checks passed
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants