[dependabot]

Bumps certifi from 2024.8.30 to 2026.10.19.

Commits

• 662df63 Restore unaffected emSign roots (#439) (#440)
• 5cb238c Remove emsign (#437)
• 69494a7 Bump actions/download-artifact from 8.0.1 to 8.0.2 (#436)
• 029c7b0 Bump actions/upload-artifact from 7.0.1 to 7.0.2 (#435)
• 9d0a8f1 Add support for Python 3.15 (#432)
• db472ab Bump pypa/gh-action-pypi-publish from 1.14.1 to 1.14.2 (#431)
• f4bc676 2026.07.22 (#428)
• 4c91f9c Bump actions/setup-python from 6.3.0 to 7.0.0 (#427)
• 01a66c5 Bump actions/checkout from 7.0.0 to 7.0.1 (#426)
• eb355f4 Bump pypa/gh-action-pypi-publish from 1.14.0 to 1.14.1 (#425)
• Additional commits viewable in compare view

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 commands and options

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[greptile-apps]

PR author is in the excluded authors list.

[github-actions]

Deep Review

✅ No critical issues found.

The only changed file is poetry.lock. The certifi bump itself is clean: 2024.8.30 → 2026.10.19, with new hashes and python-versions raised to >=3.7, which is within the project's >= 3.9 floor. The lock was also re-resolved with a newer Poetry (2.1.1 → 2.5.1), which changed several other dependencies beyond certifi. The published package's dependency ranges in pyproject.toml are unchanged, so library users are not affected. The impact is limited to development and CI environments.

🟡 P2 -- recommended

• poetry.lock:556 -- Re-resolving the lock removed the Python ≥3.11 OpenTelemetry branch that commit b4c0b38 added on purpose (opentelemetry-* 1.44.0 and instrumentation/semantic-conventions 0.65b0). Every Python version now locks to 1.41.1 / 0.62b1. As a result, local test runs on 3.11+ no longer cover the newer SDK layout (the MeterProvider._metric_readers move), even though tests/utils.py has a helper written specifically to handle it.
  • Fix: Regenerate the lock with poetry lock so the 1.44.0 / 0.65b0 branch for Python ≥3.11 comes back, then re-apply only the certifi version change.
• poetry.lock:305 -- The grpcio version markers moved: Python 3.11–3.13 now resolves to grpcio 1.83.0 instead of 1.67.1. importlib-metadata and zipp also lost their python_version < "3.11" marker in the main group, so they now install on every Python version. None of these changes is related to certifi.
  • Fix: Fold these into the same lock regeneration as above, so the only transitive changes left are the ones the certifi bump actually needs.

🔵 P3 nitpicks (1)

• poetry.lock:1 -- The lock header now names Poetry 2.5.1 instead of 2.1.1. The constraint strings were also rewritten in the newer syntax (!= exclusions, .dev0), which adds noise to the diff.
  • Fix: Regenerate with the Poetry version the maintainers use, or note the generator upgrade in the PR so the extra churn is expected.

---

Reviewers (1): orchestrator (inline lockfile analysis; no sub-agents were dispatched because the diff only changes a generated lockfile)

Testing gaps:

• CI (unit.yaml, smoke.yaml) only runs on Python 3.10, so dropping the 3.11+ OpenTelemetry 1.44.0 branch from the lock would not show up in any CI result.