Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Prod build is not guaranteed to be the same as beta

Open
#178 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

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.

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)

Dominant language
Python
Stars
1
Forks
1
Avg merge
15h 10m
Merged PRs (30d)
12

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PolicyEngine/policyengine-sim-api

All issues in PolicyEngine/policyengine-sim-api

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.