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 <2.11 - autoclosed #310

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 27, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ops (changelog) <2.5 -> <2.11 age adoption passing confidence

Release Notes

canonical/operator (ops)

v2.10.0

Compare Source

  • Added support for Pebble Notices (PebbleCustomNoticeEvent, get_notices, and so on)
  • Added Relation.active, and excluded inactive relations from Model.relations
  • Added full support for charm metadata v2 (in particular, extended ContainerMeta,
    and various info links in CharmMeta)

v2.9.0

Compare Source

  • Added log target support to ops.pebble layers and plans
  • Added Harness.run_action(), testing.ActionOutput, and testing.ActionFailed

v2.8.0

Compare Source

  • Added Unit.reboot() and `Harness.reboot_count``
  • Added RelationMeta.optional
  • The type of a Handle's key was expanded from str to str|None
  • Narrowed types of app and unit in relation events to exclude None where applicable

v2.7.0

Compare Source

  • Added Unit.set_ports()
  • Type checks now allow comparing a JujuVersion to a str
  • Renamed OpenPort to Port (OpenPort remains as an alias)

v2.6.0: : Harness.handle_exec, Harness.add_relation improvements, and more

Compare Source

This release has two significant improvements to testing.Harness:

  • Add Harness.handle_exec to allow charm tests to simulate Container.exec calls (Pebble one-shot commands) and provide expected output. Thanks @​weiiwang01 for the design and implementation (PR 993).
  • Simplify adding relation units and relation data by adding app_data and unit_data parameters to Harness.add_relation. Previously, charm tests would have to call add_relation followed by add_relation_unit and update_relation_data -- now only a single add_relation call is required. Implemented in PR 994.

In addition, several small improvements and fixes are included:

See all changes from 2.5.0 to 2.6.0.

v2.5.1: : Fix str vs bytes issue with testing push()

Compare Source

This is a patch fix on top of 2.5.0 to fix #​990: "TypeError: write() argument must be str, not bytes" in Container.push under Harness.

v2.5.0: : Collect-status, Harness.get_filesystem_root, Pebble service context

Compare Source

This release includes three significant additions:

  1. Multi-status: An initial version of the much-discussed "multi-status" handling in the form of the new collect_app_status and collect_unit_status events. This is useful for letting the framework automatically evaluate application (or unit) status from various components of the charm. We'll be documenting this properly soon, but in the meantime, read the API reference docs on CollectStatusEvent. PR #​954.
  2. Harness.get_filesystem_root: Overhauling the Harness's test filesystem from an in-memory filesystem to use a temp directory on the real filesystem; use Harness.get_filesystem_root to get the temp filesystem directory for a specific container. This makes testing container filesystem operations significantly easier and allows tests to use the regular Python file APIs to interact with it. Thanks @​weiiwang01 for his efforts on this in #​960.
  3. Service context: Added support for Pebble's new "service context" feature, to allow you to exec commands in the context of a specified service (where context means environment variables, working directory, and user/group). PR #​957.

Other notable changes:

In addition, the following developers made their first contribution:

We also made several other minor improvements to type annotations and a few other tweaks. See the full changelog: canonical/operator@2.4.1...2.5.0


Configuration

📅 Schedule: Branch creation - "on the 2nd and 4th day instance on sunday" (UTC), 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested a review from a team as a code owner August 27, 2023 00:10
@renovate renovate bot force-pushed the renovate-ops-2.x branch from 2e6033e to 016cbb5 Compare August 31, 2023 01:28
@renovate renovate bot changed the title chore(deps): update dependency ops to <2.6 chore(deps): update dependency ops to <2.7 Aug 31, 2023
@renovate renovate bot requested a review from a team as a code owner August 31, 2023 01:28
@renovate renovate bot force-pushed the renovate-ops-2.x branch from 016cbb5 to d3e36b4 Compare September 4, 2023 16:09
@renovate renovate bot force-pushed the renovate-ops-2.x branch from d3e36b4 to d6b7961 Compare September 6, 2023 11:27
@renovate renovate bot force-pushed the renovate-ops-2.x branch from d6b7961 to 8ff9f89 Compare September 7, 2023 13:07
@renovate renovate bot force-pushed the renovate-ops-2.x branch from 8ff9f89 to f435e25 Compare September 8, 2023 19:26
@renovate renovate bot force-pushed the renovate-ops-2.x branch from 3b40fc7 to 0a81499 Compare November 22, 2023 07:35
@renovate renovate bot force-pushed the renovate-ops-2.x branch from 0a81499 to cf0bf5b Compare November 22, 2023 10:57
@renovate renovate bot changed the title chore(deps): update dependency ops to <2.9 chore(deps): update dependency ops to <2.10 Nov 30, 2023
@renovate renovate bot force-pushed the renovate-ops-2.x branch from cf0bf5b to cffc569 Compare November 30, 2023 01:30
@renovate renovate bot force-pushed the renovate-ops-2.x branch from cffc569 to 27b0306 Compare December 1, 2023 16:26
@renovate renovate bot force-pushed the renovate-ops-2.x branch from 27b0306 to 7a2bdb3 Compare December 11, 2023 16:41
@renovate renovate bot force-pushed the renovate-ops-2.x branch from 7a2bdb3 to aa4bf5d Compare January 18, 2024 13:38
@renovate renovate bot force-pushed the renovate-ops-2.x branch from aa4bf5d to 25400e4 Compare January 22, 2024 08:33
@renovate renovate bot force-pushed the renovate-ops-2.x branch from 25400e4 to cac7fb5 Compare January 31, 2024 03:10
@renovate renovate bot changed the title chore(deps): update dependency ops to <2.10 chore(deps): update dependency ops to <2.11 Jan 31, 2024
@renovate renovate bot force-pushed the renovate-ops-2.x branch from cac7fb5 to 357a09b Compare February 9, 2024 11:15
@renovate renovate bot changed the title chore(deps): update dependency ops to <2.11 chore(deps): update dependency ops to <2.11 - autoclosed Feb 17, 2024
@renovate renovate bot closed this Feb 17, 2024
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.

0 participants