Skip to content

ci: rename l4 job to vm-e2e in release and spike workflows#90

Merged
fullstackjam merged 1 commit into
mainfrom
ci/rename-l4-job-to-vm-e2e
May 19, 2026
Merged

ci: rename l4 job to vm-e2e in release and spike workflows#90
fullstackjam merged 1 commit into
mainfrom
ci/rename-l4-job-to-vm-e2e

Conversation

@fullstackjam
Copy link
Copy Markdown
Collaborator

Summary

  • Rename the l4 job to vm-e2e in both release.yml and vm-e2e-spike.yml
  • l4 is an internal tier label that means nothing in the GitHub Actions UI; vm-e2e is self-describing

Test plan

  • CI green
  • After merge, push a tag and confirm the job shows as vm-e2e in the release run

@github-actions github-actions Bot added the ci CI/CD changes label May 19, 2026
@fullstackjam fullstackjam merged commit d1cf74f into main May 19, 2026
11 checks passed
@fullstackjam fullstackjam deleted the ci/rename-l4-job-to-vm-e2e branch May 19, 2026 03:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci CI/CD changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant