update conda envs used in testing
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 5
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
the conda envs we use in the github actions are now very old compared to latest versions of the software
we should update them and make any required code changes to go with them. This will be done initially with using iris 2.2 as current (so consistent with what we have now) and the current default as next.
Then we will need to repeat this process periodically to keep it up to data
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the GitHub Actions workflows and conda environment definitions used for testing. Check how the current Iris 2.2 environment and the current default environment are represented, then identify any code changes required by the updates. Done means both environments are refreshed, tests pass, and the project remains compatible with them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100