-
Notifications
You must be signed in to change notification settings - Fork 84
⚠️ CONFLICT! Lineage pull request for: skeleton #264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps [actions/checkout](https://github.com/actions/checkout) from 5 to 6. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v5...v6) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
This is necessary for cisagov/skeleton-ansible-role#243 (Fedora 43 support). See here for more details about this release: https://github.com/ansible/ansible-lint/releases/tag/v25.11.1
types-setuptools is not necessary here since we are not interfacing with setuptools directly. Also update the accompanying comment to refer to pyproject.toml instead of setup.py.
I occasionally need to run python -m build to debug an issue with a wheel. Twine seems good to include too, since folks may want to upload to Test PyPI or PyPI.
Python 3.10 is currently the oldest non-EOL version of Python, so we want to apply all rules that apply to this version or later. See here for more details: https://www.gyford.com/phil/writing/2025/08/26/how-to-use-pyupgrade/
ansible-core<2.17.7 suffers from GHSA-99w6-3xph-cx78.
…pgrade Add `--py310-plus` argument to `pyupgrade` `pre-commit` hook
…-pre-commit-hook Upgrade the `ansible-lint` `pre-commit` hook
…s/checkout-6 Bump actions/checkout from 5 to 6
Pin `ansible-core` to 2.17.7 or later
61.0.0 was the first version of setuptools to offer a full-fledged backend that uses pyproject.toml for metadata configuration (in compliance with PEP 621): https://setuptools.pypa.io/en/stable/history.html#v61-0-0
77.0.0 was the first version of setuptools to support license expressions (in compliance with PEP 639): https://setuptools.pypa.io/en/stable/history.html#v77-0-0
…ev-dependency Remove an unnecessary dev dependency
…cies Add `build` and `twine` as `dev` dependencies
Lineage pull request for: skeleton
…setuptools Add lower bound for `setuptools`
Bumps [actions/download-artifact](https://github.com/actions/download-artifact) from 6 to 7. - [Release notes](https://github.com/actions/download-artifact/releases) - [Commits](actions/download-artifact@v6...v7) --- updated-dependencies: - dependency-name: actions/download-artifact dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
…s/download-artifact-7 Bump actions/download-artifact from 6 to 7
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 5 to 6. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@v5...v6) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
…s/upload-artifact-6 Bump actions/upload-artifact from 5 to 6
This project must support Python 3.7, so we cannot include upgrades past that point. See here for more details: https://www.gyford.com/phil/writing/2025/08/26/how-to-use-pyupgrade/
dee2683 to
ca3fd9d
Compare
68.0.0 is the most recent version of setuptools to support Python 3.7, and 75.3.2 is the most recent version to support Python 3.8.
2d9c6ff to
920a681
Compare
jsf9k
approved these changes
Dec 30, 2025
dav3r
approved these changes
Dec 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
dependencies
Pull requests that update a dependency file
github-actions
Pull requests that update GitHub Actions code
python
Pull requests that update Python code
test
This issue or pull request adds or otherwise modifies test code
upstream update
This issue or pull request pulls in upstream updates
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Lineage Pull Request: CONFLICT
Lineage has created this pull request to incorporate new changes found in an upstream repository:
Upstream repository:
https://github.com/cisagov/skeleton-python-library.gitRemote branch:
HEADCheck the changes in this pull request to ensure they won't cause issues with your project.
The
lineage/skeletonbranch has one or more unresolved merge conflicts that you must resolve before merging this pull request!How to resolve the conflicts
Take ownership of this pull request by removing any other assignees.
Clone the repository locally, and reapply the merge:
Review the changes displayed by the
statuscommand. Fix any conflicts and possibly incorrect auto-merges.After resolving each of the conflicts,
addyour changes to the branch,commit, andpushyour changes:Note that you may append to the default merge commit message that git creates for you, but please do not delete the existing content. It provides useful information about the merge that is being performed.
Wait for all the automated tests to pass.
Confirm each item in the "Pre-approval checklist" below.
Remove any of the checklist items that do not apply.
Ensure every remaining checkbox has been checked.
Mark this draft pull request "Ready for review".
✅ Pre-approval checklist
Note
You are seeing this because one of this repository's maintainers has configured Lineage to open pull requests.
For more information:
🛠 Lineage configurations for this project are stored in
.github/lineage.yml📚 Read more about Lineage