Skip to content

fix(bruno): keep generated values in runtime scope - #3973

Open
Yurii201811 wants to merge 1 commit into
interledger:mainfrom
Yurii201811:fix/bruno-v4-runtime-variables
Open

Yurii201811 wants to merge 1 commit into
interledger:mainfrom
Yurii201811:fix/bruno-v4-runtime-variables

Conversation

@Yurii201811

Copy link
Copy Markdown

Changes proposed in this pull request

  • Keep values generated by the Rafiki Bruno collection in runtime scope instead of persisting them to environment files.
  • Read generated values from runtime scope, while preserving the configured assetId fallback used by the Local Playground environments.

Context

Bruno v4 persists bru.setEnvVar() changes to disk by default. The affected values are generated for the current collection run, and some are access or continuation tokens, so they should stay in runtime scope.

Fixes #3948

Verification

  • pnpm dlx prettier@3.2.5 --check bruno/collections/Rafiki
  • node --check bruno/collections/Rafiki/scripts.js
  • Confirmed no bru.setEnvVar(), bru.deleteEnvVar(), or bru.setGlobalEnvVar() calls remain in the Rafiki collection.
  • Confirmed all changed files are under bruno/collections/Rafiki/.

Checklist

  • Related issues linked using fixes #number
  • Tests added/updated
  • Make sure that all checks pass
  • Bruno collection updated (if necessary)
  • Documentation issue created with user-docs label (if necessary)
  • OpenAPI specs updated (if necessary)

@netlify

netlify Bot commented Aug 30, 2026

Copy link
Copy Markdown

Deploy Preview for brilliant-pasca-3e80ec canceled.

Name Link
🔨 Latest commit 12a55cb
🔍 Latest deploy log https://app.netlify.com/projects/brilliant-pasca-3e80ec/deploys/6a948a22d2c95b00084decb4

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Prepare for Bruno v4 migration

1 participant