Skip to content

⚠️ CONFLICT! Lineage pull request for: skeleton#89

Merged
jsf9k merged 26 commits intodevelopfrom
lineage/skeleton
Dec 30, 2025
Merged

⚠️ CONFLICT! Lineage pull request for: skeleton#89
jsf9k merged 26 commits intodevelopfrom
lineage/skeleton

Conversation

@cisagovbot
Copy link

@cisagovbot cisagovbot commented Dec 23, 2025

Lineage Pull Request: CONFLICT

Achtung!!!

Lineage has created this pull request to incorporate new changes found in an upstream repository:

Upstream repository: https://github.com/cisagov/skeleton-python-library.git
Remote branch: HEAD

Check the changes in this pull request to ensure they won't cause issues with your project.

The lineage/skeleton branch has one or more unresolved merge conflicts that you must resolve before merging this pull request!

How to resolve the conflicts

  1. Take ownership of this pull request by removing any other assignees.

  2. Clone the repository locally, and reapply the merge:

    git clone git@github.com:cisagov/action-lineage.git action-lineage
    cd action-lineage
    git remote add skeleton https://github.com/cisagov/skeleton-python-library.git
    git remote set-url --push skeleton no_push
    git switch develop
    git switch --create lineage/skeleton --track origin/develop
    git pull skeleton HEAD
    git status
  3. Review the changes displayed by the status command. Fix any conflicts and possibly incorrect auto-merges.

  4. After resolving each of the conflicts, add your changes to the branch, commit, and push your changes:

    git add .pre-commit-config.yaml pyproject.toml src/example/example.py 
    git commit
    git push --force --set-upstream origin lineage/skeleton

    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.

  5. Wait for all the automated tests to pass.

  6. Confirm each item in the "Pre-approval checklist" below.

  7. Remove any of the checklist items that do not apply.

  8. Ensure every remaining checkbox has been checked.

  9. Mark this draft pull request "Ready for review".

✅ Pre-approval checklist

  • ✌️ The conflicts in this pull request have been resolved.
  • All relevant type-of-change labels have been added.
  • All new and existing tests pass.

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

dependabot bot and others added 24 commits November 24, 2025 18:37
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/
…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
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
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
@cisagovbot cisagovbot added the upstream update This issue or pull request pulls in upstream updates label Dec 23, 2025
@github-actions github-actions bot added the dependencies Pull requests that update a dependency file label Dec 23, 2025
@github-actions github-actions bot added 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 labels Dec 23, 2025
@jsf9k jsf9k marked this pull request as ready for review December 30, 2025 15:39
@jsf9k jsf9k enabled auto-merge December 30, 2025 15:39
@jsf9k jsf9k merged commit de224f7 into develop Dec 30, 2025
111 checks passed
@jsf9k jsf9k deleted the lineage/skeleton branch December 30, 2025 18:58
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants