build targets ignore lock files
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- build-system, devops, release
Research direction
Start by locating the build targets that run dependency updates and the deployment entry point. Trace when lock files are replaced during beta and production deployments. Done means deployment preserves the locked dependencies, while updating dependencies is available only as an explicit action.
Written by the indexing model from the issue text.
Description
All our build targets automatically run update. This means that we effectively ignore the lock file when deploying our services because the build process just overwrites them with the most recent dependencies.
Given the way we do deployments this actually even means prod and beta could be running completely different versions of the service dependencies.
I'm not sure if there is some legit reason to do this by default in some environments, but suggest we make updating dependencies an explicit action, not the default and definitely don't do it as part of deploy.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 15h 10m
- Merged PRs (30d)
- 12
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.
More from PolicyEngine/policyengine-sim-api
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
PolicyEngine/policyengine-sim-api#674 · 3 comments ·
All issues in PolicyEngine/policyengine-sim-api
Similar issues
-
agent-ready documentation needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
instance instance add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
searxng/searx-instances#939 · 1 comment ·
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100