Repository navigation
[pull] main from Alishahryar1:main - #244
Merged
Merged
Conversation
## Why FCC currently installs from GitHub's moving main archive. Publish versioned packages to PyPI after merge and enforce which changes require a release so the installer can use published versions consistently. ## How - Require exactly one patch, minor, or major increment from the target branch for changes under `assets/`, `scripts/`, or `src/`, or to `.python-version`, `pyproject.toml`, or `uv.lock`. Forbid version changes for other-only PRs. Ignore only FCC's own version values when classifying metadata changes, and reject stale, skipped, noncanonical, or mismatched versions. Minor and major increments reset all lower components to zero. Multiple commits in a PR share one version bump. - Run the native Windows Muse lifecycle tests only on Windows, preserving both Windows PowerShell and PowerShell 7 coverage. - Fix browser-test synchronization: hold only the intended stale provider response, and wait for account-status route capture before releasing its response. - Run required `Version policy` in normal pull-request CI, including this PR. Keep strict up-to-date checks and FCC 6.2.64. Accepted scope: the check catches version mistakes. Changes to the checker or CI itself are reviewed like other repository code, rather than adding tamper-resistant enforcement. - Move dependency installation into the shared CI setup. Cache-warming and publishing jobs opt out, preserving their dedicated behavior. - Rename the cache workflow to `post-merge.yml`. Its three-platform cache matrix and independent Linux publishing job share one workflow queue with cancellation disabled. GitHub orders queued runs by arrival at the concurrency group. - Build and validate the exact merged commit's wheel and source archive, then publish changed versions through uv Trusted Publishing using the main-only `pypi` environment. Documentation-only merges skip publication. Rerun a failed release's original workflow to retry that commit. - Replace the installers' GitHub ZIP requirement with the PyPI package name, retaining force reinstall, package refresh, Python selection, voice extras, and backend options. Existing `fcc-update` commands already invoke these installers. - Accepted rollout choice: installations can briefly fail after this first merge until the first PyPI publication succeeds. There is no archive fallback. Later releases leave the previous published version available if publication fails. <!-- greptile_comment --> <!-- greptile_summary --> <h2><a href="https://app.greptile.com/api/retrigger?id=69241840"><picture><source media="(prefers-color-scheme: dark)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/RetriggerDark.svg?v=2"><source media="(prefers-color-scheme: light)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2"><img alt="Retrigger" src="https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2" align="right"></picture></a>Confidence Score: 5/5</h2> <!-- greptile-risk --> No outstanding findings block merging. <details open><summary>Summary</summary> The PR adds version-policy CI and post-merge PyPI publishing, updates installers to use the published package, and limits native Windows Muse lifecycle tests to Windows. No new findings remain. </details> <!-- greptile_confidence_score:5 --> <sub>Reviews (4) · Last reviewed commit: ["Limit native Windows Muse lifecycle test..."](https://github.com/alishahryar1/free-claude-code/commit/4dc704e93c20637ca7554b9475816afbd21af92b)</sub> <!-- /greptile_comment -->
![https://greptile-static-assets.s3.amazonaws.com/badges/RetriggerDark.svg?v=2"><source](https://greptile-static-assets.s3.amazonaws.com/badges/RetriggerDark.svg?v=2"><source){kind=link}
![https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2"><img](https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2"><img){kind=link}
pull
Bot
merged commit Sep 25, 2026
78a9364
into
Co-Contribute-OpenSource:main
10 of 11 checks passed
This branch had an error being deployed
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )