Skip to content

Conventional Comments Toolkit 1.0.0-beta.18

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 30 Oct 13:41
· 265 commits to main since this release

1.0.0-beta.18 — October 30, 2026

The settings page's journal says what went wrong in a sentence, records the extension's own errors and can be copied for a bug report; filtering threads by label works on GitHub again.

✨ Features

  • The journal on the settings page can be copied for a bug report. Each line has a copy icon, and a button copies the whole journal. What you paste into an issue carries the extension version, your browser and what a developer needs to reopen the problem. Page content is not collected as a field of its own, but the address of the page is in the report, and the message and details of an error can contain snippets of what the extension was handling. Read the whole report, not only the address, before you paste it into a public issue.

  • Each journal line says what went wrong in a sentence. "Merge button not found: it cannot be greyed out" instead of merge-button, with a level, WARN or ERROR. The technical name stays in the copy.

  • The extension now records its own errors. A crash used to leave no trace. It now shows up as an ERROR line that says what the extension was doing, and the details are in the copy. They stay on your device.

🐛 Bug fixes

  • Filtering threads by label hides them on GitHub again. GitHub forced every thread to stay visible, so a thread you had filtered out stayed on screen. Selecting praise no longer leaves an issue thread showing.

  • Clearing the filter gives a thread its original display back. A thread that already had a forced display setting lost it once the filter was cleared, and GitHub's own styling could override it again.

Relevé complet, contraintes et cas limites compris : CHANGELOG.md. Notes de version en français : docs/release-notes-1.x-fr.md.


Installation sans chaîne de build

Aucun Node, npm ni Git requis : télécharger l'archive, la décompresser, charger le dossier.

Navigateur Archive Comment charger
Chrome, Edge, Chromium conventional-comments-toolkit-1.0.0-beta.18-chromium.zip chrome://extensions → Mode développeur → Charger l'extension non empaquetée → le dossier décompressé
Firefox conventional-comments-toolkit-1.0.0-beta.18-firefox.zip about:debugging#/runtime/this-firefox → Charger un module temporaire → le manifest.json du dossier décompressé

Décompressez ailleurs que dans le dossier des téléchargements : Chromium relit ce dossier à chaque démarrage, le supprimer désactive l'extension. Sous Firefox, un module temporaire est retiré à la fermeture du navigateur.

Chaque archive contient un INSTALLATION.txt reprenant ces étapes (FR et EN). Guide détaillé : docs/extension-setup-fr.md (EN : docs/extension-setup-en.md).

L'extension démarre en mode assist : elle aide et signale, elle ne bloque jamais l'envoi. Aucun vérificateur (composant B) n'est encore livré : un commentaire n'est contrôlé que dans le navigateur des personnes ayant installé l'extension.

Empreintes SHA-256

5f31e1a603c6c038e5b69dd8bd569d291ca2c6b04c0bf26b0b9ae3bbf672f4b1  conventional-comments-toolkit-1.0.0-beta.18-chromium.zip
bc4e38f048e98c3d4b42b4f9715526664a855bfd1324ebabf0832c4b09c6403d  conventional-comments-toolkit-1.0.0-beta.18-firefox.zip

Construit depuis f79e4ed2bb8d0df080c3f90beeca07daf94d666a — bundle vérifié sans code distant (§10), manifestes MV3 Chromium et Firefox chargeables, suite de tests rejouée.