Skip to content

chore(release): prepare v1.1.0 - #89

Merged
SPhillips1337 merged 1 commit into
mainfrom
release/v1.1.0
Nov 11, 2026
Merged

SPhillips1337 merged 1 commit into
mainfrom
release/v1.1.0

Conversation

@SPhillips1337

Copy link
Copy Markdown
Contributor

Bumps the version to 1.1.0 and adds its release notes. After this merges, an annotated v1.1.0 tag on main triggers release.yml. That workflow checks package.json matches the tag, builds the Windows and Linux assets, and publishes the GitHub release with CHANGELOG.md as the notes.

This is the first release built with the updater (#88). It is also the first run of the new latest.yml / latest-linux.yml upload and checks in release.yml, so watch that job.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

@amazon-q-developer amazon-q-developer Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

This is a standard release preparation PR bumping the version from 1.0.0 → 1.1.0. All five changed files are consistent:

  • package.json and package-lock.json both reflect "version": "1.1.0".
  • CHANGELOG.md has a well-formed 1.1.0 section matching the PR description's feature list.
  • README.md correctly updates the "Release status" paragraph.
  • versions.txt appends the 1.1.0 entry.

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.

@SPhillips1337
SPhillips1337 merged commit 93795c6 into main Nov 11, 2026
3 checks passed
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