Repository navigation
chore(release): prepare v1.1.0 - #89
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
There was a problem hiding this comment.
This is a standard release preparation PR bumping the version from 1.0.0 → 1.1.0. All five changed files are consistent:
package.jsonandpackage-lock.jsonboth reflect"version": "1.1.0".CHANGELOG.mdhas a well-formed1.1.0section matching the PR description's feature list.README.mdcorrectly updates the "Release status" paragraph.versions.txtappends the1.1.0entry.
No defects were found. The PR is safe to merge once the release workflow (release.yml) confirms the tag matches the version in package.json.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
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.



Bumps the version to 1.1.0 and adds its release notes. After this merges, an annotated
v1.1.0tag onmaintriggersrelease.yml. That workflow checkspackage.jsonmatches the tag, builds the Windows and Linux assets, and publishes the GitHub release with CHANGELOG.md as the notes.package.json/package-lock.json: 1.0.0 → 1.1.0CHANGELOG.md: 1.1.0 section covering feat: reopen recent sessions at startup, plus PowerShell cwd and long voice fixes #83, feat: favourite directories with a star in the path line #84, fix(deps): clear the high-severity audit advisories #85, fix(deps): override vulnerable minimatch in the packaging toolchain #86, feat(sidebar): close a workspace terminal from its sidebar card #87, feat(updates): prompt when a new release ships, with optional install #88 and the open-cwd launch hintsversions.txt, README release statusThis is the first release built with the updater (#88). It is also the first run of the new
latest.yml/latest-linux.ymlupload and checks inrelease.yml, so watch that job.🤖 Generated with Claude Code