Skip to content

Upgrade setup-miniconda to v4 for Node.js compatibility#803

Open
RHammond2 wants to merge 2 commits into
NatLabRockies:mainfrom
RHammond2:fix/ci-conda-setup
Open

Upgrade setup-miniconda to v4 for Node.js compatibility#803
RHammond2 wants to merge 2 commits into
NatLabRockies:mainfrom
RHammond2:fix/ci-conda-setup

Conversation

@RHammond2

Copy link
Copy Markdown
Collaborator

Upgrade CI workflow to use setup-miniconda v4 to avoid Node.js deprecation

This PR bumps the conda-incubator/setup-miniconda action from v3 to v4, which updates the Node.js version from 20.x (deprecated) to 24.x.

Section 1: Type of Contribution

  • Feature Enhancement
    • Framework
    • New Model
    • Updated Model
    • Tools/Utilities
    • Other (please describe):
  • Bug Fix
  • Documentation Update
  • CI Changes
  • Other (please describe):

Section 2: Draft PR Checklist

N/A

Section 3: General PR Checklist

  • PR description thoroughly describes the new feature, bug fix, etc.
  • Added tests for new functionality or bug fixes
  • Tests pass (If not, and this is expected, please elaborate in the Section 6: Test Results)
  • Documentation
    • Docstrings are up-to-date
    • Related docs/ files are up-to-date, or added when necessary
    • Documentation has been rebuilt successfully
    • Examples have been updated (if applicable)
  • CHANGELOG.md
    • At least one complete sentence has been provided to describe the changes made in this PR
    • After the above, a hyperlink has been provided to the PR using the following format:
      "A complete thought. [PR XYZ]((https://github.com/NatLabRockies/H2Integrate/pull/XYZ)", where
      XYZ should be replaced with the actual number.
    • N/A: CI Action changes only, and no version bump required.

Section 4: Related Issues

N/A

Section 5: Impacted Areas of the Software

Section 5.1: New Files

N/A

Section 5.2: Modified Files

  • .github/workflows/ci.yml: setup-miniconda v3 -> v4

Section 6: Additional Supporting Information

When checking the CI cron job, I noticed a significant number of warnings relating to Node.js deprecations. I believe I fixed this in the develop branch with the expectation of a near-term version release, but that has not happened yet, so I am submitting the change directly to main as well.

Section 7: Test Results, if applicable

N/A

Section 8 (Optional): New Model Checklist

N/A

@RHammond2 RHammond2 added the infrastructure Anything relating to CI, project management, or non-code changes label Jul 10, 2026
@RHammond2 RHammond2 requested a review from johnjasa July 10, 2026 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

infrastructure Anything relating to CI, project management, or non-code changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant