chore: release - #156
Merged
Merged
chore: release#156
Conversation
stats-forge-helper
Bot
force-pushed
the
changeset-release/main
branch
6 times, most recently
from
September 25, 2026 06:09
4b61f7c to
41028e4
Compare
stats-forge-helper
Bot
force-pushed
the
changeset-release/main
branch
from
September 25, 2026 06:13
41028e4 to
ef53762
Compare
marcalexiei
approved these changes
Sep 25, 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
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@stats-forge/github-stats-forge-cli@0.6.2
Patch Changes
#171
8d271e8- build: accept any compatible @InQuirer releaseThe six prompt packages were pinned exactly, so a patched release reached an install
only after a release here. A caret lets one in at install time, as core's
zodalready does.#130
42951eb- build: update @inquirer/checkbox to 5.2.5#130
42951eb- build: update @inquirer/confirm to 6.3.2#130
42951eb- build: update @inquirer/input to 5.1.6#130
42951eb- build: update @inquirer/number to 4.2.3#130
42951eb- build: update @inquirer/password to 5.2.2#130
42951eb- build: update @inquirer/select to 5.2.5Updated dependencies [
c056ec3,33daaa2]:@stats-forge/github-stats-forge-core@0.8.2
Patch Changes
#169
c056ec3- fix: resolve a language's color whatever its caseWakaTime and gist languages are not always spelled the way linguist spells them,
and a casing difference drew the default gray instead of the language's brand color.
#157
33daaa2- feat(core): update language colorsRegenerated from the upstream linguist languages file.
@stats-forge/github-stats-server@0.4.6
Patch Changes
dbc8c1e- docs: pin the stats-forge/github-stats-forge-action example to v0.8.1c056ec3,33daaa2]: