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

Bump version to 4.8.0.post1 #347

Merged
merged 1 commit into from
Nov 29, 2023

Conversation

umohnani8
Copy link
Member

Had an issue with the 4.8.0 release on pypi and we can't repush changes with the same version again so need to bump to a minor version to be able to publish on pypi again.

@umohnani8
Copy link
Member Author

@lsm5 @rhatdan PTAL

@lsm5
Copy link
Member

lsm5 commented Nov 28, 2023

is this semver compliant? I fear it would cause issues with rpm builds.

Why not bump to v4.8.1 ?

@lsm5
Copy link
Member

lsm5 commented Nov 28, 2023

cc @jwhonce

Makefile Outdated Show resolved Hide resolved
@lsm5
Copy link
Member

lsm5 commented Nov 28, 2023

hmm, packit jobs are successful and we get rpms of the form: python-podman-4.8.0-1.20231128113321306557.pr347.1.g2ca2e7a. So AFAICT, it ignores the -1 in the upstream version.

I'm fine with this change if we can't do 4.8.1.

@umohnani8
Copy link
Member Author

If packit is not complaining, then I think let's leave it at 4.8.0-1. I messed up the pypi release, my bad - will make sure to be more careful in future.

@lsm5
Copy link
Member

lsm5 commented Nov 28, 2023

@mgorny ping, will this change be ok for gentoo?

@mgorny
Copy link
Contributor

mgorny commented Nov 28, 2023

We could make it work on our end but it's "invalid" in the Python world (unless I'm mistaken, PyPI will translate it to 4.8.0.1). The usual way of doing rereleases is to name them 4.8.0.post1.

@umohnani8 umohnani8 changed the title Bump version to 4.8.0-1 Bump version to 4.8.1 Nov 29, 2023
@lsm5
Copy link
Member

lsm5 commented Nov 29, 2023

We could make it work on our end but it's "invalid" in the Python world (unless I'm mistaken, PyPI will translate it to 4.8.0.1). The usual way of doing rereleases is to name them 4.8.0.post1.

ack thanks for the input @mgorny . We haven't used the .postN scheme in this repo, so I'm not too keen on it atm. We'll go ahead with 4.8.1 as it's simpler and safer packaging wise and shouldn't break anything.

Copy link
Member

@lsm5 lsm5 left a comment

Choose a reason for hiding this comment

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

/lgtm
/hold

Had an issue with the 4.8.0 release on pypi and we can't
repush changes with the same version again so need to bump
to a minor version to be able to publish on pypi again.

Signed-off-by: Urvashi Mohnani <umohnani@redhat.com>
@lsm5 lsm5 changed the title Bump version to 4.8.1 Bump version to 4.8.0.post1 Nov 29, 2023
Copy link
Member

@lsm5 lsm5 left a comment

Choose a reason for hiding this comment

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

/lgtm
/hold

@mgorny you were right after all :) . Thanks for the tip.

@openshift-ci openshift-ci bot added the lgtm label Nov 29, 2023
@lsm5
Copy link
Member

lsm5 commented Nov 29, 2023

/approve

Copy link
Member

@lsm5 lsm5 left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

Copy link
Contributor

openshift-ci bot commented Nov 29, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lsm5, umohnani8

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:

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

@lsm5
Copy link
Member

lsm5 commented Nov 29, 2023

/hold cancel

@openshift-merge-bot openshift-merge-bot bot merged commit 803ea74 into containers:release-4.8 Nov 29, 2023
14 checks passed
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.

3 participants