Pinned dependency warning
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Under an hour
- Newbie friendliness
- 22/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github-actions, python
- Domain
- ci-cd, documentation
Research direction
The question is whether the docs dependencies in requirements.txt should be pinned to exact versions, to silence the CI warning seen in the screenshot. Start with requirements.txt and the new CI workflow that installs it, and check whether maintainers have already decided. The thread has two comments and no answer for 335 days, so ask for a decision before writing any change. Done means a recorded decision, and if pinning is chosen, a requirements.txt with exact versions that the workflow installs cleanly.
Written by the indexing model from the issue text.
Description
We added a CI check to make sure new releases of the bot won't break the docs anymore. When creating the workflow we got the following warning because we install the dependencies of the docs in requirements.txt. At the moment the version of the dependencies are not pinned is this something we should do or can we ignore this warning?
- Dominant language
- Python
- Stars
- 14
- Forks
- 54
- Avg merge
- 11h 2m
- Merged PRs (30d)
- 41
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from EESSI/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
add "talks" sectionOpen
Difficulty 2/5 Half a day Newbie friendliness 62/100
Maintainers usually reply within 1 day
Similar issues
-
ChatBedrockConverse changes the keys of JSON tool results to camelCase (`order_id` becomes `orderId`)Possibly taken @geyazheng claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
langchain-ai/langchain-aws#1469 ·
Maintainers usually reply within 1 day
-
b4b usability
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
fix(schedule): align list_tasks since cursor filter boundary from strict > to >=Possibly taken @bfs2021 claimed this today. Openagent-ready bug p2 schedule
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
allenporter/supernote#540 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
frazane/scoringrules#164 ·
Maintainers usually reply within 1 day
-
The docs build fails: ecc's live inventory dropped the ecc.ecc names btclib's pinned ecc usesPossibly taken @fametrano claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
btclib-org/btclib#2968 ·
Maintainers usually reply within 1 day