-
-
Notifications
You must be signed in to change notification settings - Fork 73
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: adamchainz/django-upgrade
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 1.24.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: adamchainz/django-upgrade
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 1.25.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 15 commits
- 25 files changed
- 6 contributors
Commits on Mar 30, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 85c06a2 - Browse repository at this point
Copy the full SHA 85c06a2View commit details
Commits on Apr 11, 2025
-
[pre-commit.ci] pre-commit autoupdate (#550)
<!--pre-commit.ci start--> updates: - [github.com/PyCQA/flake8: 7.1.2 → 7.2.0](PyCQA/flake8@7.1.2...7.2.0) <!--pre-commit.ci end--> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 32afbb7 - Browse repository at this point
Copy the full SHA 32afbb7View commit details
Commits on Apr 24, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 7676c59 - Browse repository at this point
Copy the full SHA 7676c59View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6cdb93d - Browse repository at this point
Copy the full SHA 6cdb93dView commit details -
Configuration menu - View commit details
-
Copy full SHA for c9fc05e - Browse repository at this point
Copy the full SHA c9fc05eView commit details
Commits on Apr 26, 2025
-
Configuration menu - View commit details
-
Copy full SHA for ecbdbe6 - Browse repository at this point
Copy the full SHA ecbdbe6View commit details
Commits on Apr 27, 2025
-
Configuration menu - View commit details
-
Copy full SHA for c219e4b - Browse repository at this point
Copy the full SHA c219e4bView commit details
Commits on May 5, 2025
-
Bump astral-sh/setup-uv from 5 to 6 in the github-actions group (#560)
Bumps the github-actions group with 1 update: [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv). Updates `astral-sh/setup-uv` from 5 to 6 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/astral-sh/setup-uv/releases">astral-sh/setup-uv's releases</a>.</em></p> <blockquote> <h2>v6.0.0 🌈 activate-environment and working-directory</h2> <h2>Changes</h2> <p>This version contains some breaking changes which have been gathering up for a while. Lets dive into them:</p> <ul> <li><a href="https://github.com/astral-sh/setup-uv/blob/HEAD/#activate-environment">Activate environment</a></li> <li><a href="https://github.com/astral-sh/setup-uv/blob/HEAD/#working-directory">Working Directory</a></li> <li><a href="https://github.com/astral-sh/setup-uv/blob/HEAD/#default-cache-dependency-glob">Default <code>cache-dependency-glob</code></a></li> <li><a href="https://github.com/astral-sh/setup-uv/blob/HEAD/#use-default-cache-dir-on-self-hosted-runners">Use default cache dir on self hosted runners</a></li> </ul> <h3>Activate environment</h3> <p>In previous versions using the input <code>python-version</code> automatically activated a venv at the repository root. This led to some unwanted side-effects, was sometimes unexpected and not flexible enough.</p> <p>The venv activation is now explicitly controlled with the new input <code>activate-environment</code> (false by default):</p> <pre lang="yaml"><code>- name: Install the latest version of uv and activate the environment uses: astral-sh/setup-uv@v6 with: activate-environment: true - run: uv pip install pip </code></pre> <p>The venv gets created by the <a href="https://docs.astral.sh/uv/pip/environments/"><code>uv venv</code></a> command so the python version is controlled by the <code>python-version</code> input or the files <code>pyproject.toml</code>, <code>uv.toml</code>, <code>.python-version</code> in the <code>working-directory</code>.</p> <h3>Working Directory</h3> <p>The new input <code>working-directory</code> controls where we look for <code>pyproject.toml</code>, <code>uv.toml</code> and <code>.python-version</code> files which are used to determine the version of uv and python to install.</p> <p>It can also be used to control where the venv gets created.</p> <pre lang="yaml"><code>- name: Install uv based on the config files in the working-directory uses: astral-sh/setup-uv@v6 with: working-directory: my/subproject/dir </code></pre> <blockquote> <p>[!CAUTION]</p> <p>The inputs <code>pyproject-file</code> and <code>uv-file</code> have been removed.</p> </blockquote> <h3>Default <code>cache-dependency-glob</code></h3> <p><a href="https://github.com/ssbarnea"><code>@ssbarnea</code></a> found out that the default <code>cache-dependency-glob</code> was not suitable for a lot of users.</p> <p>The old default</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/astral-sh/setup-uv/commit/6b9c6063abd6010835644d4c2e1bef4cf5cd0fca"><code>6b9c606</code></a> Bump dependencies (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/389">#389</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/ef6bcdff59f18584d3ff2d6733fe1ffb9b7545c1"><code>ef6bcdf</code></a> Fix default cache dependency glob (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/388">#388</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/9a311713f4acad0acceb25fb016307e47c3887b6"><code>9a31171</code></a> chore: update known checksums for 0.6.17 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/384">#384</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/c7f87aa956e4c323abf06d5dec078e358f6b4d04"><code>c7f87aa</code></a> bump to v6 in README (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/382">#382</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/aadfaf08d64f83cdd98eea14fdab8eb08f73656c"><code>aadfaf0</code></a> Change default cache-dependency-glob (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/352">#352</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/a0f9da6273a171f2d94cce2036eaf5a07fefa23c"><code>a0f9da6</code></a> No default UV_CACHE_DIR on selfhosted runners (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/380">#380</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/ec4c6916287cf1471f9f803d79ef6a0a04520e81"><code>ec4c691</code></a> new inputs activate-environment and working-directory (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/381">#381</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/aa1290542ebcd3b6932d825ed2b40807f82b2fdd"><code>aa12905</code></a> chore: update known checksums for 0.6.16 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/378">#378</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/fcaddda076a8158a712b6d64986baf606c446694"><code>fcaddda</code></a> chore: update known checksums for 0.6.15 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/377">#377</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/fb3a0a97fac846cb3395265a3087ab94ad3ca2a0"><code>fb3a0a9</code></a> log info on venv activation (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/375">#375</a>)</li> <li>See full diff in <a href="https://github.com/astral-sh/setup-uv/compare/v5...v6">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for b936cf3 - Browse repository at this point
Copy the full SHA b936cf3View commit details
Commits on May 9, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 6ac0d43 - Browse repository at this point
Copy the full SHA 6ac0d43View commit details
Commits on May 11, 2025
-
Add support for class-based settings files in USE_L10N fixer (#549)
Partially Implements #548. Co-authored-by: Gav O'Connor <gavin.oconnor@zoodigital.com>
Configuration menu - View commit details
-
Copy full SHA for d1c0838 - Browse repository at this point
Copy the full SHA d1c0838View commit details -
Add tests to PASSWORD_RESET fixer to support class-based settings (#551)
Fixer already supported class-based settings, so I just added some unittests to cover this scenario. Partially implements #548
Configuration menu - View commit details
-
Copy full SHA for 539ad05 - Browse repository at this point
Copy the full SHA 539ad05View commit details -
Configuration menu - View commit details
-
Copy full SHA for 149f093 - Browse repository at this point
Copy the full SHA 149f093View commit details -
Configuration menu - View commit details
-
Copy full SHA for 605e55d - Browse repository at this point
Copy the full SHA 605e55dView commit details
Commits on May 12, 2025
-
Configuration menu - View commit details
-
Copy full SHA for ef1f9c6 - Browse repository at this point
Copy the full SHA ef1f9c6View commit details
Commits on May 13, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 779b1ca - Browse repository at this point
Copy the full SHA 779b1caView commit details
Loading
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 1.24.0...1.25.0