-
Notifications
You must be signed in to change notification settings - Fork 152
Comparing changes
Open a pull request
base repository: mozilla-releng/balrog
base: v3.66
head repository: mozilla-releng/balrog
compare: main
- 13 commits
- 21 files changed
- 5 contributors
Commits on Jan 23, 2025
-
Configuration menu - View commit details
-
Copy full SHA for a472fc2 - Browse repository at this point
Copy the full SHA a472fc2View commit details -
Configuration menu - View commit details
-
Copy full SHA for 94db2fb - Browse repository at this point
Copy the full SHA 94db2fbView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2b581f8 - Browse repository at this point
Copy the full SHA 2b581f8View commit details -
Configuration menu - View commit details
-
Copy full SHA for 80cf55f - Browse repository at this point
Copy the full SHA 80cf55fView commit details
Commits on Jan 24, 2025
-
fix(docker): Switch to
pip install
and remove repoze-lru workaround (……#3281) - Replaces `python setup.py install` with `pip install` in the Docker image - Removes the hard-coded `repoze.lru` (`-` to `.`) workaround in `pin-helper` The issue arose because `pip-compile` switches `.` to `-` when following [PEP-0503](https://peps.python.org/pep-0503/#normalized-names) package name normalization rules. While `pip` seamlessly handles the aliased name (installing the package with `.`), `setuptools` does not manage the mismatch well. By moving to `pip install`, we avoid the naming conflict entirely and prevent future mishaps.
Configuration menu - View commit details
-
Copy full SHA for 19dbbfb - Browse repository at this point
Copy the full SHA 19dbbfbView commit details -
Add a
pr-complete
task that we can require before merging PRs (#3282)* Add a `pr-complete` task that we can require before merging PRs The task does nothing, always succeeds but depends on all test tasks passing. * Add ui tasks to `pr-complete` dependencies
Configuration menu - View commit details
-
Copy full SHA for b593d46 - Browse repository at this point
Copy the full SHA b593d46View commit details
Commits on Feb 6, 2025
-
chore: Update tox to version 4 and repin dependencies (#3283)
* chore: Update tox to version 4 * chore: Update dockerfile to remove some tox warnings
Configuration menu - View commit details
-
Copy full SHA for d198acc - Browse repository at this point
Copy the full SHA d198accView commit details -
chore: update python dependencies (#3306)
* chore: update python dependencies * Fix formatting for what black now expects
Configuration menu - View commit details
-
Copy full SHA for 4f74d24 - Browse repository at this point
Copy the full SHA 4f74d24View commit details
Commits on Feb 12, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 9ce9fee - Browse repository at this point
Copy the full SHA 9ce9feeView commit details
Commits on Feb 13, 2025
-
fix: put dockerhub credentials in ~/.docker/config.json (#3314)
The new token I just added is a format that isn't supported in .dockercfg
Configuration menu - View commit details
-
Copy full SHA for 8cf91fc - Browse repository at this point
Copy the full SHA 8cf91fcView commit details
Commits on Feb 25, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 06ff1a9 - Browse repository at this point
Copy the full SHA 06ff1a9View commit details -
Configuration menu - View commit details
-
Copy full SHA for a05909d - Browse repository at this point
Copy the full SHA a05909dView commit details -
Configuration menu - View commit details
-
Copy full SHA for ce198a6 - Browse repository at this point
Copy the full SHA ce198a6View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v3.66...main