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 ghcr.io/open-feature/sync-testbed docker tag to v0.5.19 #591

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 29, 2024

This PR contains the following updates:

Package Type Update Change
ghcr.io/open-feature/sync-testbed service patch v0.5.6 -> v0.5.19

Release Notes

open-feature/flagd-testbed (ghcr.io/open-feature/sync-testbed)

v0.5.19

Compare Source

Features
  • add certificates for ssl test and an ssl test image (#​168) (8177dc0)

v0.5.18

Compare Source

Features
  • add yaml file with current version, to easier fetch images corr… (#​169) (ac1263a)

v0.5.17

Compare Source

Features
  • add dedicated gherkin file for events (and grace attempts) (#​164) (22ab80c)

v0.5.16

Compare Source

Features

v0.5.15

Compare Source

Bug Fixes

v0.5.13

Compare Source

Bug Fixes

v0.5.12

Compare Source

Bug Fixes

v0.5.11

Compare Source

Bug Fixes

v0.5.10

Compare Source

Bug Fixes

v0.5.8

Compare Source

Bug Fixes

v0.5.7

Compare Source

Bug Fixes

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 October 29, 2024 18:11
@renovate renovate bot force-pushed the renovate/ghcr.io-open-feature-sync-testbed-0.x branch 2 times, most recently from 3f610be to 181f8ee Compare November 4, 2024 21:05
@renovate renovate bot force-pushed the renovate/ghcr.io-open-feature-sync-testbed-0.x branch from 181f8ee to fe598c6 Compare November 7, 2024 01:54
@renovate renovate bot changed the title chore(deps): update ghcr.io/open-feature/sync-testbed docker tag to v0.5.13 chore(deps): update ghcr.io/open-feature/sync-testbed docker tag to v0.5.15 Dec 2, 2024
@renovate renovate bot force-pushed the renovate/ghcr.io-open-feature-sync-testbed-0.x branch from fe598c6 to 2d08e1c Compare December 2, 2024 19:51
@renovate renovate bot changed the title chore(deps): update ghcr.io/open-feature/sync-testbed docker tag to v0.5.15 chore(deps): update ghcr.io/open-feature/sync-testbed docker tag to v0.5.17 Dec 6, 2024
@renovate renovate bot force-pushed the renovate/ghcr.io-open-feature-sync-testbed-0.x branch from 2d08e1c to 32aa0dc Compare December 6, 2024 10:54
@renovate renovate bot force-pushed the renovate/ghcr.io-open-feature-sync-testbed-0.x branch from 32aa0dc to 4080fd5 Compare December 16, 2024 22:23
@renovate renovate bot changed the title chore(deps): update ghcr.io/open-feature/sync-testbed docker tag to v0.5.17 chore(deps): update ghcr.io/open-feature/sync-testbed docker tag to v0.5.18 Dec 16, 2024
@renovate renovate bot changed the title chore(deps): update ghcr.io/open-feature/sync-testbed docker tag to v0.5.18 chore(deps): update ghcr.io/open-feature/sync-testbed docker tag to v0.5.19 Dec 17, 2024
@renovate renovate bot force-pushed the renovate/ghcr.io-open-feature-sync-testbed-0.x branch from 4080fd5 to 9f711e7 Compare December 17, 2024 23:29
@renovate renovate bot force-pushed the renovate/ghcr.io-open-feature-sync-testbed-0.x branch from 9f711e7 to e5bd26c Compare December 19, 2024 17:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants