Skip to content

fix(ci): add version comments to SHA-pinned GitHub Actions#154

Open
anupsv wants to merge 1 commit into
masterfrom
fix/add-sha-version-comments
Open

fix(ci): add version comments to SHA-pinned GitHub Actions#154
anupsv wants to merge 1 commit into
masterfrom
fix/add-sha-version-comments

Conversation

@anupsv
Copy link
Copy Markdown
Contributor

@anupsv anupsv commented May 14, 2026

Summary

  • All three GitHub Actions in both workflow files were already correctly SHA-pinned
  • pnpm/action-setup and actions/setup-node were missing the version comment that makes pinned SHAs human-readable and auditable
  • No SHA values were changed — only version comments added

SHA Verification

Action SHA Version
actions/checkout 11bd71901bbe5b1630ceea73d27597364c9af683 v4.2.2 (already commented)
pnpm/action-setup fc06bc1257f339d1d5d8b3a19a8cae5388b55320 v4.4.0 (comment added)
actions/setup-node 49933ea5288caeca8642d1e84afbd3f7d6820020 v4.4.0 (comment added)

All SHAs verified via GitHub API against their respective release tags.

Test plan

  • Verify the SHAs in the diff still match the tagged versions on GitHub
  • Confirm CI workflows continue to pass after this change

🤖 Generated with Claude Code

All workflow actions were already correctly SHA-pinned, but
pnpm/action-setup and actions/setup-node were missing the version
comment that makes the pinned SHA auditable at a glance.

- pnpm/action-setup@fc06bc1...  → # v4.4.0
- actions/setup-node@49933ea... → # v4.4.0
- actions/checkout@11bd719...   → # v4.2.2 (already present)

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
mcclurejt added a commit that referenced this pull request May 15, 2026
The platform now sets tee-env-ECLOUD_PLATFORM_HOST directly from
cfg.DeriveAppHostname(appAddress) at VM-create time (see
ecloud-platform PR #154). Injecting it into publicEnv from the
client made the user's on-chain release blob carry a value the
user never supplied — visible in 'ecloud compute app info' and
the verify dashboard, and frozen in the release record so a later
AppBaseDomain change can't update it.

Platform-derived values belong in platform metadata. Drop the
injection. derivePlatformHost stays exported because external
consumers (e.g. scripts/e2e/lib/cli.sh's mirror in the
ecloud-platform harness) still use it for client-side
hostname derivation when they need to predict the platform's
choice.
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