Skip to content

Pin and automate doing isolated bumps of hub image dependencies' major versions #3565

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

Merged
merged 3 commits into from
Nov 1, 2024

Conversation

consideRatio
Copy link
Member

@consideRatio consideRatio commented Oct 31, 2024

I had to rename and isolate requirements.in to unfrozen/requirements.txt because it was the only way for me to ensure dependabot worked as wanted.

I also had to add some arguments in ci/refreeze specifying files.


Dependabot function verified in a fork, and ci/refreeze function verified manually. No remnants of requirements.in found when searching.

image

Copy link
Member

@minrk minrk left a comment

Choose a reason for hiding this comment

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

Nice and makes sense! I'm not sure every bump of these will actually mean a breaking change for the chart, but I think it will be good to be prompted to make a choice when they come in.

@@ -15,3 +15,15 @@ updates:
interval: monthly
time: "05:00"
timezone: Etc/UTC
- package-ecosystem: pip
directory: /images/hub/unfrozen
labels: [breaking]
Copy link
Member

Choose a reason for hiding this comment

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

nice isolation!

jupyterhub-idle-culler==1.*

# Other optional dependencies for additional features
pymysql==1.* # mysql
Copy link
Member

Choose a reason for hiding this comment

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

fwiw, I wouldn't consider a bump of any of these to be a breaking change, but that's not a big deal. Perhaps they shouldn't be pinned?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah hmmm I agree, they aren't meant to be a breaking change for the user.

It could be relevant to be given a chance to read the changelog before merging though. I'm fine with removing pins or retaining them, but I agree they are reasonably not to be listed as breaking in the end.

I think for all major bumps here, some may not be breaking in the end, so generally a manual consideration about breaking label or not this is probably needed.

avoids PRs labeling them as 'breaking'

Co-authored-by: Erik Sundell <erik.i.sundell@gmail.com>
@minrk minrk merged commit fabaae9 into jupyterhub:main Nov 1, 2024
15 checks passed
consideRatio pushed a commit to jupyterhub/helm-chart that referenced this pull request Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants