Skip to content

Conversation

@cclauss
Copy link
Contributor

@cclauss cclauss commented Nov 18, 2025

https://github.com/django-haystack/pysolr/actions/runs/19463495336 shows a warning annotation:

Analyze
1 issue was detected with this workflow: git checkout HEAD^2 is no longer necessary. Please remove this step as Code Scanning recommends analyzing the merge commit for best results.

https://github.com/django-haystack/pysolr/actions/runs/19463495336 shows a warning annotation:
>  Analyze
1 issue was detected with this workflow: git checkout HEAD^2 is no longer necessary. Please remove this step as Code Scanning recommends analyzing the merge commit for best results.
@DhavalGojiya
Copy link
Contributor

Also, see this workflow: https://github.com/django-haystack/pysolr/blob/master/.github/workflows/pypi-release.yml

Do we actually use it in the project to publish releases?

@acdha
Copy link
Collaborator

acdha commented Nov 18, 2025

Also, see this workflow: https://github.com/django-haystack/pysolr/blob/master/.github/workflows/pypi-release.yml

Do we actually use it in the project to publish releases?

As of the last few releases, yes. It allowed us to stop managing API keys and reuse the work the PyPA has been doing for trusted package signatures.

@acdha acdha merged commit d5aa41f into master Nov 18, 2025
9 checks passed
@acdha acdha deleted the CodeQL-git-checkout-HEAD2-is-no-longer-necessary branch November 18, 2025 12:12
@cclauss
Copy link
Contributor Author

cclauss commented Nov 18, 2025

Yes, we do use the pypi-release workflow to release to PyPI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants