Skip to content

chore(deps): update dependency providers/flagd/test-harness to v1.4.0 #1147

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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 8, 2025

This PR contains the following updates:

Package Update Change
providers/flagd/test-harness minor v1.3.3 -> v1.4.0

Release Notes

open-feature/test-harness (providers/flagd/test-harness)

v1.4.0

Compare Source

✨ New Features
  • utilize docker image functionality also for file provider (#​211) (93ec8ef)
🧹 Chore

Configuration

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

🚦 Automerge: Enabled.

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 January 8, 2025 17:41
@renovate renovate bot added the renovate label Jan 8, 2025
@renovate renovate bot enabled auto-merge (squash) January 8, 2025 17:41
@renovate renovate bot force-pushed the renovate/providers-flagd-test-harness-1.x branch 12 times, most recently from 17506d8 to 8716641 Compare January 15, 2025 22:10
@aepfli
Copy link
Member

aepfli commented Jan 15, 2025

Superseded by #1115

@renovate renovate bot force-pushed the renovate/providers-flagd-test-harness-1.x branch 5 times, most recently from bf0a9a4 to dc176de Compare January 18, 2025 20:16
@renovate renovate bot changed the title chore(deps): update dependency providers/flagd/test-harness to v1.3.0 chore(deps): update dependency providers/flagd/test-harness to v1.3.2 Jan 20, 2025
@renovate renovate bot force-pushed the renovate/providers-flagd-test-harness-1.x branch from 5e4e80e to 3fa9156 Compare January 21, 2025 10:39
@renovate renovate bot changed the title chore(deps): update dependency providers/flagd/test-harness to v1.3.2 chore(deps): update dependency providers/flagd/test-harness to v1.3.3 Jan 21, 2025
@renovate renovate bot force-pushed the renovate/providers-flagd-test-harness-1.x branch 10 times, most recently from 0d76b5b to ef0b891 Compare January 28, 2025 20:32
@renovate renovate bot changed the title chore(deps): update dependency providers/flagd/test-harness to v1.3.3 chore(deps): update dependency providers/flagd/test-harness to v1.4.0 Jan 28, 2025
@renovate renovate bot force-pushed the renovate/providers-flagd-test-harness-1.x branch 9 times, most recently from 6e0907b to 05c033b Compare February 3, 2025 22:02
@renovate renovate bot force-pushed the renovate/providers-flagd-test-harness-1.x branch from 05c033b to 2eb20c5 Compare February 6, 2025 08:52
@renovate renovate bot force-pushed the renovate/providers-flagd-test-harness-1.x branch from ee79e31 to 090ee90 Compare February 7, 2025 10:36
@aepfli aepfli closed this Feb 7, 2025
auto-merge was automatically disabled February 7, 2025 10:36

Pull request was closed

Copy link
Contributor Author

renovate bot commented Feb 7, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v1.4.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

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

@renovate renovate bot deleted the renovate/providers-flagd-test-harness-1.x branch February 7, 2025 10:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants