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

debump jupyterhub to 3.2.1 #5696

Closed

Conversation

shaneknapp
Copy link
Contributor

@shaneknapp shaneknapp commented Apr 24, 2024

DO NOT MERGE! this PR is for review and debugging only... i will deploy this locally w/hubploy

testing out jupyterhub and nbgitpuller issues in conjunction w/#5693

i set the chart version to 3.2.1, ran charpress --push and snagged the image name and tags from there. it didn't actually push anything as those images were already present in the repo. :)

@ryanlovett @balajialg

@shaneknapp
Copy link
Contributor Author

shaneknapp commented Apr 24, 2024

ok, i went to the artifact registry in the GCP console and found the last version we built (back in dec 2023)... got the tag from there and manually deployed to staging.dev-r.d.b.e and we're good!

jovyan@hub-7567558c9c-9qjxw:/srv/jupyterhub$ pip list | grep jupyterhub
jupyterhub                       4.0.2

@balajialg you can copy these lines manually in to the dev-r config/staging.yaml and when you merge to staging you'll be running the last 4.0.x version of jupyterhub that we had before bumping to 4.1.5.

@balajialg
Copy link
Contributor

@shaneknapp Sounds great! Thanks a lot

@shaneknapp shaneknapp closed this Apr 25, 2024
@shaneknapp shaneknapp deleted the debump-dev-r-hub branch April 25, 2024 00:36
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.

2 participants