Skip to content

Releases: Reefact/conventional-comments-toolkit

Conventional Comments Toolkit 1.0.0-beta.12

Choose a tag to compare

@github-actions github-actions released this 08 Sep 09:34

1.0.0-beta.12 — September 8, 2026

The guided tour is legible at last — the page behind it really does go dark, and its card sits above it instead of blending in — and the "Status" section says what it observed rather than what that might mean.

✨ Features

  • The "Status" section tells you what it is for. It was the only section of the options page whose heading had nothing under it, so you had to read the two lines it shows to work out what it covered.

🐛 Bug fixes

  • The guided tour now dims the page around the part it is pointing at. In the dark theme it barely dimmed at all — a dark veil over an already dark page changes almost nothing — so the tour looked like it was highlighting nothing, and its card, which had the same colour as the panels behind it, read as one more panel rather than as something floating above them. The rest of the page now goes properly dark in both themes, and the card carries a drop shadow you can actually see; in the dark theme it is also a lighter surface than the panels behind it.
  • The "Status" section no longer suggests the extension changed your pages. It reported "pages whose structure changed under it", which reads as an accusation and, either way, claims more than the extension knows: what it records is that one of its selectors found nothing on the page. That can mean the page changed — or simply that the element is legitimately absent, like the merge button on a closed pull request. Both the section and the tour step now report what was actually observed.

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.12-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.12-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. La source de vérité reste le compagnon serveur (composant B).

Empreintes SHA-256

993fbb1871f211001e32cb43e7d9c1fc7758e2ee047f144de868c8939ef28af5  conventional-comments-toolkit-1.0.0-beta.12-chromium.zip
196aa29ab1e4996da81d05935692a59c078c4bb914987e3b7521b5c0161948f7  conventional-comments-toolkit-1.0.0-beta.12-firefox.zip

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

Conventional Comments Toolkit 1.0.0-beta.11

Choose a tag to compare

@github-actions github-actions released this 08 Sep 07:00

1.0.0-beta.11 — September 8, 2026

You now authorize every platform the same way — github.com included — so the extension asks before it works anywhere, and you can revoke that access at any time.

✨ Features

  • You choose where the extension works, and you can change your mind. github.com used to be built into the extension: active from the moment you installed it, with no way to revoke that access from the extension itself. It now goes through the same one-click authorization as every other platform, and every domain you have allowed carries a "Withdraw" button. Domains authorized by your organisation's policy stay as they are — that is not this screen's call.
  • The options page opens automatically the first time and offers you a guided tour. It introduces each section and explains what it is for; you can skip it at any point, close it with Escape, and it never comes back on its own. A "Replay the guided tour" button in the page header replays it whenever you want.
  • The options page now speaks French or English, like the rest of the extension. It stayed in French whatever you had chosen — so someone who had set the interface to English saw English everywhere except on the settings page where they made that choice. The new language now takes effect immediately, rather than at the next reload.

🐛 Bug fixes

  • GitHub Enterprise Cloud with data residency now works at all. A domain allowed as *.ghe.com was recorded under a mangled name, so the extension never recognised the pages it was authorized for. This is older than this release, and no test could see it: the flaw only appears in a browser, and the tests ran where it does not.
  • You no longer need to reload the tab you came from. Allowing a domain from the options page left that tab inert — precisely the tab you were about to use. The extension now activates there immediately.
  • A failed revocation is no longer reported as successful. When the browser refuses to remove an access, the screen used to report the domain as unconfigured afterwards — an anomaly it had created itself, while the access was in fact still granted. It now changes nothing and says why.
  • Revoking access from chrome://extensions now also clears the saved platform. The platform you had chosen for that domain used to stay behind, so granting it again the same way silently restored the old choice instead of asking you.
  • The extension no longer loads itself on pages it does not support. If you had granted access to all sites from the browser's own controls, its code was injected into every https page, where it could do nothing anyway. Patterns that do not identify a concrete host no longer appear as domains to configure either.
  • The interface no longer appears twice on a page covered by two of your authorizations, and a tab left open for a long time no longer accumulates a copy of the extension's stylesheet.

🔧 Changed

  • After this update, the extension is silent on github.com until you allow it. One click on "Activate" in the options page is enough. This step cannot be automated: the browser only grants a site permission after an explicit action from you. The page opens by itself to say so — but only if the update left you with no working domain at all; if you already had another one configured, the extension keeps working there and nothing tells you it is no longer active on github.com.
  • The options screen is rebuilt around the actual access states: domains the extension already knows, where one click both authorizes and classifies; any other domain, where you say which platform it belongs to before granting; the list of what is configured; and, only when it is not empty, the domains you allowed from the browser rather than from this screen, where the extension is not active yet.
  • Each visualstudio.com organisation is now authorized individually through the free-form field, with Azure DevOps pre-filled. The catalog entry it replaces asked for every organisation on those legacy addresses at once, when a workstation uses one.

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.11-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.11-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. La source de vérité reste le compagnon serveur (composant B).

Empreintes SHA-256

ad7734deba3d1fa8cd567a899c596e2edf8695bb869e71ba5af91ece3a611fab  conventional-comments-toolkit-1.0.0-beta.11-chromium.zip
70b99ff1229821787ecb1931dc2e3492fd64b0c6e3c22c6b07e7568390d9a75c  conventional-comments-toolkit-1.0.0-beta.11-firefox.zip

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

Conventional Comments Toolkit 1.0.0-beta.10

Choose a tag to compare

@github-actions github-actions released this 05 Sep 14:10

1.0.0-beta.10 — September 5, 2026

GitHub rewrote its "Files changed" view, and the extension had gone quiet on it: this release brings the whole toolkit back there, and makes diagnostics speak the language you picked.

🐛 Bug fixes

  • The comment tooling works again on GitHub's rewritten "Files changed" view. GitHub now serves that page at /pull/N/changes, where the extension recognised nothing: no label toolbar, no quick entry, no live validation, no badges on published comments — precisely where a blocking issue: counts most. All of it is back. A page carrying an editing surface the extension does not recognise now leaves a diagnostic entry too, instead of being inert and silent at once.
  • Under enforce, a non-compliant comment can no longer be published from that view. Neither by clicking Reply under a diff line, nor from the "Finish your comments" panel of a batch review, whose buttons sit in the overlay rather than beside the field. Only the keyboard path was guarded before, so a comment the extension had flagged could still be sent with a mouse.
  • Editing the root comment of a thread is validated again there. It was taken for a reply, which the default configuration exempts from validation — an issue: root could be edited into anything without the extension looking. Published comments get their badges back too, resolved threads read as resolved instead of unknown, and the pull request banner shows the authors and bodies it was missing.
  • A blocking label in a review summary is warned about again. In the "Finish your comments" body, issue: reported everything except the one warning that matters there: nobody can resolve a review summary, so it carries no blocking state. The same text in the conversation box has always said so.
  • The Preview tab shows badges on that view too. Writing issue: … in a composer on …/changes and switching to Preview rendered the prefix in plain text, where the same switch on the conversation page showed the badge.
  • The composer looks like itself again on that view. The toolbar sits above the field instead of being folded into a narrow column beside it, the compliance outline around the field is visible instead of clipped by the container that wraps it, and the toolbar, the field and the verdict pill are no longer squeezed against the frame that surrounds them. That spacing survives a trip through the Preview tab as well, which used to strip it until the composer was closed.
  • Diagnostic messages now follow the language you picked in the options page. A French interface could show Conforme, avec avertissements above This comment is blocking but has no discussion: that one line took its language from the repository's configuration rather than from your own preference. Label names (issue, praise…) and diagnostic codes (E-NO-LABEL, W-NO-DISCUSSION…) stay untranslated in both languages — they are identifiers, and the check output names them the same way.

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.10-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.10-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. La source de vérité reste le compagnon serveur (composant B).

Empreintes SHA-256

7b6d94e00e668801d1a5488d6678227c6283eb9e4b15833dbb41912fe56498ae  conventional-comments-toolkit-1.0.0-beta.10-chromium.zip
ea126785415192a7b9f31dc062aa9fd25d9472dee69598368634fd7e0fb88d9e  conventional-comments-toolkit-1.0.0-beta.10-firefox.zip

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

Conventional Comments Toolkit 1.0.0-beta.9

Choose a tag to compare

@github-actions github-actions released this 04 Sep 11:27

1.0.0-beta.9 — September 4, 2026

The extension no longer gets in the way of a pull request's own description, no longer goes quiet on a page that starts out empty, and finally says why when it cannot read your configuration.

✨ Features

  • When the configuration cannot be read, the options page now shows why — HTTP 429, a TypeError, a 404 that cannot be told from a refusal — together with the level it came from, instead of the bare word unreachable. The reason stays on your machine: it goes to chrome.storage.local and nowhere else.

🐛 Bug fixes

  • A pull request's own description is no longer treated as a review comment. The convention says nothing about it, yet the label toolbar was drawn on it — and under enforce the submit guard applied to its Update button, so a description without a label: prefix could not be saved at all. Badges are gone from it too. Where a future GitHub rendering names things differently, the description simply behaves as it did before, never worse.
  • The "Configuration unread" banner no longer appears on every repository. Every configuration read was failing before it left the browser, on public and private repositories alike, with a configuration file and without — so the extension always fell back to its degraded state. Repository-level configuration is readable again.
  • A page that had nothing to show no longer stops watching after five seconds. On the Files changed view of a pull request with no thread yet, the first comment posted afterwards got neither badge nor banner until a full reload — and so did coming back to Conversation from another tab of the same pull request. A page that has not moved is still left alone; one that gains a comment, a thread or a published result is rendered again.
  • A missing page is no longer read as a hidden one while you are signed in. GitHub masks a private resource as missing, and the extension trusted a page-scraped "private" signal that could be wrong on a public repository. Two independent signals must now agree before a 404 means an unreadable configuration.
  • The selector degradation journal is usable again. Visiting a single closed pull request filled all fifty lines with one entry and evicted every real degradation, because the merge button it looks for is legitimately absent there. One line per selector now — and the opt-in telemetry, which inflated for the same reason, with it.

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.9-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.9-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. La source de vérité reste le compagnon serveur (composant B).

Empreintes SHA-256

9a9b03eba92d484effd84e8d2a86d01292afc0a5fb74ea88ca04479ce09cdf02  conventional-comments-toolkit-1.0.0-beta.9-chromium.zip
7bb7f2e761201d7e81b520f379e68a1759d7476ddd21fba5f3be6e1d6126e158  conventional-comments-toolkit-1.0.0-beta.9-firefox.zip

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

Conventional Comments Toolkit 1.0.0-beta.8

Choose a tag to compare

@github-actions github-actions released this 04 Sep 07:39

1.0.0-beta.8 — September 4, 2026

Published comments read like titles — badges, then the subject in bold on the same line — and three ways a comment could silently lose its badges are closed.

✨ Features

  • A published comment's subject is now shown in bold on the badge line, to the right of the badges, instead of starting on the line below them. A blank line separates it from the rest of the comment. Where the subject cannot be delimited safely — inline formatting carrying its own line break, for instance — the previous layout is kept rather than risking a wrong cut.

🐛 Bug fixes

  • Editing a comment no longer strips its badges. The platform rewrites the rendered body on an update; the badges and the structured prefix went with it, and nothing brought them back until you reloaded the page.
  • The structured prefix is re-hidden when the platform restores it on its own, which previously left issue (blocking): visible in the middle of an otherwise decorated comment.
  • Leaving a pull request, or switching the extension to mode: off, no longer leaves part of a comment invisible. The badges were removed but the prefix stayed hidden, so an extension that declares itself inactive went on concealing text you had written.

🔧 Changed

  • The composer toolbar now stacks two rows — labels, then decorations — so a narrow window or a side panel can no longer put a label button next to a decoration segment as if they were one kind of control.
  • Label buttons no longer show their icon; badges on published comments still do. The buttons share one row's width, where an icon costs every other button; a badge stands alone at the head of its comment, where it costs nothing.

Releve complet, contraintes et cas limites compris : CHANGELOG.md. Notes de version en francais : 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.8-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.8-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. La source de vérité reste le compagnon serveur (composant B).

Empreintes SHA-256

838a3f825df4aa24da53f149e7b260c1531b8a05537d7f7887d7e455df662f83  conventional-comments-toolkit-1.0.0-beta.8-chromium.zip
637fb379f031050f9f92837a23962a2d87d70ec95c4cf22c1ebe024ea0aab012  conventional-comments-toolkit-1.0.0-beta.8-firefox.zip

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

Conventional Comments Toolkit 1.0.0-beta.7

Choose a tag to compare

@github-actions github-actions released this 03 Sep 21:50

1.0.0-beta.7 — September 3, 2026

The structured prefix disappears from a published comment — the badges already say it — except everywhere saying it twice was the safer answer.

✨ Features

  • issue (blocking): no longer appears in a published comment: the badges carry that information, so the text is hidden on screen. On screen only — the comment stored on the platform is untouched, and reopening the edit form shows it in full.
  • Where the badges would not say the same thing, the text stays: a decoration you wrote that the configuration rejects, a case or punctuation defect the tool is meant to flag, decorations folded into a +N badge. Hiding those would erase the only trace of what you actually typed.
  • A line that merely looks like a prefix — inside a code block, a quote, a list, a heading, a table or a <details> summary — is left alone.

🔧 Changed

  • Every default label now has an icon and a colour, contrast-checked against WCAG 1.4.11.

Releve complet, contraintes et cas limites compris : CHANGELOG.md. Notes de version en francais : 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.7-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.7-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. La source de vérité reste le compagnon serveur (composant B).

Empreintes SHA-256

513b08ed92bad48074ca2775ef60c5b6b749f478a1beea6b81ebdd4b9cf845be  conventional-comments-toolkit-1.0.0-beta.7-chromium.zip
82058e4616b9bb4c9dceeed4eae60fd0ef5e232e32f3948132da989a01b4854f  conventional-comments-toolkit-1.0.0-beta.7-firefox.zip

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

Conventional Comments Toolkit 1.0.0-beta.6

Choose a tag to compare

@github-actions github-actions released this 03 Sep 13:08

1.0.0-beta.6 — September 3, 2026

Decorations get badges of their own, and the whole display follows a configuration change while you watch.

✨ Features

  • Each decoration on a published comment now gets its own badge beside the label: red where it forces the blocking character, green where it forces non-blocking, dashed where the decoration is declared nowhere.

🐛 Bug fixes

  • Changing the configuration now refreshes what is already on screen — including on a tab you left open on a pull request. A label disabled mid-review loses its badge instead of keeping one for a state that no longer exists.
  • A comment box you already had open follows that change too, including whether it blocks your submission. It went on applying the configuration captured when it opened, so an organisation switching from enforce to off left you blocked until you closed and reopened the box.

Releve complet, contraintes et cas limites compris : CHANGELOG.md. Notes de version en francais : 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.6-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.6-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. La source de vérité reste le compagnon serveur (composant B).

Empreintes SHA-256

2750adac4a629dfb005e7840bc346c977e24c685aee9efdafe6516102fc15b71  conventional-comments-toolkit-1.0.0-beta.6-chromium.zip
1aad9ed5b6c328e319fcfc71a315955e23f465b5738ec57b8355e7f188c686c8  conventional-comments-toolkit-1.0.0-beta.6-firefox.zip

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

Conventional Comments Toolkit 1.0.0-beta.5

Choose a tag to compare

@github-actions github-actions released this 02 Sep 01:46

1.0.0-beta.5 — September 2, 2026

Repository configuration is readable again on private repositories.

🐛 Bug fixes

  • The extension reads your repository's and organisation's configuration on private repositories again. The read follows a redirect the browser refuses to authenticate; credentials are now dropped on that hop alone, so the file stays readable without asking you for any host permission.
  • A configuration file that could not be read for lack of a session is no longer taken for a file that does not exist — which silently applied the wrong configuration.

Releve complet, contraintes et cas limites compris : CHANGELOG.md. Notes de version en francais : 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.5-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.5-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. La source de vérité reste le compagnon serveur (composant B).

Empreintes SHA-256

3ad5070774ba3897254643b23015970131d5912b1cf69dbf0cf5be1d99cf06e9  conventional-comments-toolkit-1.0.0-beta.5-chromium.zip
7ffc33ee366c698cb81d8a10ab1f4d05baa10742a03059c7605a7079d1124f49  conventional-comments-toolkit-1.0.0-beta.5-firefox.zip

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

Conventional Comments Toolkit 1.0.0-beta.4

Choose a tag to compare

@github-actions github-actions released this 01 Sep 15:00

1.0.0-beta.4 — September 1, 2026

The decoration selector says what your comment carries, not what you last clicked.

🐛 Bug fixes

  • The decoration selector now reflects the comment itself. A decoration you removed by editing the text, or one that left with a label the configuration disabled, no longer stays lit in the toolbar.

Releve complet, contraintes et cas limites compris : CHANGELOG.md. Notes de version en francais : 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.4-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.4-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. La source de vérité reste le compagnon serveur (composant B).

Empreintes SHA-256

8195ecef9a25a278ebf82cce104e4c84728f4095449f1508aabc1558a2a26234  conventional-comments-toolkit-1.0.0-beta.4-chromium.zip
97a985d002ee346dd23451b474b86e3df0fefa27df59be602f0cfce916133617  conventional-comments-toolkit-1.0.0-beta.4-firefox.zip

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

Conventional Comments Toolkit 1.0.0-beta.3

Choose a tag to compare

@github-actions github-actions released this 01 Sep 12:16

1.0.0-beta.3 — September 1, 2026

Two permissions dropped from the manifest, telemetry that only exists if you ask for it, and the material for a store submission.

🔧 Changed

  • activeTab and the permanent github.com host permission are gone. Hosts are granted optionally instead — the extension asks for what it needs, when it needs it.
  • The pull-request banner is a summary, not a merge gate. The verdict belongs to the platform's own check, which is already red and already blocking; restating it here devalued both.

✨ Features

  • Optional telemetry, off unless you turn it on, bound to the endpoint you consented to and configured by your organisation's policy rather than by a repository file.
  • The version shown in chrome://extensions now distinguishes pre-releases: 1.0.0-beta.1 and 1.0.0-beta.2 no longer both read 1.0.0.

🐛 Bug fixes

  • On GitHub Enterprise Server and self-hosted Azure DevOps Server, granting the host permission now actually gives you the extension. The grant succeeded and nothing appeared: no adapter was ever built for that host. Which platform a host serves is now recorded with it, so a GHES domain and an Azure DevOps Server one are told apart.
  • An organisation configuration hosted outside your platform is readable again. It never was: the page's own CORS policy blocked it whatever permission you had granted, leaving the extension permanently degraded and judging on two configuration levels where the server uses three.

Releve complet, contraintes et cas limites compris : CHANGELOG.md. Notes de version en francais : 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.3-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.3-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. La source de vérité reste le compagnon serveur (composant B).

Empreintes SHA-256

589d849ba94cb20bbce4eccbb96877865ecfaa8112fb6fd130e49bd77ef6758f  conventional-comments-toolkit-1.0.0-beta.3-chromium.zip
7efb3aaab269ae1f1f21ec38193e7668a9249d5270c86ec7314f6b556505e0ad  conventional-comments-toolkit-1.0.0-beta.3-firefox.zip

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