Skip to content

Lock file maintenance - #553

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: (in timezone Europe/London)

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 the dependencies Renovatebot and dependabot updates label Jul 12, 2026
@renovate
renovate Bot enabled auto-merge (squash) July 12, 2026 23:15
@github-actions

github-actions Bot commented Jul 12, 2026 •

Copy link
Copy Markdown

Note

[Low Risk] Single-target ALB and NLB backends may go empty during instance replacement

The plan replaces the only currently healthy backends behind both load balancers: 540044833068.eu-west-2.ec2-instance.i-0bf4039822e01f430 is the sole healthy target in 540044833068.eu-west-2.elbv2-target-group.api-207c90ee-tg, and 10.0.101.34:9090 on 540044833068.eu-west-2.ec2-instance.i-0cff13d553da3fe3a is the sole healthy target in 540044833068.eu-west-2.elbv2-target-group.txn-feed-terraform-example. I checked the current target groups and target health, the attachment replacements, and the instance replacement diffs. The attachments are being replaced but show no overlap details, and the new instance IDs, ENIs, and private IPs are mostly only known after apply, so the plan does not establish that a new healthy backend will exist before the old one is removed.

If these replacements execute without overlapping healthy registration, the ALB path for /health on port 80 and the NLB path on port 9090 will have zero healthy targets during convergence, causing backend request failures until the replacement instances boot, pass health checks, and reattach. I looked for evidence of redundancy or explicit replacement ordering safeguards and did not find any in the current state or planned changes.
View reasoning tree here.

Note

[Low Risk] Instance replacement can delete the only visible local processing state for the API feed and fraud processor

The plan replaces the core-api and fraud_processor EC2 instances while their only visible attached storage is the root EBS volume, and those root volumes are configured with DeleteOnTermination=true. On termination, AWS will delete the existing root disks, so any offsets, caches, or transaction-processing state kept only on vol-06e1f6ef7dd525bef, vol-0fb10261c4b49ad53, or the fraud processor’s root volume will be lost instead of being reattached to the replacement instances.

I checked the current target groups and related planned changes for a safety mechanism and did not find one. The fraud-ingest target group currently has a single healthy upstream feed target at 10.0.101.34, which belongs to the core-api instance being replaced, and the feed attachment itself is also being replaced. No planned preserved volume, secondary processor, or visible external offset store appears in this change. If the fraud processor depends on local persisted offsets or local buffering, it will restart against a feed endpoint that is also being replaced and can miss or replay in-flight transaction events until state is rebuilt.
View reasoning tree here.

Signals

Routine → Multiple compute and monitoring resources showing unusual infrequent updates at 1 event/week for the last 2-5 months, with related instance and subscription resources changing only 2-3 events/week for the last 5 months.

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

View in Overmind

@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 7012bf6 to 7b5e925 Compare July 20, 2026 21:56
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from b067ef9 to 8a5a1bf Compare July 30, 2026 16:40
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 8a5a1bf to eeff7e0 Compare August 11, 2026 21:52
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from eeff7e0 to 416484e Compare October 3, 2026 23:27
@renovate

renovate Bot commented Oct 3, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ 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: modules/api-server/demo-app/package-lock.json
npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code EALLOWREMOTE
npm error Fetching packages of type "remote" have been disabled
npm error Refusing to fetch "https://registry.npmjs.org/@tailwindcss/oxide-wasm32-wasi/-/oxide-wasm32-wasi-4.3.5.tgz"
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-11-17T00_03_36_285Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 416484e to be6579b Compare October 5, 2026 13:57
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 0837135 to 092e8e8 Compare October 20, 2026 11:17
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 92e67ec to 966c952 Compare October 26, 2026 17:57
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 966c952 to d27d6c5 Compare November 17, 2026 00:03

This branch has not been deployed

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

Labels

dependencies Renovatebot and dependabot updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants