Skip to content

Rename to FastStream for Firefox - #676

Closed
Nawid3333 wants to merge 5 commits into
mainfrom
feature/rename-faststream-for-firefox
Closed

Nawid3333 wants to merge 5 commits into
mainfrom
feature/rename-faststream-for-firefox

Conversation

@Nawid3333

Copy link
Copy Markdown
Owner

Renames the add-on to FastStream for Firefox and points every link at the renamed repository Nawid3333/FastStream-for-Firefox. Draft: nothing here is merged or released without your word.

Before merging: rename the repository first

The order matters (also in docs/notes/build-and-release.md):

  1. Rename the repository on GitHub: Settings → General → Repository name, or gh repo rename FastStream-for-Firefox. GitHub redirects the old URLs from then on, so every installed copy keeps finding its updates through the old update_url.
  2. Then merge this PR. Its release is the first whose manifest asks the new update_url.

If this PR is merged first, its release asks an update_url under a repository name that does not exist yet, and its copies find no update until the rename. Never create a new repository named FastStream under this account: that would end the redirects for copies installed before the rename.

What changes

  • extension_name is "FastStream for Firefox" in all 16 locales (combined-locales.json too). The gecko id thanatus@Nawid is unchanged, so Firefox treats it as the same add-on and keeps its settings.
  • Every Nawid3333/FastStream link now points at the new name: build.mjs update_url, the update checker, options page, error dialog, problem log, perms/welcome pages, package.json, the release tools, and the release title in release.yml.
  • README (+ pt-BR): what the fork is, that it is not affiliated with upstream, that it ships from GitHub and not from AMO, and a License section (no open-source license; LICENSE.md is upstream's, unchanged).
  • tools/check-update-path.mjs accepts a link under the former name (FORMER_REPOS). The last release before the rename still links its xpi there, and the failsafe would otherwise open a false "Update path broken" issue until the next release. The xpi is still downloaded (redirects followed, as Firefox does) and its hash and signature checked.
  • The zips are now named firefox-github-faststream_for_firefox-<version>.zip. The workflows' firefox-github-*.zip globs match both names.

Checked

  • pnpm run lint, pnpm run typecheck: clean.
  • pnpm exec vitest run: 229 files passed, 1 skipped; 3552 tests passed, 6 skipped. The new checkUpdatePath test passes too.
  • pnpm run build:keep: AMO manifest has the new update_url and the same id.
  • lint:amo, lint:github: 0 errors / 0 warnings / 0 notices. addons-linter has no rule about names, so AMO's server-side name check runs only at the next signing. " for Firefox" follows Mozilla's naming pattern.
  • git grep "Nawid3333/FastStream" finds only the new name, plus the deliberate FORMER_REPOS entry.

Not changed on purpose: the short name "FastStream" in UI text, the tag messages "FastStream " (a workflow test pins them), and upstream's logo.

🤖 Generated with Claude Code

Nawid3333 and others added 5 commits November 13, 2026 16:39
…ry rename

extension_name is "FastStream for Firefox" in all 16 locales (the brand, in the
"<Name> for Firefox" form Mozilla's add-on policy asks for), combined-locales.json
updated by hand. Every link to this repository now points at
Nawid3333/FastStream-for-Firefox: the AMO build's update_url (same
/releases/latest/download/updates.json path), the update checker's package.json URL,
the issue links, the permissions and welcome pages, package.json and the release tools.
The GitHub release title says "FastStream for Firefox". The gecko add-on id is
unchanged, so installed copies keep updating as the same add-on.

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

README (and its Portuguese copy) now says plainly what this is: a Firefox-only
fork of Andrew S's FastStream, building on his code, not affiliated with or
endorsed by him, released from GitHub and not listed on addons.mozilla.org. A
License section says the fork claims no open-source license and LICENSE.md is
upstream's, unchanged. The privacy policy, the mpv guide, the uninstall page,
the AMO reviewer notes (the zip is now firefox-amo-faststream_for_firefox-*.zip)
and the maintenance docs link Nawid3333/FastStream-for-Firefox.
build-and-release.md records the rename and what it means for installed copies.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The unit tests and the workflow fixtures name Nawid3333/FastStream-for-Firefox,
and auto-release-shipped's builds are firefox-*-faststream_for_firefox-*.zip, the
name web-ext now derives from "FastStream for Firefox".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
lint:amo reports 0 errors, 0 notices and 0 warnings on the renamed build
(measured 2026-11-13); the notes still promised 3.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…er name

After the GitHub rename, the last release made before it still links its xpi under
Nawid3333/FastStream, which GitHub redirects. The failsafe (every 3 hours, from main) compared
the link with the new GITHUB_REPOSITORY only and would have opened "Update path broken" until
the next release. FORMER_REPOS lists the old name; the xpi is still downloaded (redirect
followed, as Firefox does) and its hash and signature checked. The rename note says in which
order to rename the repository and merge.

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

Copy link
Copy Markdown
Owner Author

Folded into the test branch test/all-prs (347a3b6), which carries every open pull request except #634 (mpv) and goes to main as one merge after the owner's test. Closed so that only main, mpv-update and the test branch remain. The rename is in it: rename the repository on GitHub before that merge (see docs/firefox-optimization-ui-review.md, section 7).

@Nawid3333 Nawid3333 closed this Nov 14, 2026
@Nawid3333
Nawid3333 deleted the feature/rename-faststream-for-firefox branch November 14, 2026 15:08
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