Repository navigation
chore: sync release v1.1.0 to develop - #125
Merged
Merged
Conversation
The Dependabot bump (PR #86) upgraded @typescript-eslint/eslint-plugin to ^8.60.0 in package.json but did not regenerate the lock file, so npm ci installed a stale version that lacked the no-useless-assignment rule. Regenerated the lock file to pin the plugin at 8.60.0, then fixed the 20 errors it surfaced. Two config menu loops assigned running = false before an immediate return - simplified to while (true) with exits via return only. Eighteen redundant as-cast assertions in the commitlint-sync and constants test files were removed since TypeScript already infers the correct types.
Patch release bringing accumulated develop work to main. The published CLI behaves identically to 1.0.0 - no runtime code changed. Corrects the LICENSE copyright holder to Maksym Bukator. Adds knip unused-code detection to CI and the pre-push hook, broadens the Prettier format check to cover docs and test files, updates development dependencies to resolve advisories in vite, flatted, and js-yaml, and retargets Dependabot at the develop branch.
Patch release. No src/ changes; the CLI behaves the same as 1.0.1. Changed: - Raise the declared minimum Node.js version from >=18 to >=22.13.0. v1.0.1 already required Node >=22.12.0 through commander@15, so this corrects the metadata. 22.13.0 is the highest floor among production dependencies (@inquirer/prompts 8.x) - Update production dependencies: chalk 6.0.1, execa 10.1.0, @inquirer/prompts 8.7.3, ora 9.4.1 - Run CI and release workflows on Node 22 instead of 20 - Skip TypeScript major bumps in Dependabot until typescript-eslint supports TypeScript 7 - Bump actions/setup-node from 6 to 7 - Replace the static README logo with an animated banner Security: - Resolve 17 dev-dependency advisories, 15 of them Dependabot alerts (fast-uri, js-yaml, postcss, smol-toml, brace-expansion, vitest, @humanfs/node, source-map-js). Development tooling only; the published package was not affected
- Bump version 1.0.2 -> 1.1.0 - Add the 1.1.0 CHANGELOG entry for custom themes
# Conflicts: # CHANGELOG.md # package-lock.json # package.json
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.
🎯 Overview
Back-merges the v1.1.0 release into develop to complete the release cycle. It brings the release metadata created on the release branch (version and changelog) back into develop, so the two branches stay reconciled.
✨ Changes
Release sync
Reconcile develop with the tagged release:
🔧 Technical Details
Files Modified:
package.json/package-lock.json- version 1.1.0CHANGELOG.md- 1.1.0 entryThis branch is the release branch itself. It is based on the current develop tip (
a03bf6b), so the diff is only the release metadata. Its tree is identical to main at3a3faec(tagv1.1.0).📋 Testing
How to Test:
Expected Behavior:
The version is 1.1.0, and develop matches main after merge.
🔗 Related Issues
Relates to #123
✅ Checklist
📝 Notes
No functional changes. Dependabot #121 stays open against develop for the next release.