chainlink allow to customise which YAML file is used for installing private plugins

Why? So that 3rd parties could instruct the local CRE to use a different private.plugins.yaml file without touching the chainlink repo.

How? By running go run . env setup -c custom-setup-file.toml or go run . env build-caps custom-setup-file.toml.

# custom-setup-file.toml
# This file defines private plugins to be installed via `loopinstall`.

# Common plugin configuration
defaults:
  goflags: "-ldflags=-s"

plugins:
  secret-cap:
    - moduleURI: "./secret-cap"
      installPath: "."
      flags: "-tags timetzdata"

Dec 11 '25 15:12 Tofel

I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset as well as in the text include at least one of the following tags:

#added For any new functionality added.
#breaking_change For any functionality that requires manual action for the node to boot.
#bugfix For bug fixes.
#changed For any change to the existing functionality.
#db_update For any feature that introduces updates to database schema.
#deprecation_notice For any upcoming deprecation functionality.
#internal For changesets that need to be excluded from the final changelog.
#nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
#removed For any functionality/config that is removed.
#updated For any functionality that is updated.
#wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.