Skip to content

chore: Drop support for unsupported packages conform SPEC 0 - #3363

Closed
github-actions[bot] wants to merge 3 commits into
mainfrom
update-spec0-dependencies-31051826559
Closed

github-actions[bot] wants to merge 3 commits into
mainfrom
update-spec0-dependencies-31051826559

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown

This PR was created automatically

@github-actions
github-actions Bot requested a review from namurphy as a code owner August 5, 2026 22:12
@codecov

codecov Bot commented Aug 5, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.39%. Comparing base (85a2448) to head (7703633).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3363      +/-   ##
==========================================
+ Coverage   94.63%   95.39%   +0.76%     
==========================================
  Files         109      109              
  Lines        9956     9956              
  Branches     1511     1511              
==========================================
+ Hits         9422     9498      +76     
+ Misses        332      262      -70     
+ Partials      202      196       -6     

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@github-actions github-actions Bot added requirements Related to updating requirements packaging Related to packaging or distribution labels Aug 5, 2026
@namurphy

namurphy commented Aug 5, 2026 •

Copy link
Copy Markdown
Member

This was an automated pull request to run scientific-python/spec0-action via the workflow defined in .github/workflows/update-spec0.yml.

See also #3362.

Comment thread pyproject.toml
"tqdm>=4.66.6",
"wrapt>=1.15",
"xarray>=2024.5",
"xarray>=2024.10",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I ran this manually on 2026-08-05, so I expected that this would have been xarray>=2024.9 instead of xarray>=2024.10 to include all minor versions released in the last 24 months. Is it doing this for the upcoming quarter? 🤔

@namurphy

namurphy commented Aug 5, 2026

Copy link
Copy Markdown
Member

Closing this in favor of an earlier pull request, #3345.

Overall, this action looks quite helpful since it removes the need to manually look up the SPEC 0 drop schedule. It's still necessary to manually run pre-commit for pyproject-fmt and uv lock.

We'll still need to review the changes to make sure that we're not dropping anything too early. For example, I'd like to keep supporting numpy>=1.26 for one more release since there have been a few packages in the heliopythoniverse that took a while to support it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

packaging Related to packaging or distribution requirements Related to updating requirements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant