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 v1.0.9 #34

Closed
wants to merge 2 commits into from
Closed

Release v1.0.9 #34

wants to merge 2 commits into from

Conversation

cclauss
Copy link
Contributor

@cclauss cclauss commented Apr 30, 2024

Replaces failed #33

As recommended at #30 (review)

I went back to https://github.com/pytest-dev/nose2pytest/pull/6/files v1.0.9 Nov 17, 2022

I used the last commit of #6 to

git checkout 7918d3a1b788c9d72ec013b7fbb28bdcab875b1f
git switch -c release-v1.0.9
code setup.cfg   # Remove `README.rst` from the `bumpversion.files =` line.
git commit -am"Remove v1.0.9 from README.rst"
bumpversion patch --new-version 1.0.9
git tag v1.0.9
git push

@nicoddemus
Copy link
Member

Unfortunately the conflict will prevent GitHub from running the CI jobs.

IMHO it is not trivial to generate releases for the old versions, because of small issues like this.

Is there a strong need for the old versions to be released to PyPI, or just the latest one is fine? If so I would just release the last version and be done with it.

@cclauss cclauss closed this Apr 30, 2024
@cclauss cclauss deleted the release-v1.0.9 branch April 30, 2024 10:58
@cclauss
Copy link
Contributor Author

cclauss commented Apr 30, 2024

Releasing the old versions is beyond my git foo...

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.

None yet

2 participants