Skip to content

chore(microvm): build and publish lifecycle hook - #5380

Draft
edersonbrilhante wants to merge 1 commit into
feat-microvm-lifecycle-hooksfrom
microvm-lifecycle-hooks-ci-followup
Draft

chore(microvm): build and publish lifecycle hook#5380
edersonbrilhante wants to merge 1 commit into
feat-microvm-lifecycle-hooksfrom
microvm-lifecycle-hooks-ci-followup

Conversation

@edersonbrilhante

Copy link
Copy Markdown
Contributor

Description

Add CI and release automation for the MicroVM lifecycle hook introduced by #5280. The hook is registered as a Yarn workspace, built and tested in the Lambda workflow, packaged as a release asset, and attested alongside the Lambda artifacts.

The release workflow uploads microvm-lifecycle-hooks.zip and its attestation assets. The storage adapter is aligned with the current storage-provider export API so the new build succeeds on the #5280 base.

Test Plan

  • yarn install --immutable --mode=skip-build
  • yarn prettier --check "services/microvm-lifecycle-hooks/**/*.{ts,json,md}"
  • yarn eslint services/microvm-lifecycle-hooks/src
  • NX_DAEMON=false yarn nx test @aws-github-runner/microvm-lifecycle-hooks (45 tests passed)
  • yarn workspace @aws-github-runner/microvm-lifecycle-hooks build
  • Packaged and inspected microvm-lifecycle-hooks.zip
  • YAML parsing and git diff --check

Related Issues

Stacked on #5280.

@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails
actions/step-security/harden-runner 05e31511f85b41b11d1cf0ef85d0992719546e2c 🟢 7.8
Details
CheckScoreReason
Binary-Artifacts🟢 10no binaries found in the repo
Branch-Protection🟢 8branch protection is not maximal on development and all release branches
CI-Tests🟢 106 out of 6 merged PRs checked by a CI test -- score normalized to 10
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Code-Review🟢 10all changesets reviewed
Contributors🟢 6project has 2 contributing companies or organizations -- score normalized to 6
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Dependency-Update-Tool🟢 10update tool detected
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Maintained🟢 1030 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Packaging⚠️ -1packaging workflow not detected
Pinned-Dependencies🟢 6dependency not pinned by hash detected -- score normalized to 6
SAST🟢 9SAST tool detected but not run on all commits
Security-Policy🟢 10security policy file detected
Signed-Releases⚠️ -1no releases found
Token-Permissions🟢 10GitHub workflow tokens follow principle of least privilege
Vulnerabilities⚠️ 022 existing vulnerabilities detected

Scanned Files

  • .github/workflows/lambda.yml

@edersonbrilhante edersonbrilhante added the javascript Pull requests that update Javascript code label Sep 7, 2026
@edersonbrilhante
edersonbrilhante marked this pull request as draft September 7, 2026 09:51
@edersonbrilhante
edersonbrilhante force-pushed the microvm-lifecycle-hooks-ci-followup branch from be02857 to f1da598 Compare September 8, 2026 15:30
@edersonbrilhante
edersonbrilhante force-pushed the microvm-lifecycle-hooks-ci-followup branch from f1da598 to a973a0a Compare September 8, 2026 20:23
@edersonbrilhante
edersonbrilhante force-pushed the microvm-lifecycle-hooks-ci-followup branch from a973a0a to 0a02f45 Compare September 8, 2026 20:27
@edersonbrilhante
edersonbrilhante force-pushed the microvm-lifecycle-hooks-ci-followup branch from 0a02f45 to 1e1d9f2 Compare September 8, 2026 20:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

compute-provider:aws_microvm javascript Pull requests that update Javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant