Repository navigation
Conventional Comments Toolkit 1.0.0-beta.19
Pre-release1.0.0-beta.19 — October 31, 2026
When a part of the page is not recognised, the journal now records what the page showed at that moment, and the whole diagnostic downloads as an archive to attach to a bug report; editing a comment on GitHub no longer writes a false alarm.
✨ Features
-
The journal records what the page showed when something was not recognised. A line now says how far the extension got in the page, what it found there instead and when it happened; for the merge button and the PR creation date, it also says whether the element showed up a moment later. That is often enough for a developer to find the cause without asking you to capture the page. It keeps the page's structure and interface attributes only, never the page's text: not what you type, not comments or code. Attribute values are kept, though, and an interface label such as a button's accessible name, or an account name, can appear in them. It stays on your device.
-
A skeleton of the page is kept from the moment of the problem, when your browser and storage allow it. It is the page's structure, without the page's text, taken at the instant something failed rather than afterwards. Skeletons take at most 1 MB of the extension's storage, the oldest go first, and the extension never lets them crowd out anything else. When the browser cannot compress a skeleton or storage is short, none is stored: the journal line still names it, and the archive simply lacks that file.
🔧 Changed
- "Copy the whole log" becomes "Download the diagnostic (.zip)". The archive holds the journal, the skeletons still stored and a README that says what each file contains; attach it to an issue. Copying a single line works as before, and "Clear the log" now clears the skeletons too. The archive holds the addresses of the pages involved, which on an enterprise server name a repository and a review: read the archive before you share it, keeping in mind that an interface label can name an account.
🐛 Bug fixes
- Editing a comment on GitHub no longer writes a false alarm to the journal. A hidden field of GitHub's "Reference in new issue" dialog, which is not a comment field, was reported as a comment field not recognised although nothing was wrong.
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.19-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.19-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
0c962ca2a303f87330d03086f22d61db123139d91a92ab2832bb881f281a0423 conventional-comments-toolkit-1.0.0-beta.19-chromium.zip
0b078c03a839cc5c0efd745a7d4992950e84a6e437ae72cc16e16f537bf6fc9a conventional-comments-toolkit-1.0.0-beta.19-firefox.zip
Construit depuis 996a6fda0079d778731b8e4dbc429710c1291693 — bundle vérifié sans code distant (§10), manifestes MV3 Chromium et Firefox chargeables, suite de tests rejouée.