Skip to content

Update dependency promptfoo to ^0.122.0 - #556

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/promptfoo-0.x
Open

Update dependency promptfoo to ^0.122.0#556
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/promptfoo-0.x

Conversation

@renovate

@renovate renovate Bot commented Aug 7, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
promptfoo (source) ^0.121.0 → ^0.122.0 age confidence

Release Notes

promptfoo/promptfoo (promptfoo)

v0.122.0

Compare Source

⚠ BREAKING CHANGES
Bug Fixes
Miscellaneous Chores

v0.121.20

Compare Source

Features
Bug Fixes

v0.121.19

Compare Source

Features
Bug Fixes

Configuration

📅 Schedule: (in timezone Europe/London)

  • Branch creation
    • "before 10am on friday"
  • Automerge
    • At any time (no schedule defined)

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

♻ Rebasing: Whenever PR becomes conflicted, 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 added dependencies Renovatebot and dependabot updates frontend javascript Pull requests that update javascript code labels Aug 7, 2026
@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown

Caution

[High Risk] Singleton target group replacements will leave the load balancers with no healthy backends

The change replaces both load balancer target group attachments and the EC2 instances behind them. api-207c90ee-tg currently has exactly one healthy instance target, i-0bf4039822e01f430, and txn-feed-terraform-example currently has exactly one healthy IP target, 10.0.101.34. When Terraform replaces those instances, the old targets will be deregistered and the new instance IDs or IPs will only exist after apply, so each target group will temporarily have no healthy backend to serve traffic.

This is not just harmless attachment churn. AWS only routes to newly registered targets after registration completes and the target passes initial health checks, and the API target group checks /health on a 30 second interval. With only one backend in each group and no evidence of create_before_destroy or parallel healthy capacity, the ALB and NLB paths will drop traffic during the cutover, producing failed requests, unhealthy-target transitions, and likely Route53/CloudWatch alerting for the affected singleton services.
View reasoning tree here.

Caution

[High Risk] Replacing singleton EC2 backends will drop the live API, transaction feed, and EIP endpoint during apply

The change replaces the only healthy backend behind two live AWS load balancer target groups: 540044833068.eu-west-2.ec2-instance.i-0bf4039822e01f430 is the sole healthy instance target in 540044833068.eu-west-2.elbv2-target-group.api-207c90ee-tg, and 540044833068.eu-west-2.ec2-instance.i-0cff13d553da3fe3a currently owns the sole healthy IP target 10.0.101.34:9090 in 540044833068.eu-west-2.elbv2-target-group.txn-feed-terraform-example. Both backing instances and both target group attachments are being replaced, so during apply there will be a window where the old target is gone before the new instance is registered and healthy.

This will break the ALB-served API on port 80, the transaction feed on port 9090, and the public endpoint on EIP 13.134.236.98, which is being reassociated to the replacement instance. The main risk is not an unproven AMI regression; it is that these are singleton endpoints with no redundant healthy targets, so instance replacement itself creates downtime and endpoint churn.
View reasoning tree here.

Signals

Routine → Multiple compute resources showing unusual and infrequent routine changes at 1 event/week for the last 2-5 months, with additional instance resources at 3 events/week for the last 5 months, which is infrequent compared to typical patterns.

Additional Change Details: Items 76 Edges 166 model|risks_v6 ✨Encryption Key State Risk ✨KMS Key Creation

View in Overmind

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

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Renovatebot and dependabot updates frontend javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants