Remove lower bound on xeus-zmq version environment-dev.yml

[mcbarton]

Description

Please include a summary of changes, motivation and context for this PR.

Conda will automatically pick the most recent release of xeus-zmq it can. Therefore the lower bound is not necessary in the yml file. We just need to make sure we don't pick a version 4 release when it happens in case we are not compatible with it.

Fixes # (issue)

Type of change

Please tick all options which are relevant.

• Bug fix
• New feature
• Added/removed dependencies
• Required documentation updates

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.54%. Comparing base (ca8c42e) to head (058a44b).
⚠️ Report is 105 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #272   +/-   ##
=======================================
  Coverage   80.54%   80.54%           
=======================================
  Files          19       19           
  Lines         956      956           
  Branches       88       88           
=======================================
  Hits          770      770           
  Misses        186      186           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[anutosh491]

Hmmm xeus 5 needs minimum xeus-zmq 3, not sure this should be changed. Xeus 5 and above won't be compatible with anything less than 3 so this looks just fine to me

[mcbarton]

Hmmm xeus 5 needs minimum xeus-zmq 3, not sure this should be changed. Xeus 5 and above won't be compatible with anything less than 3 so this looks just fine to me

Just a point that it's not explicitly needed to state a minimum version of 3 in the yml file, because conda will pick up the latest version it can (which will be greater than 3). This is evident by the ci passing. You just need to make sure it doesn't pick a version 4 of the package, given you may not be compatible (the reason to keep the upper bound).

[anutosh491]

Cool, you're not wrong (I just like keeping stuff consistent with the feedstock which maintains >3<4) let's take is in.