Upgrade setup-miniconda to v4 for Node.js compatibility#803
Open
RHammond2 wants to merge 2 commits into
Open
Conversation
This reverts commit bc6d71c.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrade CI workflow to use
setup-minicondav4 to avoid Node.js deprecationThis PR bumps the
conda-incubator/setup-minicondaaction from v3 to v4, which updates the Node.js version from 20.x (deprecated) to 24.x.Section 1: Type of Contribution
Section 2: Draft PR Checklist
N/A
Section 3: General PR Checklist
docs/files are up-to-date, or added when necessaryCHANGELOG.md"A complete thought. [PR XYZ]((https://github.com/NatLabRockies/H2Integrate/pull/XYZ)", where
XYZshould be replaced with the actual number.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-minicondav3 -> v4Section 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