ci: add reproducible plugin verification#1
Conversation
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
📝 WalkthroughWalkthroughThe pull request pins the Rust and Extism test environment, adds reusable CI and release workflow paths, and strengthens WASM smoke tests with shared fixtures, JSON host stubs, required artifacts, and export-level assertions. ChangesPlugin CI and WASM smoke coverage
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
There was a problem hiding this comment.
1 issue found across 5 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name=".github/workflows/plugin-ci.yml">
<violation number="1" location=".github/workflows/plugin-ci.yml:11">
P2: The job-level `permissions: contents: write` in the CI workflow may be both too broad (write access to repo contents) and too narrow (all other permissions default to `none`). Granting only `contents: write` while omitting `checks`, `pull-requests`, or `statuses` could break the reusable workflow if it needs to post check annotations or comment on PRs. Consider reviewing what the called reusable workflow actually requires and setting the minimum set of explicit permissions.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
|
|
||
| jobs: | ||
| plugin-ci: | ||
| permissions: |
There was a problem hiding this comment.
P2: The job-level permissions: contents: write in the CI workflow may be both too broad (write access to repo contents) and too narrow (all other permissions default to none). Granting only contents: write while omitting checks, pull-requests, or statuses could break the reusable workflow if it needs to post check annotations or comment on PRs. Consider reviewing what the called reusable workflow actually requires and setting the minimum set of explicit permissions.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .github/workflows/plugin-ci.yml, line 11:
<comment>The job-level `permissions: contents: write` in the CI workflow may be both too broad (write access to repo contents) and too narrow (all other permissions default to `none`). Granting only `contents: write` while omitting `checks`, `pull-requests`, or `statuses` could break the reusable workflow if it needs to post check annotations or comment on PRs. Consider reviewing what the called reusable workflow actually requires and setting the minimum set of explicit permissions.</comment>
<file context>
@@ -0,0 +1,13 @@
+
+jobs:
+ plugin-ci:
+ permissions:
+ contents: write
+ uses: mpiton/vortex/.github/workflows/plugin-ci.yml@e9edb3b1b60cd795f03cf1e5acba7d6b3731f753
</file context>
There was a problem hiding this comment.
Fixed in 542117b. Branch and PR validation is read-only; contents:write exists only on the tag-gated release job.
There was a problem hiding this comment.
All reported issues were addressed across 1 file (changes from recent commits).
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
Summary
Validation
Linear: MAT-129
Summary by cubic
Adds reproducible plugin verification using centrally maintained, SHA-pinned workflows split into read-only verification and owner-gated release. Requires the release
.wasmin smoke tests and exercises all exports with HTTP and premium credentials; pins Rust 1.95.0,wasm32-wasip1, andextism1.30.0. Aligns with Linear MAT-129.CI and Tests
rust-toolchain.toml; docs clarify lint → build.wasm→ test order; smoke tests hard-fail if the artifact is missing.Dependencies
extismto=1.30.0.Cargo.lockto the latestwasmtimestack and related crates.Written for commit 1e10c33. Summary will update on new commits.
Summary by CodeRabbit