Repository navigation
Chore: release 1.1.0 - #233
Merged
Merged
Conversation
1.0.2 added new features (reverse-sync, --pages, --jsonSummary, --fullPull), so under semver it is a minor release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jules-exel
approved these changes
Oct 2, 2026
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
2 participants
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.
Re-releases 1.0.2 as 1.1.0. 1.0.2 added new features (
reverse-sync,--pages,--jsonSummary,--fullPull), so under semver it should have been a minor release.Only
package.jsonandpackage-lock.jsonchange. The code is the same asv1.0.2(29d1ad8).After merge:
v1.1.0on main so the npm-publish workflow publishes it.npm dist-tag add @agility/cli@1.1.0 latestv1.1.0with the same notes as v1.0.2, and point the v1.0.2 release at 1.1.0.npm deprecate @agility/cli@1.0.2 "Re-released as 1.1.0".🤖 Generated with Claude Code