From 4ce0211bf7e1c60efdc7bf8b6ce4cf35d4452e83 Mon Sep 17 00:00:00 2001 From: small-claude <307551610+vpetersson-bot@users.noreply.github.com> Date: Sun, 1 Nov 2026 09:05:00 +0000 Subject: [PATCH 1/2] Bump the manifests to 2026.11.0 master has carried 2026.10.0 since #268, but no tag was cut for it, so the newest release is still v1.6.1 from July. A new month resets MICRO, so the release that ships now is 2026.11.0. Co-Authored-By: Claude Opus 5.5 --- src/manifest-chrome.json | 2 +- src/manifest-firefox.json | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/manifest-chrome.json b/src/manifest-chrome.json index 3308496..c56b7fc 100644 --- a/src/manifest-chrome.json +++ b/src/manifest-chrome.json @@ -1,7 +1,7 @@ { "manifest_version": 3, "name": "Save to Screenly", - "version": "2026.10.0", + "version": "2026.11.0", "description": "Display live web pages on your Screenly digital sign.", "icons": { "16": "assets/images/screenly-logo-16.png", diff --git a/src/manifest-firefox.json b/src/manifest-firefox.json index a4251ee..ac8de3e 100644 --- a/src/manifest-firefox.json +++ b/src/manifest-firefox.json @@ -1,7 +1,7 @@ { "manifest_version": 3, "name": "Save to Screenly", - "version": "2026.10.0", + "version": "2026.11.0", "description": "Display live web pages on your Screenly digital sign.", "icons": { "16": "assets/images/screenly-logo-16.png", From e8c149d832b3ef2696cbd24bc7a76edab3e8895d Mon Sep 17 00:00:00 2001 From: small-claude <307551610+vpetersson-bot@users.noreply.github.com> Date: Tue, 3 Nov 2026 19:00:59 +0000 Subject: [PATCH 2/2] Use a two-digit year: bump the manifests to 26.11.0 The stores have never seen a 2026.x version (the newest tag is v1.6.1), so switch to YY.M.MICRO now, before a four-digit tag makes it permanent. CONTRIBUTING.md documented YYYY.M.MICRO, which is where the 2026.x numbers came from, so update it to match. Co-Authored-By: Claude Opus 5.5 --- CONTRIBUTING.md | 21 +++++++++++---------- src/manifest-chrome.json | 2 +- src/manifest-firefox.json | 2 +- 3 files changed, 13 insertions(+), 12 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1d46fcc..e155e9d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -34,10 +34,10 @@ For a guide on how to open a pull request, please read [this documentation from ### Versioning -Releases use CalVer `YYYY.M.MICRO`, with no zero padding on the month: -`2026.9.0`, `2026.10.0`. A new month resets MICRO to `0`; a second release -within the same month increments it. Tags carry a `v` prefix — `v2026.9.0` — -which is what `build.yaml` triggers on. +Releases use CalVer `YY.M.MICRO`, with a two-digit year and no zero padding on +the month: `26.9.0`, `26.11.0`. A new month resets MICRO to `0`; a second +release within the same month increments it. Tags carry a `v` prefix — +`v26.11.0` — which is what `build.yaml` triggers on. **The version lives in the manifests.** `src/manifest-chrome.json` and `src/manifest-firefox.json` both carry it, and it is what the stores read. Bump @@ -54,22 +54,23 @@ agreeing is a convention rather than a guarantee. not the extension's. Its version is unrelated and is not bumped for a release. Chrome Web Store versions may only ever increase, so the move from `1.x` to -CalVer is one-way. +CalVer is one-way. The same goes for the year: `26` sorts below `2026`, so a +single `vYYYY` release would rule out the two-digit year for good. ### Creating a Release * Bump `.version` in `src/manifest-chrome.json` and `src/manifest-firefox.json` - to the new `YYYY.M.MICRO` version, and merge that to `master`. -* Tag the merged commit. `vYYYY.M.MICRO`, matching the manifests exactly — the - first CalVer release was `v2026.9.0`: + to the new `YY.M.MICRO` version, and merge that to `master`. +* Tag the merged commit. `vYY.M.MICRO`, matching the manifests exactly — the + first CalVer release is `v26.11.0`: ```bash $ git pull $ git checkout master $ git tag [...] -$ git tag -a vYYYY.M.MICRO -m "tl;dr changelog." -$ git push origin vYYYY.M.MICRO +$ git tag -a vYY.M.MICRO -m "tl;dr changelog." +$ git push origin vYY.M.MICRO ``` * Navigate to the [GitHub releases](https://github.com/Screenly/Browser-Extension/releases) and click 'Draft a new release'. * Select the tag you just created above and provide a release title and description. diff --git a/src/manifest-chrome.json b/src/manifest-chrome.json index c56b7fc..c8e043f 100644 --- a/src/manifest-chrome.json +++ b/src/manifest-chrome.json @@ -1,7 +1,7 @@ { "manifest_version": 3, "name": "Save to Screenly", - "version": "2026.11.0", + "version": "26.11.0", "description": "Display live web pages on your Screenly digital sign.", "icons": { "16": "assets/images/screenly-logo-16.png", diff --git a/src/manifest-firefox.json b/src/manifest-firefox.json index ac8de3e..b050abf 100644 --- a/src/manifest-firefox.json +++ b/src/manifest-firefox.json @@ -1,7 +1,7 @@ { "manifest_version": 3, "name": "Save to Screenly", - "version": "2026.11.0", + "version": "26.11.0", "description": "Display live web pages on your Screenly digital sign.", "icons": { "16": "assets/images/screenly-logo-16.png",