PolicyEngine / PolicyEngine/policyengine-sim-api
Prod build is not guaranteed to be the same as beta
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 10h 29m
- Merged PRs (30d)
- 7
Description
We're not effectively using the lock file to ensure the beta and prod build are identical. This means that if a dependency changes at the wrong time the prod build for a deploy could pick up a different version from the beta build.
This is relatively limited because they build in parallel, but it shouldn't work this way.
Scope of this task is to enforce the lock file and implement mechanisms to update dependencies on a cadence (I.e. maybe we update dependency automatically once a week)
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
No files, tests, or entry points are named. Start by locating the dependency lock file and the beta/prod build configuration, then trace how each build installs dependencies. Done means both builds use the same locked dependencies and dependency updates occur on an explicit cadence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100