8000 Release new version of testcontainers-gcp by barendatnicolab · Pull Request #404 · testcontainers/testcontainers-python · GitHub
[go: up one dir, main page]
Skip to content

Release new version of testcontainers-gcp #404

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.

Sign up for GitHub

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

Jump to bottom
Closed
barendatnicolab wants to merge 1 commit into from
Closed

Release new version of testcontainers-gcp #404

barendatnicolab wants to merge 1 commit into from

Conversation

@barendatnicolab
Copy link
@barendatnicolab barendatnicolab commented Dec 7, 2023

For contest, see #403

Current version on PyPI (0.0.1rc1) is not in sync with branch main. This PR will bump the version and as such that version will hold the changes from this commit: 934c8d8

Not sure what we need to do to actually publish this to PyPI?

@barendatnicolab
Release new version of testcontainers-gcp
151a5d4 
No code changes have been made, but current `main` is ahead of PyPI.
See  testcontainers#403
@markConklin
Copy link
markConklin commented Dec 21, 2023

Gently Bumping this. Thank you.

@alexanderankin
Copy link
Member
alexanderankin commented Dec 21, 2023

I think this depends on Till or Sergei responding with regard to #405 - as currently no other folks have the ability to publish to pypi for this project

@alexanderankin
Copy link
Member
alexanderankin commented Jan 15, 2024

so, unfortunately, we still have not heard from Till, so we are thinking of doing something like #408 to bring all the code back together into one pypi package. and then this would be on the fast track for #405 i think.

@barendatnicolab
Copy link
Author
barendatnicolab commented Jan 22, 2024

Thanks for (trying) to revamp the release cycle @alexanderankin. If there's anything I can do, let me know. For now I've temporarily solved this by publishing a fix to our internal PYPI, but would still love to see it fixed.

@alexanderankin
Copy link
Member
alexanderankin commented Jan 23, 2024 •
edited
Loading

thanks @barendatnicolab

i've published a new version 4.0.0-rc2, which theoretically contains the code which should be published to fix this ticket. I'm still fixing the doctests and various other build stuff, progress on poetry-refactor (issue 408) and later, poetry-refactor-changes-to-publish branches respectively. I guess either testing this rc version or helping with the doctests both helps? (doctests seem fixed)

@totallyzen
Copy link
Contributor
totallyzen commented Feb 29, 2024

hey, please follow #418 for more info

@totallyzen totallyzen closed this Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@tillahoffmann tillahoffmann Awaiting requested review from tillahoffmann

Assignees

No one assigned

Labels

👀 requires attention

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@barendatnicolab @markConklin @alexanderankin @totallyzen
0