Skip to content

chore(deps): update dependency promptfoo to v0.121.11#512

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

chore(deps): update dependency promptfoo to v0.121.11#512
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/promptfoo-0.x-lockfile

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Mar 27, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
promptfoo 0.121.20.121.11 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

promptfoo/promptfoo (promptfoo)

v0.121.11

Compare Source

Features
  • quiverai: add Arrow 1.1 models, vectorize endpoint, and GPT Image-2 pipeline (#​9139) (ce2c62d)
Bug Fixes

v0.121.10

Compare Source

Features
Bug Fixes
Performance Improvements
  • providers/http: parallelize createHttpsAgent file reads (#​8956) (108c80b)
Reverts
  • feat(providers): add first-class n parameter support for OpenAI chat completions (#​9113) (543b5de)

v0.121.9

Compare Source

Features
Bug Fixes
  • cli: align command-line reference with CLI (#​8900) (c4ce0d4)
  • deps: update openai packages (544d1c6)
  • telemetry: mirror person properties on every event (#​8902) (95ad451)
  • prevent report table header icon overlap (#​8880) (ad87060)
  • trailing slashes on internal routes, Docusaurus Link for internal hrefs, and test hygiene (#​8903) (0828ff7)

v0.121.8

Compare Source

Features
Bug Fixes

v0.121.7

Compare Source

Features
Bug Fixes

v0.121.5

Compare Source

Features
Bug Fixes
  • app: chart toggle visibility (#​8439) (f9d448d)
  • assertions: avoid jsdom in HTML assertions (979aee4)
  • correct rouge assertion reason messages when inverse: true (#​8682) (7d64d8d)
  • deps: update anthropic packages (#​8670) (0a4a7e0)
  • deps: update dependency openai to ^6.34.0 (#​8701) (73f6ba1)
  • deps: update dependency parse5 to v8 (#​8710) (759391d)
  • deps: update openai packages (#​8672) (1ae735c)
  • providers: close stdin on exec provider to prevent child process hanging (#​8686) (9cd7709)
  • providers: resolve settings file path for claude-agent-sdk (#​8606) (d575bd1)
  • providers: send reasoning config for Azure responses deployments (#​8255) (67437f3)
  • redteam: throw immediately on non-OK HTTP responses in redteam discover (#​8677) (770a557)
  • server: prevent circular JSON when Bedrock/Anthropic provider is used as llm-rubric judge from web UI (#​8688) (f26e54b)

v0.121.4

Compare Source

Features
Bug Fixes

Note

PR body was truncated to here.


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 Mar 27, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Mar 27, 2026

Caution

[High Risk] Production API server will be launched as a public EC2 host without an IAM instance profile

This change creates a new production API EC2 instance on t4g.nano and starts a Python health service bound to 0.0.0.0:9090. The attached security groups restrict 9090 to 10.0.0.0/8, so the health endpoint is not broadly internet-exposed, but the instance pattern itself is still unsafe: the existing live equivalent 540044833068.eu-west-2.ec2-instance.i-025efedc46bef3be1 shows the same configuration launches with a public IP and IamInstanceProfile: null.

That means the change is creating another directly reachable production EC2 host without a machine IAM role, which violates the organization’s network-access and compute-hardening requirements. The public endpoint increases attack surface on the host, and the lack of an instance profile removes the normal least-privilege path for AWS access, encouraging unmanaged credentials or preventing use of AWS-managed controls such as SSM-based administration.
View reasoning tree here.

Caution

[High Risk] Public SSH exposure on the internet-facing EC2 instance will remain after this change

The production EC2 instance 540044833068.eu-west-2.ec2-instance.i-0c5a1bf5b0c8c445e is publicly reachable and attached to security group sg-0437857de45b640ce, which allows inbound SSH on port 22 from 0.0.0.0/0. This is a direct violation of the organization’s network access policy and AWS compute hardening guidance (SEC06-BP03), because it exposes an internet-facing host to unrestricted interactive access.

This change does not mitigate that exposure. The planned diff only causes the instance public IP/DNS to be reassigned as part of the update path, and related planned resources show public addressing is still being used. With no corresponding change to remove the public IP path or restrict the SSH rule, the instance will remain directly reachable for brute-force attempts and unauthorized access, with a clear path to host compromise and follow-on lateral movement from a production platform host.
View reasoning tree here.

Caution

[High Risk] Public ALB target group replacement can cut over to an incompatible single backend and take the API offline

The change replaces the public ALB target group api-207c90ee-tg while introducing a new single EC2 backend that only serves a demo health endpoint on 9090 and is registered through aws_lb_target_group_attachment. The current ALB listener forwards to an instance target group on port 80 with HTTP /health checks, and AWS requires target type to be fixed at target-group creation. Unless the replacement target group, listener forwarding, health checks, and backend security-group rules are all updated consistently, the ALB will forward to no healthy targets because the new backend does not match the current public target-group contract.

This will cause public API outage on api-207c90ee-alb when traffic is switched to the replacement target group. The change also concentrates the public path onto one newly launched instance instead of an existing multi-target backend, so it reduces fault tolerance and depends on successful instance launch during deployment. On top of that, the new instance is being assigned an Elastic IP, which creates direct EC2 exposure contrary to the organization’s network-access policy.
View reasoning tree here.

Caution

[High Risk] Single-AZ single-instance API deployment will leave the service without failover

This change is creating a production-tagged EC2-backed API server in subnet-07b5b1fb2ba02f964, which blast-radius data shows is in eu-west-2a only, and attaching that single instance to a target group on port 9090. There is no Auto Scaling Group, no second instance in another Availability Zone, and no evidence of multi-AZ target registration. The service is therefore still anchored to one EC2 instance in one AZ even though it sits behind an ALB.

If that instance or eu-west-2a has a failure, the load balancer will have no healthy target to route to and the API will go down. This is a production single point of failure and violates the organization’s high-availability requirement for multi-AZ deployment in production (REL10-BP01).
View reasoning tree here.

Warning

[Medium Risk] New EC2 health server on port 9090 will be broadly reachable through shared security groups

The change creates 540044833068.eu-west-2.ec2-instance.i-025efedc46bef3be1 with user data that starts a Python HTTP server bound to 0.0.0.0:9090, then attaches it to shared production security groups sg-03cf38efd953aa056 and sg-089e5107637083db5. Current state shows the internal-services group allows inbound 9090 from 10.0.0.0/8, and both shared groups are used as broad trust boundaries rather than instance-specific controls.

That means the new unmanaged health endpoint will be reachable across a very large internal address range and will inherit customer/internal access scopes intended for other purposes. This is a real network-segmentation and least-privilege violation under SEC05-BP02 and the org policy that EC2 access must be tightly controlled. Even though the new target group attachment correctly uses port 9090, the instance still expands internal attack surface and lateral-movement paths for a production workload.
View reasoning tree here.

Signals

Routine → Multiple API server and access resources showing unusual, infrequent routine changes at 1 event/week for the last 3 months, with several related resources at 2 events/week for the last 3 months, which is infrequent compared to typical patterns.
Policies → Multiple policy findings show unusual security and compliance issues that may need review: an S3 bucket does not have server-side encryption configured and is missing required tags, while a security group allows SSH (port 22) access from anywhere (0.0.0.0/0).

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

View in Overmind

Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

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

Overmind

⛔ Auto-Blocked


🔴 Decision

Auto-blocked: Routine score (-5) is below minimum (-1)


📊 Signals Summary

Routine 🔴 -5


🔥 Risks Summary

High 0 · Medium 0 · Low 0


💥 Blast Radius

Items 23 · Edges 75


View full analysis in Overmind ↗

@renovate renovate Bot force-pushed the renovate/promptfoo-0.x-lockfile branch from 514a41c to 58cbaeb Compare March 27, 2026 13:24
Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

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

Overmind

⛔ Auto-Blocked


🔴 Decision

Auto-blocked: Policy signal (-3) is below threshold (-2); Routine score (-5) is below minimum (-1)


📊 Signals Summary

Routine 🔴 -5

Policies 🔴 -3


🔥 Risks Summary

High 0 · Medium 0 · Low 0


💥 Blast Radius

Items 5 · Edges 20


View full analysis in Overmind ↗

@renovate renovate Bot force-pushed the renovate/promptfoo-0.x-lockfile branch from 58cbaeb to a1c25a9 Compare April 1, 2026 20:12
Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

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

Overmind

⛔ Auto-Blocked


🔴 Decision

Found 2 high risks requiring review


📊 Signals Summary

Routine 🔴 -5

Policies 🔴 -3


🔥 Risks Summary

High 2 · Medium 0 · Low 0


💥 Blast Radius

Items 107 · Edges 219


View full analysis in Overmind ↗

@renovate renovate Bot force-pushed the renovate/promptfoo-0.x-lockfile branch from a1c25a9 to f877105 Compare April 8, 2026 21:00
Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

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

Overmind

⛔ Auto-Blocked


🔴 Decision

Found 1 high risk requiring review


📊 Signals Summary

Routine 🔴 -5

Policies 🔴 -3


🔥 Risks Summary

High 1 · Medium 1 · Low 0


💥 Blast Radius

Items 63 · Edges 135


View full analysis in Overmind ↗

@renovate renovate Bot force-pushed the renovate/promptfoo-0.x-lockfile branch from f877105 to 4b949a7 Compare April 11, 2026 01:20
@renovate renovate Bot changed the title chore(deps): update dependency promptfoo to v0.121.3 chore(deps): update dependency promptfoo to v0.121.4 Apr 11, 2026
Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

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

Overmind

⛔ Auto-Blocked


🔴 Decision

Found 2 high risks requiring review


📊 Signals Summary

Routine 🔴 -5

Policies 🔴 -3


🔥 Risks Summary

High 2 · Medium 0 · Low 0


💥 Blast Radius

Items 93 · Edges 217


View full analysis in Overmind ↗

@renovate renovate Bot force-pushed the renovate/promptfoo-0.x-lockfile branch from 4b949a7 to 2bb4553 Compare April 15, 2026 03:03
@renovate renovate Bot changed the title chore(deps): update dependency promptfoo to v0.121.4 chore(deps): update dependency promptfoo to v0.121.5 Apr 15, 2026
Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

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

Overmind

⛔ Auto-Blocked


🔴 Decision

Auto-blocked: Policy signal (-3) is below threshold (-2); Routine score (-5) is below minimum (-1)


📊 Signals Summary

Routine 🔴 -5

Policies 🔴 -3


🔥 Risks Summary

High 0 · Medium 0 · Low 0


💥 Blast Radius

Items 79 · Edges 192


View full analysis in Overmind ↗

@renovate renovate Bot changed the title chore(deps): update dependency promptfoo to v0.121.5 chore(deps): update dependency promptfoo to v0.121.7 Apr 22, 2026
@renovate renovate Bot force-pushed the renovate/promptfoo-0.x-lockfile branch 2 times, most recently from d4fad61 to 5b7c7a5 Compare April 24, 2026 22:34
@renovate renovate Bot changed the title chore(deps): update dependency promptfoo to v0.121.7 chore(deps): update dependency promptfoo to v0.121.8 Apr 24, 2026
@renovate renovate Bot force-pushed the renovate/promptfoo-0.x-lockfile branch from 5b7c7a5 to be239e2 Compare April 27, 2026 19:41
@renovate renovate Bot changed the title chore(deps): update dependency promptfoo to v0.121.8 chore(deps): update dependency promptfoo to v0.121.9 Apr 27, 2026
@renovate renovate Bot force-pushed the renovate/promptfoo-0.x-lockfile branch from be239e2 to 4766350 Compare April 29, 2026 20:37
@renovate renovate Bot force-pushed the renovate/promptfoo-0.x-lockfile branch from 4766350 to 8464773 Compare May 7, 2026 21:45
@renovate renovate Bot changed the title chore(deps): update dependency promptfoo to v0.121.9 chore(deps): update dependency promptfoo to v0.121.10 May 7, 2026
@renovate renovate Bot force-pushed the renovate/promptfoo-0.x-lockfile branch from 8464773 to d192a3c Compare May 8, 2026 06:14
@renovate renovate Bot changed the title chore(deps): update dependency promptfoo to v0.121.10 chore(deps): update dependency promptfoo to v0.121.11 May 8, 2026
@renovate renovate Bot force-pushed the renovate/promptfoo-0.x-lockfile branch from d192a3c to 3392d49 Compare May 12, 2026 10:12
@renovate renovate Bot force-pushed the renovate/promptfoo-0.x-lockfile branch from 3392d49 to 02477be Compare May 18, 2026 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants