Skip to content

test(release): isolate release-notes fixture env - #762

Open
hangox wants to merge 2 commits into
icebear0828:devfrom
hangox:test/release-notes-fixture-env
Open

test(release): isolate release-notes fixture env#762
hangox wants to merge 2 commits into
icebear0828:devfrom
hangox:test/release-notes-fixture-env

Conversation

@hangox

@hangox hangox commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Remove RELEASE_NOTES_* configuration from the environment used by release-notes fallback test fixtures.
  • Prevent CI secrets from turning fallback assertions into real LLM requests and timeouts.
  • Add a focused assertion that the fixture retains unrelated environment values while removing all four release-notes variables.

Test plan

  • CI=true GITHUB_ACTIONS=true RELEASE_NOTES_BASE_URL=http://127.0.0.1:9/v1 RELEASE_NOTES_API_KEY=test-key RELEASE_NOTES_MODEL=test-model RELEASE_NOTES_REQUEST_TIMEOUT_MS=3000 npx vitest run tests/unit/ci/release-notes-script.test.ts --pool=forks --maxWorkers=1 --minWorkers=1 --testTimeout=5000 --hookTimeout=10000
  • npx tsc --noEmit
  • git diff --check

Notes

  • Test-only change; no production release workflow behavior changes.

hangox and others added 2 commits August 31, 2026 11:38
Release-note fallback fixtures must not inherit CI LLM credentials, which
can turn a local fallback assertion into a real network request and timeout.

Co-Authored-By: Claude <noreply@anthropic.com>
Exercise the squash-promotion fallback with complete ambient LLM settings
and verify that no release-note configuration reaches the node subprocess.

Co-Authored-By: Claude <noreply@anthropic.com>
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.

1 participant