[RELEASE] 2025.3.1

[dcmcand]

Release Checklist

Release details

Scheduled release date - 2025-03-17

Release captain responsible - dcmcand

Milestone: https://github.com/nebari-dev/nebari/milestone/61

Starting point - a new release is out

• Create this issue to track and discuss the upcoming release.
• Use the previous release issue for any final release-specific discussions, then close.
  • This can be a good time to debrief and discuss improvements to the release process.

Looking forward - planning

• Create milestone for next release (if it doesn't already exist) and link it back here.
• Triage bugs to determine what be should included in the release and add it to the milestone.
• What new features, if any, will be included in the release and add it to the milestone.
  • This will be, in large part, determined by the roadmap.
  • Is there a focus for this release (i.e. UX/UI, stabilization, etc.)?

Pre-release process

• Decide on a date for the release.
  • What outstanding issues need to be addressed?
  • Has documentation been updated appropriately?
  • Are there any breaking changes that should be highlighted?
  • Are there any upstream releases we are waiting on?
  • Do we need to update the dask versions in the nebari-dask?
  • Will there be an accompanying blog post?
• Prepare for the release.
  • Update the nebari upgrade for this release
    • Add upgrade messaging including deprecation warnings, version specific warnings and so on.
  • Optionally, announce a merge freeze.
  • Release Candidate (RC) cycle.
    • Is this a hotfix?
      • Create a new branch off of the last version tag.
        • Use this branch to cut the pre-release and the "official" release.
      • git cherry-pick the commits that should be included.
    • Cut RC via GHA release workflow (w/ "This is a pre-release" checked).
    • Perform end-to-end testing. Use the Testing Checklist template.
      • For minor releases, relying on the end-to-end integration tests might suffice.
    • End-user validation.
      • If possible, pull in volunteers to help test.
      • (Repeat steps if necessary)
  • Update RELEASE.md notes.

Cut the official release

If there were changes to the following packages, handle their releases before cutting a new release for Nebari

• Cut PyPI release for nebari-workflow-controller
• Cut PyPI release for argo-jupyter-scheduler

These steps must be actioned in the order they appear in this checklist.

• Tag, build and push docker images
• Update and cut release for nebari-dask meta package on Conda-Forge.
• Update CURRENT_RELEASE (and any other tags) in the constants.py
• Cut PyPI release via GHA release workflow.
  • Avoid appending v to tag.
    • Copy release notes from RELEASE.md.
• Merge automated release PR for nebari on Conda-Forge.
• Merge release branch into main

[viniciusdc]

Hey @dcmcand One thing to note, the order for cutting the final docker images tag and publishing a new release of nebari-dask is incorrect, the package release needs to be done first then the docker images final build. This is one of the action items from #2960

[Adam-D-Lewis]

I also relaxed some pin requirements in this PR:
"google-auth>=2.31.0,<3.0.0",
"pydantic>=2.9.2,<3.0.0",
"rich>=13.5.1,<14",

If the PR is merged, you may need to update the conda-forge recipe.