docs: RELEASE-NOTES.md for v1.0.5 (sessions + project memory) - #69
Merged
ndemianc merged 1 commit intoAug 15, 2026
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
44 commits since v1.0.4, five merged PRs (#64-#68). The headline is not the MCP tail — it is that chats became sessions and projects gained a memory. Structure follows v1.0.4: a lede, Highlights, then the factual sections. Six highlights — sessions and the History panel, honest three-tier resume, project memory, memory-as-untrusted-input, fork, and Copy as Markdown — plus the eight new settings with their real defaults. Two things stated that a release note would usually omit: - A "Not in this release" section saying the panel does NOT search yet. It is the first gap a user hits once a project holds more than a screenful of sessions, and letting them discover it after upgrading is worse than saying it. Same finding #68 put in the design docs. - The memory security posture as its own highlight rather than a footnote, because memory is replayed into every future session and is distilled from transcripts containing repo files and MCP output. The instruction gate, the surfacing, the redaction and the verify-first framing are the feature. Every claim re-checked against the build rather than the commit log: all 8 settings and defaults match package.json; the card renders exactly rename/fork/export/done/delete/pin; the digest carries its verify-first framing; the instruction gate refuses to auto-promote; secrets are redacted; and the "no search" claim is true. Suite counts (32 suites / 528 cases) measured, not recalled.
Copy link
Copy Markdown
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the project’s release notes to reflect LevelCode v1.0.5, focusing on the shift from ephemeral chats to persisted sessions and the introduction of per-project memory (with explicit “untrusted input” framing and security posture).
Changes:
- Rewrites the v1.0.5 lede and Highlights to cover sessions (resume/fork/export) and project memory.
- Adds a “New settings” section enumerating the new sessions/memory settings and defaults.
- Adds a “Not in this release” section explicitly calling out missing Sessions search, and updates test coverage + changelog link.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Sorry, something went wrong.
Comment thread
RELEASE-NOTES.md
|
|
||
| ## New settings | ||
|
|
||
| | Setting | Default | | |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
44 commits since v1.0.4, five merged PRs (#64–#68). The headline isn't the MCP tail — it's that chats became sessions and projects gained a memory.
Structure follows v1.0.4: lede, Highlights, then the factual sections. Six highlights — sessions and the History panel, honest three-tier resume, project memory, memory-as-untrusted-input, fork, Copy as Markdown — plus the eight new settings with their real defaults.
Two things a release note would usually leave out
A "Not in this release" section, saying plainly that the Sessions panel does not search yet. It's the first gap a user hits once a project holds more than a screenful of sessions, and letting them discover it after upgrading is worse than saying it. Same finding #68 put into the design docs.
The memory security posture as its own highlight, not a footnote. Memory is replayed into the system prompt of every future session and is distilled from transcripts containing repo files, command output and MCP results. The instruction gate, the surfacing, the redaction and the verify-first framing are the feature, not caveats to it.
Every claim re-checked against the build
Not against the commit log:
It also passes the tag-on-merge.yml gate from #63: no TODO markers, no scaffolding, first line names v1.0.5.
Note on the release in flight
v1.0.5 is already tagged at 37cd2ca (develop tip, includes #67 and #68), and a draft release exists with all four signed assets attached — but its body is still the placeholder text from the old hybrid workflow, telling the reader the assets are unsigned. That needs replacing with these notes before publishing.