Skip to content

adding changelog entry for 0.5.0 runtime release#384

Merged
gneeri merged 3 commits into
devfrom
0-5-0-changelog
Jun 5, 2026
Merged

adding changelog entry for 0.5.0 runtime release#384
gneeri merged 3 commits into
devfrom
0-5-0-changelog

Conversation

@nallana
Copy link
Copy Markdown
Contributor

@nallana nallana commented Jun 5, 2026

Note

Low Risk
Documentation-only change to the changelog; no runtime or application code is modified.

Overview
Adds a new v0.5.0 section at the top of docs/CHANGELOG.md, ahead of the existing v0.4.9 entry, with a compare link, June 3, 2026 date, intro paragraph, and links to the 0.5 release and compiler pipeline blog posts.

The entry documents the shipped Runtime work (manifest projects, classdef, expanded functions/indexing, typed builtins, structured execution outcomes, new control/communications/plotting/optimization builtins, staged compiler pipeline and related breaking changes), Desktop (RunMat Desktop), and Agent (runnable code blocks, persistence, sync/UX tweaks)—matching the usual Added/Changed subsection layout used in prior releases.

Reviewed by Cursor Bugbot for commit ea84a11. Bugbot is set up for automated code reviews on this repo. Configure here.

Summary by CodeRabbit

  • Documentation
    • Added v0.5.0 release notes describing a major compiler/runtime revision: staged semantic compilation, support for manifest-backed multi-file projects, richer function and class semantics (requested outputs, nested scopes, function handles), explicit indexing contexts, typed builtins, structured execution outcomes, expanded control/communications/plotting/optimization builtins, GPU fusion planning improvements, modular provider updates, and a tagged-value ABI for JIT integration.

@nallana nallana requested review from finrunsfar and gneeri June 5, 2026 00:49
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 5, 2026

Review Change Stack

📝 Walkthrough

Walkthrough

Adds a v0.5.0 (June 3, 2026) changelog entry documenting compiler and runtime changes: staged semantic pipeline, manifest-backed multi-file projects, classdef runtime objects, expanded function/indexing semantics, typed builtin descriptors, structured execution outcomes, GPU fusion planning, WGPU provider modularization, and a tagged-value JIT ABI.

Changes

v0.5.0 Changelog Documentation

Layer / File(s) Summary
v0.5.0 Changelog Entry
docs/CHANGELOG.md
Added v0.5.0 release section with dated overview and detailed Runtime subsections enumerating new compiler and runtime features and architectural refactors.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

  • finrunsfar

Poem

🐰 A changelog hops into view,
v0.5.0—bright and new.
Pipelines, manifests, and runtime cheer,
GPU dreams drawing near,
I nibble bytes and bound with you.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The PR title accurately describes the primary change: adding a changelog entry for the v0.5.0 runtime release, which matches the file modification and PR objectives.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 0-5-0-changelog

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/CHANGELOG.md`:
- Around line 34-49: The changelog sections are missing blank lines before
subsection headings; edit the "### Desktop" and "### Agent" blocks so there is a
single blank line before each "#### Added" and "#### Changed" heading (i.e.,
insert a blank line between the parent "### ..." heading and the "#### ..."
subsection headings such as "#### Added" and "#### Changed" to match the
existing v0.4.9 formatting and satisfy MD022).
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 293845b3-11a5-4623-91b2-40654854ee68

📥 Commits

Reviewing files that changed from the base of the PR and between 67ed988 and ea84a11.

📒 Files selected for processing (1)
  • docs/CHANGELOG.md

Comment thread docs/CHANGELOG.md
Comment on lines +34 to +49
### Desktop

#### Added
- Add [RunMat Desktop](/blog/introducing-runmat-desktop) — a local, GPU-accelerated workspace for MATLAB-syntax code with an editor, plots, variables, notebooks, run history, local file access, optional cloud projects, and a project-aware Agent

### Agent

#### Added
- Add runnable Agent code blocks — RunMat/MATLAB-style snippets in Agent answers now render with editor controls, can be copied, and can be sent directly to runtime execution
- Add project-scoped Agent persistence so projects can restore Agent state through Desktop project settings such as `persist_agents` in `runmat.toml`
- Add local-to-cloud project conversion support for Agent and history flows that need a cloud project

#### Changed
- Make Agent activity easier to follow by grouping long activity runs and replacing “Thinking” labels with clearer “Working” language
- Improve Agent execution and project synchronization across Desktop, browser, local, and cloud runtimes

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Add blank lines around subsection headings for consistency.

The new Desktop and Agent sections are missing blank lines before their #### Added and #### Changed headings, which is inconsistent with the existing changelog formatting (see the v0.4.9 section for reference).

📝 Proposed fix to add blank lines
 ### Desktop
 
 #### Added
+
 - Add [RunMat Desktop](/blog/introducing-runmat-desktop) — a local, GPU-accelerated workspace for MATLAB-syntax code with an editor, plots, variables, notebooks, run history, local file access, optional cloud projects, and a project-aware Agent
 
 ### Agent
 
 #### Added
+
 - Add runnable Agent code blocks — RunMat/MATLAB-style snippets in Agent answers now render with editor controls, can be copied, and can be sent directly to runtime execution
 - Add project-scoped Agent persistence so projects can restore Agent state through Desktop project settings such as `persist_agents` in `runmat.toml`
 - Add local-to-cloud project conversion support for Agent and history flows that need a cloud project
 
 #### Changed
+
 - Make Agent activity easier to follow by grouping long activity runs and replacing "Thinking" labels with clearer "Working" language
 - Improve Agent execution and project synchronization across Desktop, browser, local, and cloud runtimes

As per coding guidelines, this matches the MD022 markdownlint rule requiring blank lines around headings.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### Desktop
#### Added
- Add [RunMat Desktop](/blog/introducing-runmat-desktop) — a local, GPU-accelerated workspace for MATLAB-syntax code with an editor, plots, variables, notebooks, run history, local file access, optional cloud projects, and a project-aware Agent
### Agent
#### Added
- Add runnable Agent code blocks — RunMat/MATLAB-style snippets in Agent answers now render with editor controls, can be copied, and can be sent directly to runtime execution
- Add project-scoped Agent persistence so projects can restore Agent state through Desktop project settings such as `persist_agents` in `runmat.toml`
- Add local-to-cloud project conversion support for Agent and history flows that need a cloud project
#### Changed
- Make Agent activity easier to follow by grouping long activity runs and replacing “Thinking” labels with clearer “Working” language
- Improve Agent execution and project synchronization across Desktop, browser, local, and cloud runtimes
### Desktop
#### Added
- Add [RunMat Desktop](/blog/introducing-runmat-desktop) — a local, GPU-accelerated workspace for MATLAB-syntax code with an editor, plots, variables, notebooks, run history, local file access, optional cloud projects, and a project-aware Agent
### Agent
#### Added
- Add runnable Agent code blocks — RunMat/MATLAB-style snippets in Agent answers now render with editor controls, can be copied, and can be sent directly to runtime execution
- Add project-scoped Agent persistence so projects can restore Agent state through Desktop project settings such as `persist_agents` in `runmat.toml`
- Add local-to-cloud project conversion support for Agent and history flows that need a cloud project
#### Changed
- Make Agent activity easier to follow by grouping long activity runs and replacing "Thinking" labels with clearer "Working" language
- Improve Agent execution and project synchronization across Desktop, browser, local, and cloud runtimes
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)

[warning] 36-36: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)


[warning] 41-41: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)


[warning] 46-46: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/CHANGELOG.md` around lines 34 - 49, The changelog sections are missing
blank lines before subsection headings; edit the "### Desktop" and "### Agent"
blocks so there is a single blank line before each "#### Added" and "####
Changed" heading (i.e., insert a blank line between the parent "### ..." heading
and the "#### ..." subsection headings such as "#### Added" and "#### Changed"
to match the existing v0.4.9 formatting and satisfy MD022).

@gneeri gneeri merged commit 935de48 into dev Jun 5, 2026
6 of 10 checks passed
@gneeri gneeri deleted the 0-5-0-changelog branch June 5, 2026 17:27
@coderabbitai coderabbitai Bot mentioned this pull request Jun 5, 2026
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.

3 participants