chore(deps): update dependency ops to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ops (changelog)	==2.23.0 -> ==3.1.0

---

Release Notes

canonical/operator (ops)

v3.1.0

Compare Source

Features

• Release automation script (#​1855)
• Add app_name and unit_id attributes to testing.context (#​1920)

Fixes

• If an event ends with _abort(0) tests should behave as if it ended successfully (#​1887)
• If self.app is not actually set avoid a new crash location (#​1897)
• Only add the remote unit for departed and broken relation events, fix ordering (#​1918)
• Add the remote unit to relation.data but not relation.units (#​1925)

Documentation

• Use load_config in the httpbin example charm (#​1852)
• Update HACKING.md with how to bump ops version in Charmcraft profiles (#​1872)
• Change title of docs site (#​1890)
• Use config and action classes in the Kubernetes tutorial (#​1891)
• Reference example charms from K8s tutorial and fix consistency (#​1898)
• Update style guide (#​1720)
• Fix issues in how-to guide for stored state (#​1901)
• Link out to the 12-factor tutorials from the tutorial index page (#​1902)
• Replace broken link in testing explanation (#​1913)
• Expand the storage how-to with content from Juju docs scheduled for removal (#​1915)
• Ops tracing how to (#​1853)
• Add a security explanation doc (#​1904)

Tests

• Replace Python version to 3.10 for observability charm tests (#​1914)

CI

• Use httpbin demo charm for the Charmcraft pack test (#​1895)
• Move TIOBE workflow to self-hosted runners (#​1912)
• Add SBOM generation and secscan workflow (#​1906)
• Build and publish in one step (#​1857)
• Update the name and email when updating the charm pins (#​1924)
• Drop smoke test against 20.04 (#​1923)

v3.0.0

Compare Source

The minimum version of Python for Ops 3.x is 3.10.

Documentation

• Be consistent with recommending self.app and self.unit (#​1856)

CI

• Hotfix, publish job for ops-tracing (#​1865)

v2.23.1: : Add the remote unit to Relation.data, but not Relation.units

Compare Source

This is a small bug-fix release for the 2.x series that addresses issues with the recent feature making relation data available in relation-departed events. Rather than inserting the remote unit into Relation.units, the data is available from Relation.data, without changing Relation.units.

What's Changed

Fixes

• Add the remote unit to Relation.data but not Relation.units in https://github.com/canonical/operator/pull/1928

Documentation

• Be consistent with recommending self.app and self.unit in https://github.com/canonical/operator/pull/1856
• Add notice about ops 2 and ops 3 in https://github.com/canonical/operator/pull/1867
• Update title and edit links for ops 2.23 docs in https://github.com/canonical/operator/pull/1885

CI

• Hotfix, publish job for ops-tracing in https://github.com/canonical/operator/pull/1865

Full Changelog: canonical/operator@2.23.0...2.23.1

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[amandahla]

:: ERROR: Ignored the following versions that require a different python version: 2.11.0 Requires-Python >=3.9; 2.11.0a1 Requires-Python >=3.9; 2.11.0a2 Requires-Python >=3.9; 2.11.0b1 Requires-Python >=3.9; 2.11.0b2 Requires-Python >=3.9; 2.11.1 Requires-Python >=3.9; 2.11.2 Requires-Python >=3.9; 2.11.3 Requires-Python >=3.9; 2.11.4 Requires-Python >=3.9; 2.11.5 Requires-Python >=3.9; 2.11.6 Requires-Python >=3.9; 2.11.7 Requires-Python >=3.9; 3.0.0 Requires-Python >=3.10
  2025-07-02 16:36:27.084 :: 2025-07-02 16:36:26.458 ::    :: ERROR: Could not find a version that satisfies the requirement ops==3.0.0 (from versions: 0.1.0, 0.2.0, 0.2.1, 0.4.2, 0.4.3, 0.4.4, 0.4.5, 0.4.6, 0.4.7, 0.6.0, 0.6.1, 0.7.0, 0.8.0, 0.9.0, 0.10.0, 1.0.0, 1.0.1, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.5.4, 1.5.5, 2.0.0rc2, 2.0.0, 2.1.0, 2.1.1, 2.2.0, 2.3.0, 2.4.0, 2.4.1, 2.5.0, 2.5.1, 2.6.0, 2.7.0, 2.8.0, 2.9.0, 2.10.0, 2.11.0, 2.12.0, 2.13.0, 2.14.0, 2.14.1, 2.15.0, 2.16.0, 2.16.1, 2.17.0, 2.17.1, 2.18.0, 2.18.1, 2.19.0, 2.19.4, 2.20.0, 2.21.0, 2.21.1, 2.22.0, 2.23.0.dev0, 2.23.0)

Indico uses Ubuntu 20.04, python 3.8.2

[github-actions]

Test results for commit 3a6b8c7

Test coverage for 3a6b8c7

Name                       Stmts   Miss Branch BrPart  Cover   Missing
----------------------------------------------------------------------
src/charm.py                 349     12     80      8    95%   404, 418-419, 669, 710-711, 802->818, 804->813, 813->818, 826-827, 866, 899->exit, 937-943
src/database_observer.py      32      0      4      0   100%
src/s3_observer.py            17      0      0      0   100%
src/saml_observer.py          14      0      0      0   100%
src/smtp_observer.py          15      0      0      0   100%
src/state.py                  73      0      8      0   100%
----------------------------------------------------------------------
TOTAL                        500     12     92      8    97%

Static code analysis report

Run started:2025-07-30 08:55:06.131995

Test results:
  No issues identified.

Code scanned:
  Total lines of code: 3122
  Total lines skipped (#nosec): 2
  Total potential issues skipped due to specifically being disabled (e.g., #nosec BXXX): 0

Run metrics:
  Total issues (by severity):
  	Undefined: 0
  	Low: 0
  	Medium: 0
  	High: 0
  Total issues (by confidence):
  	Undefined: 0
  	Low: 0
  	Medium: 0
  	High: 0
Files skipped (0):

[amandahla]

Reference:
https://matrix.to/#/!xdClnUGkurzjxqiQcN:ubuntu.com/$V-gkoOFriBtu-ktNKorjStBwvHs8Fxpgyk2l6D9cS7k?via=ubuntu.com&via=matrix.org&via=fsfe.org

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.