version 1.2.0 release

[JessicaS11]

No description provided.

[github-actions]

👈 Launch a binder notebook on this branch for commit c85baec

I will automatically update this comment whenever this PR is modified

[codecov]

Codecov Report

Attention: Patch coverage is 58.33333% with 25 lines in your changes missing coverage. Please review.

Project coverage is 66.05%. Comparing base (102405b) to head (c85baec).
Report is 44 commits behind head on main.

Files with missing lines	Patch %	Lines
icepyx/core/variables.py	0.00%	17 Missing ⚠️
icepyx/core/spatial.py	40.00%	0 Missing and 3 partials ⚠️
icepyx/quest/dataset_scripts/argo.py	71.42%	0 Missing and 2 partials ⚠️
icepyx/core/is2ref.py	0.00%	1 Missing ⚠️
icepyx/core/query.py	0.00%	1 Missing ⚠️
icepyx/core/visualization.py	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #561      +/-   ##
==========================================
- Coverage   66.27%   66.05%   -0.23%     
==========================================
  Files          36       36              
  Lines        3072     3049      -23     
  Branches      537      537              
==========================================
- Hits         2036     2014      -22     
+ Misses        948      947       -1     
  Partials       88       88              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[JessicaS11]

My only mild concern is #562.

[weiji14]

My only mild concern is #562.

So technically, the Publish to PyPI action should be ok when triggered on release because it will be pushing a 1.2.0 tag that doesn't exist on TestPyPI yet 🤞

[weiji14]

🚀

[JessicaS11]

So technically, the Publish to PyPI action should be ok when triggered on release because it will be pushing a 1.2.0 tag that doesn't exist on TestPyPI yet 🤞

Glad to have this confirmed (that's what I thought). I just have a penchant for ending up with the cases where what should happen isn't what happens... Thanks!

[weiji14]

So technically, the Publish to PyPI action should be ok when triggered on release because it will be pushing a 1.2.0 tag that doesn't exist on TestPyPI yet 🤞

Glad to have this confirmed (that's what I thought). I just have a penchant for ending up with the cases where what should happen isn't what happens... Thanks!

Yes, Murphy's law tends to come up during releases (and you and I both know how many times release dramas have happened before), so always good to check!