Skip to content

Releases

Conventional Comments Toolkit 1.0.0-rc.2

Conventional Comments Toolkit 1.0.0-rc.2 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Nov 03:15
v1.0.0-rc.2
d7ddd75

1.0.0-rc.2 — November 12, 2026

Two fixes to the thread filter on GitHub's new Overview page.

🐛 Bug fixes

  • On GitHub's Overview, the thread filter is no longer placed inside a thread. When the Comments section showed Unresolved or Mine, the filter's chips appeared in the middle of the first thread, between its code and its comment. They now sit above the first thread, as in All.
  • On GitHub's Overview, filtering by label hides the whole thread. A thread that did not match the chosen label lost its comments but kept its file name and code on screen, as an empty box. It now disappears entirely, and comes back when you choose all.

🔧 Changed

  • The reviewer skill installs Slugger under its new name. The tool that skills/review-pull-request uses to name review sessions is now published as Slugger instead of Slugger.Cli; the command is still slugger. An installation made under the old name keeps working, and the skill's setup step says how to move to the new 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-rc.2-chromium.zip chrome://extensions → Mode développeur → Charger l'extension non empaquetée → le dossier décompressé
Firefox conventional-comments-toolkit-1.0.0-rc.2-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. Elle ne bloque jamais la fusion d'une PR : un commentaire n'est contrôlé que dans le navigateur des personnes ayant installé l'extension.

Empreintes SHA-256

4d86d5880d294a199b179e45118e6f84242ab01dfe931457371f68bf4c92368d  conventional-comments-toolkit-1.0.0-rc.2-chromium.zip
05971c93ffdac341cee06f1248e7b2377f34f821f6286c4182d044050513166a  conventional-comments-toolkit-1.0.0-rc.2-firefox.zip

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

Loading

Conventional Comments Toolkit 1.0.0-rc.1

Conventional Comments Toolkit 1.0.0-rc.1 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 11 Nov 21:42
v1.0.0-rc.1
3371ce0

1.0.0-rc.1 — November 11, 2026

The release candidate for 1.0.0: GitLab support, GitHub's new Overview page, a working Azure DevOps, review-session markers and a summary label; enforce now really blocks, after re-reading the configuration, and the verifier is retired for good.

✨ Features

  • GitLab (gitlab.com) is supported, without blocking. Merge requests on gitlab.com get the toolbar, the badges, the thread filter and the banner. Enable gitlab.com from the settings page, like any other site. The extension cannot read a repository's configuration on GitLab yet, so it never blocks a comment there. GitLab Self-Managed and Dedicated are not supported yet.
  • GitHub's new Overview page is supported. On the Overview, the extension did not recognise the new comment field, so nothing was blocked in enforce mode, and many comments got no badges. Both the Overview and the classic Conversation page now work. The banner sits under the pull request header, and the thread filter above the list of threads.
  • Review-session markers. A line [session:<id>] in a comment says which review session wrote it, so that the comments of several agents or several runs can be told apart. The extension hides the line and shows a discreet 🤖 session: <id> at the bottom of the comment; the marker never affects validation. Add a description after an em dash, [session:<id> — *<sentence>*], and it appears when you hover the mention. Two markers in one comment show #ERROR and a warning that never blocks.
  • A summary label to recap a review pass. summary (📋, typed as ?sum) says what was checked and what is still open; it raises no point and answers none. It sits with reviewed in a new group of labels that say where a review stands, at the end of the toolbar's first row. A repository can add its own label to that group with "kind": "status".
  • Problems in your configuration are shown, in your language. When a key is unknown or retired, when the configuration is invalid, or when your organization's policy overrides a setting, the extension used to say nothing. It now lists these notices in the status pill and on the settings page, in English or French, naming where the problem comes from: your organization's policy, the organization's document or the repository's file. They inform; they never change whether a comment is accepted.
  • The journal records comment fields the extension could not fully understand. A field whose send buttons were not found, or that the extension placed by default without recognising it, now leaves a line in the settings page's journal, so a page the extension misreads can be reported.

🔧 Changed

  • In enforce mode, non-compliant comments are now blocked on every pull request. Until now, enforce only blocked pull requests created after an activation date that was not set by default, so most installations in enforce never blocked anything. That condition is gone: if your repositories use enforce, expect comments to be blocked after this update. Before blocking, the extension re-reads the configuration, so a repository just switched back to assist is not blocked: the button is released and you are asked to send again.
  • The verifier is retired, and its settings with it. The product reports the unresolved blocking threads of a pull request; it never blocks a merge, and no longer greys the merge button. The keys formatSeverity, overrideLabel, resolverOverrideGroup, activation and docUrl are no longer read, and are shown as unknown keys. The mode warn works as assist, with a notice saying the value is obsolete. If your configuration uses any of these, you can remove them.
  • The banner is collapsed by default and shows the count of unresolved blocking threads alone.
  • Azure DevOps is supported on dev.azure.com only. Organizations on {org}.visualstudio.com or on Azure DevOps Server are not covered.
  • If your configuration already defines a summary label, it needs one property to keep working as before. Your label now merges into the shipped one and becomes always non-blocking, so summary (blocking): is refused. Add "alwaysNonBlocking": false to restore it.
  • Telemetry label counts say what kind of label was used. If your organization collects telemetry, each label count now carries its kind — remark, status or reply — so that replies and recaps can be counted apart. Nothing else is added.

🐛 Bug fixes

  • Azure DevOps works. The extension had never worked on Azure DevOps; it is rebuilt from real pages. Comment fields, send buttons and threads are recognised, the live preview gets its badges, the toolbar follows the Azure DevOps theme, a blocked button looks disabled, and the repository's configuration is read, so enforce applies there.
  • Keyboard shortcuts no longer get around enforce. On Azure DevOps, pressing Enter, Ctrl+Enter or Space on the Comment button published a non-compliant comment. These keys are now blocked like a click.
  • On GitHub, "Close with comment" and the Overview's Comment button no longer get around enforce.
  • A comment that quotes code or text before its label gets its badge.
  • A repository can ask for a shorter configuration cache than your organization's policy. The policy's cache duration was imposed as is, so a repository wanting fresher settings was forced back to it. It is now a maximum, as intended.
  • On Azure DevOps, editing a comment is no longer mistaken for a new comment.
  • The diagnostic journal keeps the evidence of a problem that never went away, instead of replacing it with a later observation.

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-rc.1-chromium.zip chrome://extensions → Mode développeur → Charger l'extension non empaquetée → le dossier décompressé
Firefox conventional-comments-toolkit-1.0.0-rc.1-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. Elle ne bloque jamais la fusion d'une PR : un commentaire n'est contrôlé que dans le navigateur des personnes ayant installé l'extension.

Empreintes SHA-256

5734fa60ac88fc8cbb138ee8e0f8669563e26123f875c46f80586f8c136b1438  conventional-comments-toolkit-1.0.0-rc.1-chromium.zip
ceee55e4b65e89a9fe95437c785919311f8264d22ae5b356591b0eef91fbfb9a  conventional-comments-toolkit-1.0.0-rc.1-firefox.zip

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

Loading

Conventional Comments Toolkit 1.0.0-beta.21

Conventional Comments Toolkit 1.0.0-beta.21 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 02 Nov 06:29
v1.0.0-beta.21
5b50808

1.0.0-beta.21 — November 2, 2026

The extension no longer goes silent on GitHub after you restart your browser.

🐛 Bug fixes

  • The extension stays active after the browser restarts. After a browser restart, the extension could do nothing at all on GitHub — no badges, no banner, no toolbar, and no blocking even in enforce mode — until you opened its settings page. The browser was dropping the extension's script at restart, and nothing set it up again. The script now survives a restart, and the extension also sets it up again as soon as the browser starts. If you had to open the settings page after each restart to get the extension back, you no longer need to. The diagnostic archive now shows that start-up step too.

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.21-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.21-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

a0d27fd354bfa6f85a1f0a4ff5503a3a8288e441915e00d8cd26aeee58a7714e  conventional-comments-toolkit-1.0.0-beta.21-chromium.zip
7e36f1630fb62ddb5b44d8548e3528a1095c73afc3b854c54517e9271bb2e8d4  conventional-comments-toolkit-1.0.0-beta.21-firefox.zip

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

Loading

Conventional Comments Toolkit 1.0.0-beta.20

Conventional Comments Toolkit 1.0.0-beta.20 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 01 Nov 23:01
v1.0.0-beta.20
06a69ac

1.0.0-beta.20 — November 1, 2026

The diagnostic archive now shows how the extension was activated in your browser, to track down pages where it does nothing at all; two settings fields are easier to read.

✨ Features

  • The diagnostic archive records how the extension's script was set up in your browser. On some GitHub pages the extension can be completely inactive — no badges, no toolbar, and nothing blocked even in enforce mode — until you open its settings page. Looking into it from outside repairs it, so the cause could not be seen. The extension now keeps a short history of each time it set up, updated or removed its script: what triggered it, which sites it covered, what the browser reported before and after, and any error. If the problem happens to you, download the diagnostic from the settings page before anything else and attach it to an issue; the download is offered even when the journal has no other line. The history holds no page address, and "Clear the log" clears it too.

🔧 Changed

  • The settings page's journal no longer shows the legend about page marks. The marks and their links work as before.

🐛 Bug fixes

  • The hints inside the "Direct shortcuts" and "Button order" fields are readable in both themes. They are quieter than what you type, but no longer too faint to read. The hint of the "Domain to allow" field is unchanged.

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.20-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.20-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

c19d9aa5b3b80fea98bdc096cf0c2eb8a8a9a9a726cdae9a0290bfa77c7e565f  conventional-comments-toolkit-1.0.0-beta.20-chromium.zip
31602d790d13182803e929a59a4ea90c2d94704cda6ee3a5eea673d2b0329187  conventional-comments-toolkit-1.0.0-beta.20-firefox.zip

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

Loading

Conventional Comments Toolkit 1.0.0-beta.19

Conventional Comments Toolkit 1.0.0-beta.19 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 31 Oct 09:17
v1.0.0-beta.19
996a6fd

1.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.

Loading

Conventional Comments Toolkit 1.0.0-beta.18

Conventional Comments Toolkit 1.0.0-beta.18 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 30 Oct 13:41
v1.0.0-beta.18
f79e4ed

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.

Loading

Conventional Comments Toolkit 1.0.0-beta.17

Conventional Comments Toolkit 1.0.0-beta.17 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 29 Oct 18:04
v1.0.0-beta.17
35b5a12

1.0.0-beta.17 — October 29, 2026

Two fields of the settings page no longer show up white in the dark theme.

🐛 Bug fixes

  • The "Button order" field and the configuration block of the added labels now follow the dark theme. Both stayed white on a dark settings page, which made them hard to read and out of place next to the other fields. They now look like the rest of the page.

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.17-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.17-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

1ae33bf3f24cc7306f8f1966ed21940e0a76265ef5e1a12fec654bf294c2b02a  conventional-comments-toolkit-1.0.0-beta.17-chromium.zip
35fd5157abfd84fc402f018da9d172b14efe139358e1b3fc1f03515183eb8727  conventional-comments-toolkit-1.0.0-beta.17-firefox.zip

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

Loading

Conventional Comments Toolkit 1.0.0-beta.16

Conventional Comments Toolkit 1.0.0-beta.16 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 29 Oct 17:30
v1.0.0-beta.16
6c20b61

1.0.0-beta.16 — October 29, 2026

The settings page tells you which version you are running, and the GitHub adapter reads a pull request's merge button and resolved conversations correctly again.

✨ Features

  • The settings page shows the extension's version next to its title. A release candidate reads v1.0.0-beta.16, where chrome://extensions shows 1.0.0 for every beta, so you can tell which build you are running before you report a problem. Firefox shows its own version number.

🐛 Bug fixes

  • The banner no longer counts resolved conversations as unresolved. On a pull request whose resolved conversations GitHub collapses, the banner listed them among the unresolved ones, issue (blocking) threads included. It now agrees with the Files changed view of the same pull request.

  • The extension finds the merge button of an open pull request on github.com again. GitHub changed how the button is built and the extension no longer recognised it. Nothing changes on screen yet: the extension greys the button only when a verifier publishes a failing state, and none ships.

  • The settings page no longer reports false selector failures. Its Status section listed searches that failed because there was nothing to find, such as the merge button of a merged pull request. They are no longer logged.

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.16-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.16-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

64297fef102b40eab98deb06bf1b0ba182e143349c0455f19265be4450fe1093  conventional-comments-toolkit-1.0.0-beta.16-chromium.zip
b575b7768e1899dca085cd39db3b91b7cd0a265a2c2e4425dc668e8699ba8a14  conventional-comments-toolkit-1.0.0-beta.16-firefox.zip

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

Loading

Conventional Comments Toolkit 1.0.0-beta.15

Conventional Comments Toolkit 1.0.0-beta.15 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 29 Oct 15:43
v1.0.0-beta.15
89a8ee7

1.0.0-beta.15 — October 29, 2026

A label's badge now tells the reader what a comment means, and its button tells the writer when to use it.

🔧 Changed

  • The badge and the button no longer show the same tooltip. Hovering the label badge of a published comment tells you what the comment means, without an example: issue reads "A problem spotted in this code; the comment explains which one." Hovering the label's toolbar button tells you when to use it, then gives an example: "Flag a problem to fix, ideally with a lead." Every shipped label has both texts, in English and French. A badge text never claims more than the label says: whether a point blocks is still shown by the decoration badge next to it.

  • The reviewer skill shows priorities as coloured badges. An agent following skills/review-pull-request now marks each finding with a P0 to P3 badge; where the image does not show, the reader sees [P1] as before.

✨ Features

  • A team can write each text: labels[].usage for the button. In .conventional-comments.json, description now goes to the badge and usage to the button. Written, each replaces the shipped text; written empty (""), it removes that tooltip. Without usage, the button shows description, so a configuration written for 1.0.0-beta.14 keeps showing the same text on both.

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.15-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.15-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

4cb2752a4ef258c305bec76caa6d6aac249e176a0b68728ffc775fcd851c47e1  conventional-comments-toolkit-1.0.0-beta.15-chromium.zip
26e44008cc86431311a1ac7887c7cb750ee4406bb27c54f6f09f61913dd58942  conventional-comments-toolkit-1.0.0-beta.15-firefox.zip

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

Loading

Conventional Comments Toolkit 1.0.0-beta.14

Conventional Comments Toolkit 1.0.0-beta.14 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 29 Oct 15:11
v1.0.0-beta.14
d216086

1.0.0-beta.14 — October 29, 2026

Labels explain themselves where you read them: a hover on a badge shows its definition, and a team can write its own. quibble steps aside for nitpick, and two skills let AI agents review the toolkit's way.

✨ Features

  • A badge tells you what its label means. Hover the label badge of a published comment and you get the same tooltip as its toolbar button: the definition and an example, in the interface language. The badge also keeps the arrow cursor rather than the text-selection bar.

  • Your team can define its labels: labels[].description. Write a description for a label you create, or for a shipped one such as issue, in .conventional-comments.json, and the tooltip of the button and the badge shows it. Written, it replaces the shipped definition and its example; written empty (""), it removes the tooltip; left out, a shipped label keeps its definition. It is shown as written, whatever the interface language.

  • Two review skills for AI agents. skills/review-pull-request and skills/respond-to-review tell an agent how to review a pull request, or answer its review, with this toolkit's labels: findings followed up until verified, reviewed: once nothing is left, reply labels for the author, and never an approval or a merge. See the README.

🔧 Changed

  • quibble is off by default. Conventional Comments itself describes it as "very much like nitpick", so the toolbar showed two buttons for one meaning. Use nitpick, or bring quibble back with { "id": "quibble", "enabled": true } in .conventional-comments.json. Until you do, a quibble: comment is an unknown label where comments are validated.

  • reviewed now says when to use it. Its tooltip read "you have finished reading"; it now reads "your points are dealt with, you have nothing to add". Post it once each of your points is fixed and checked, or set aside by a reply you accept. Any later change reopens your review. It still approves nothing.

  • The extension's description no longer mentions the companion server, removed in 1.0.0-beta.13, in chrome://extensions and in the Release pages.

🐛 Bug fixes

  • A custom label no longer shows its internal key as a tooltip. Hovering the button of a label your repository created, such as risk, showed "label.risk". It now shows its description if it has one, and nothing otherwise.

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.14-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.14-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

ef9690f9042e41f55cf57ba5ca7c9cf0314d9a29e22bbf2fc753dceeede9e4f3  conventional-comments-toolkit-1.0.0-beta.14-chromium.zip
cac91f7a8576876a7540ea06e4d417ae544daded26026905a6932ff48d2c0247  conventional-comments-toolkit-1.0.0-beta.14-firefox.zip

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

Loading