chore(deps): update dependency artillery to v2.0.27 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
artillery	2.0.26 -> 2.0.27

---

Release Notes

artilleryio/artillery (artillery)

v2.0.27: Artillery v2.0.27

Compare Source

New features

Core

• Custom metric names are now limited to 1024 characters #​3637

AWS ECS/Fargate

• Add new --no-assign-public-ip flag to disable automatic assignment of public IPs to worker tasks. This allows for load tests to run from private subnets with a NAT gateway attached for use-cases where traffic has to come from a set of known IPs. #​3643

Azure ACI

• Azure load testing is now available on all subscriptions, including month-to-month ones. Previously only annual subscriptions could use the Azure integration.

Load testing with Playwright

• Upgrade to Playwright v1.56.1
• FID (First Input Delay) scores are no longer reported. FID has been deprecated as a Core Web Vital metric on September 9, 2024, and replaced by INP (Interaction To Next Paint). https://web.dev/articles/fid

Fixes & improvements

AWS ECS/Fargate

• Fix issue where ECS IAM policy could not be created #​3640
• Fix handling of relative paths in config.payload when a separate config is used with the --config flag. #​3657 #​3653
• Fix handling of --scenario-name flag #​3651

---

with contributions from @​YH1715

---

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]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nestjs/apollo@13.2.1
npm error Found: @apollo/server@5.1.0
npm error node_modules/@apollo/server
npm error   dev @apollo/server@"5.1.0" from the root project
npm error   peer @apollo/server@"^4.0.0 || ^5.0.0" from @as-integrations/express5@1.1.2
npm error   node_modules/@as-integrations/express5
npm error     dev @as-integrations/express5@"1.1.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @apollo/server@"5.0.0" from @nestjs/apollo@13.2.1
npm error node_modules/@nestjs/apollo
npm error   dev @nestjs/apollo@"13.2.1" from the root project
npm error
npm error Conflicting peer dependency: @apollo/server@5.0.0
npm error node_modules/@apollo/server
npm error   peer @apollo/server@"5.0.0" from @nestjs/apollo@13.2.1
npm error   node_modules/@nestjs/apollo
npm error     dev @nestjs/apollo@"13.2.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-11-18T17_27_08_124Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-11-18T17_27_08_124Z-debug-0.log

[coveralls]

Pull Request Test Coverage Report for Build a2b4d29c-f607-4651-9ecd-37846a48f65c

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 88.939%

---

Totals
Change from base Build b39defcd-191e-476d-9a2b-7768c390bfd4:	0.0%
Covered Lines:	7325
Relevant Lines:	8236

---

💛 - Coveralls