Skip to content

chore(release): v0.4.0 — component E5DC2 fix + wasi filesystem/sandbox fix - #404

Merged
avrabe merged 1 commit into
mainfrom
release/v0.4.0
Jul 9, 2026
Merged

chore(release): v0.4.0 — component E5DC2 fix + wasi filesystem/sandbox fix#404
avrabe merged 1 commit into
mainfrom
release/v0.4.0

Conversation

@avrabe

@avrabe avrabe commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

Version bump 0.3.6 → 0.4.0. Kiln's v0.4.0 scope is verified: SR-30 + SR-33.

Deferred to v0.5.0 (unworked/large): SR-29 (cross-core imports), SR-34 (witness-instrumented core load), REQ_GC_SUBTYPING, SM-MEM-003.

gale:REQ-OS-SYSCALL-001 shown in rivet release status v0.4.0 is a separate-repo (gale) artifact sharing the v0.4.0 version label — not kiln's release scope, and not a blocker for kiln's tag.

Must pass the 8 required gates → then I tag v0.4.0.

🤖 Generated with Claude Code

…x fix

Bumps the workspace 0.3.6 → 0.4.0. rivet release status v0.4.0 (kiln scope):
✓ SR-30 + SR-33 verified.

Scope:
  SR-30  wasi:cli/run export resolution honors the instance-import offset —
         fixes E5DC2 on meld-fused command components (#382).
  SR-33  kilnd --wasi-fs/--dir grants filesystem access (no silent no-op) +
         closes a sandbox-escape hazard (#392).

Deferred to v0.5.0 (unworked/large): SR-29 (cross-core imports), SR-34 (witness-
instrumented core load), REQ_GC_SUBTYPING, SM-MEM-003. The gale:REQ-OS-SYSCALL-001
in the v0.4.0 release view is a separate-repo (gale) artifact sharing the version
label — not part of kiln's release scope.

Trace: SR-30
@codecov

codecov Bot commented Jul 9, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@github-actions

github-actions Bot commented Jul 9, 2026

Copy link
Copy Markdown

🔍 Build Diagnostics Report

Summary

Metric Base Branch This PR Change
Errors 0 0 0
Warnings 5 5 0

🎯 Impact Analysis

Issues in Files You Modified

  • 0 new errors introduced by your changes
  • 0 new warnings introduced by your changes
  • 0 total errors in modified files
  • 0 total warnings in modified files
  • 0 files you modified

Cascading Issues (Your Changes Breaking Other Files)

  • 0 new errors in unchanged files
  • 0 new warnings in unchanged files
  • 0 unchanged files now affected

Note: "Cascading issues" are errors in files you didn't modify, caused by your changes (e.g., breaking API changes, dependency issues).

✅ No Issues Detected

Perfect! Your changes don't introduce any new errors or warnings, and don't break any existing code.


📊 Full diagnostic data available in workflow artifacts

🔧 To reproduce locally:

# Install cargo-kiln
cargo install --path cargo-kiln

# Analyze your changes
cargo-kiln build --output json --filter-severity error
cargo-kiln check --output json --filter-severity warning

@avrabe
avrabe merged commit 7598c60 into main Jul 9, 2026
20 checks passed
@avrabe
avrabe deleted the release/v0.4.0 branch July 9, 2026 04:48
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