Skip to content
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

chore(deps): update dependency ops to v2.17.0 #229

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 27, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ops (changelog) ==2.14.0 -> ==2.17.0 age adoption passing confidence

Release Notes

canonical/operator (ops)

v2.17.0

Compare Source

Features

  • Optionally install Scenario with ops[testing] and expose the names in ops.testing (#​1381)
  • Change ops.main() so that you don't need to type: ignore it (#​1345)
  • Expand the secret ID out to the full URI when only given the ID (#​1358)
  • Add a JujuVersion property for Pebble log forwarding to Loki (#​1370)
  • Pre-emptively raise InvalidStatusError instead of waiting for Juju:
    • Make it an error to call CollectStatusEvent.add_status with error or unknown (#​1386)
    • Document and validate settable status values in _ModelBackend.set_status (#​1354)

Fixes

  • Fix type of StatusBase subclasses by calling StatusBase.register in __init_subclass__ (#​1383)
  • Secret.set_info and Secret.set_content can be called in the same hook (#​1373)

Documentation

  • Add top-level intro and module-level intros (#​1320)
  • Update the links to the Pebble docs (#​1362)
  • Note about repeatedly setting secret value in Juju 3.6 (#​1366)
  • config-changed is triggered by Juju trust (#​1357)
  • Typo on CharmBase inheritance example by @​theofpa (#​1349)
  • Docs: move Pebble to a separate page (#​1392)

Continuous Integration

  • Periodically run the unit tests of all GitHub-hosted published charms (#​1365)
  • Update the TIOBE reporting for the changes in coverage calculation (#​1367)
  • Spell-check the code as part of linting (#​1388)
  • Run the smoke tests on a schedule (#​1387)

Testing

  • Fix tests that leaked environment variables (#​1385)

Refactoring

  • Move the content of ops.testing to ops._private.harness (#​1369)
  • Keep the unittest.mock names in the 'mock' namespace (#​1379)
  • Deprecate StatusBase.register decorator (#​1384)

Chores

  • Note Juju version on legacy workaround (#​1355)
  • Re-enable test now that Pebble directory permissions are fixed (#​1363)
  • Generate warnings for events that will be removed in Juju 4.0 (#​1374)

v2.16.1: Don't have Harness alter os.environ

Compare Source

This is a small bug-fix release to address a regression in ops 2.16.0 where creating a Harness object would add a JUJU_VERSION to os.environ.

Fixes

Full Changelog: canonical/operator@2.16.0...2.16.1

v2.16.0

Compare Source

Features

Refactor

Fixes

Documentation

Tests

CI

v2.15.0

Compare Source

Features

  • Add support for Pebble check-failed and check-recovered events (#​1281)

Fixes

  • Pass secret data to Juju via files, rather than as command-line values (#​1290) fixing CVE-2024-41129
  • Include checks and log targets when merging layers in ops.testing (#​1268)

Documentation

  • Clarify distinction between maintenance and waiting status (#​1148)

CI

  • Bump the Go version to match Pebble (#​1285)
  • Run ruff format over charm pin update code (#​1278)
  • Bump certifi from 2024.2.2 to 2024.7.4 in /docs (#​1282)
  • Update charm pins (#​1269)

v2.14.1

Compare Source

Fixes

  • Add connect timeout for exec websockets to avoid hanging (#​1247)
  • Adjust Harness secret behaviour to align with Juju (#​1248)

Tests

  • Fix TypeError when running test.pebble_cli (#​1245)
  • Properly clean up after running setup_root_logging in test_log (#​1259)
  • Verify that defer() is not usable on stop,remove,secret-expired,secret-rotate (#​1233)

Documentation

  • Fix HACKING.md link on PyPI, and internal links (#​1261, #​1236)
  • Add a section to HACKING.md on PR titles (commit messages to main) (#​1252)
  • Add release step to update pinned charm tests (#​1213)
  • Add a security policy (#​1266)

CI

  • Only run tests once on push to PR (#​1242)
  • Validate PR title against conventional commit rules in (#​1262)
  • Only update ops, not all dependencies, in charm tests in (#​1275)
  • Add artefact attestation (#​1267)

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.

@renovate renovate bot requested a review from a team as a code owner June 27, 2024 07:17
Copy link
Contributor

@merkata merkata left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nrobinaubertin
Copy link
Contributor

Blocked by canonical/charm-logdump-action#9

@renovate renovate bot changed the title chore(deps): update dependency ops to v2.14.1 chore(deps): update dependency ops to v2.15.0 Jul 22, 2024
@renovate renovate bot changed the title chore(deps): update dependency ops to v2.15.0 chore(deps): update dependency ops to v2.16.0 Aug 29, 2024
@renovate renovate bot changed the title chore(deps): update dependency ops to v2.16.0 chore(deps): update dependency ops to v2.16.1 Sep 5, 2024
@renovate renovate bot changed the title chore(deps): update dependency ops to v2.16.1 chore(deps): update dependency ops to v2.17.0 Sep 26, 2024
Copy link
Contributor Author

renovate bot commented Nov 5, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Copy link
Contributor

github-actions bot commented Nov 5, 2024

Test coverage for c2ff9ff

Name                Stmts   Miss Branch BrPart  Cover   Missing
---------------------------------------------------------------
src/charm.py          557     35    174     34    91%   162, 204-207, 299->302, 414, 473->477, 627, 658, 664, 681-685, 715, 750-751, 811, 820, 924->937, 936, 938, 943-944, 1004, 1024, 1031, 1121, 1130, 1142, 1163, 1172, 1191, 1195, 1224, 1265, 1397, 1419, 1426->1428, 1471->exit, 1483, 1493, 1531
src/cos.py             20      0      0      0   100%
src/exceptions.py      16      1      2      1    89%   41
src/state.py           33      0      2      0   100%
src/types_.py          15      0      0      0   100%
---------------------------------------------------------------
TOTAL                 641     36    178     35    91%

Static code analysis report

Run started:2024-11-05 10:29:46.053124

Test results:
  No issues identified.

Code scanned:
  Total lines of code: 4647
  Total lines skipped (#nosec): 1
  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):

@cbartz
Copy link
Contributor

cbartz commented Nov 8, 2024

@yanksyoon Can you take over here please (it seems there have been some security vulnerabilities detected by trivy)?

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

Successfully merging this pull request may close these issues.

4 participants