From 96099963fd4d389b1956d32c61597296a70de8f0 Mon Sep 17 00:00:00 2001 From: Tim Sinaeve Date: Wed, 29 Oct 2025 13:20:27 +0100 Subject: [PATCH] chore: prepare 0.6.9 release --- README.md | 2 +- TECHNICAL_MANUAL.md | 2 +- VERSION_LOG.md | 10 ++++++++ docs/README.md | 2 +- docs/TECHNICAL_MANUAL.md | 2 +- docs/VERSION_LOG.md | 10 ++++++++ package-lock.json | 4 ++-- package.json | 2 +- scripts/__tests__/release-workflow.test.mjs | 26 ++++++++++----------- 9 files changed, 40 insertions(+), 20 deletions(-) diff --git a/README.md b/README.md index d30c68d..3615042 100644 --- a/README.md +++ b/README.md @@ -87,7 +87,7 @@ To create a new public build of DocForge: 3. Review the Markdown documentation (README, manuals, and release notes) so the written guidance matches the current workflow. 4. Sync the documentation copies under `docs/` (README, manuals, version log) with any updates made at the project root. 5. Commit the changes and push them to the default branch so the release tag points at the finalized documentation. -6. Create and push a tag that matches the new version (for example, `git tag v0.6.8` followed by `git push origin v0.6.8`) to trigger the automated release workflow. +6. Create and push a tag that matches the new version (for example, `git tag v0.6.9` followed by `git push origin v0.6.9`) to trigger the automated release workflow. 7. Monitor the "Release" workflow run, then confirm that the published GitHub release lists the correct notes and includes installers for every platform before announcing availability. ## Application Icon Workflow diff --git a/TECHNICAL_MANUAL.md b/TECHNICAL_MANUAL.md index 9ae1bf9..efcc30c 100644 --- a/TECHNICAL_MANUAL.md +++ b/TECHNICAL_MANUAL.md @@ -145,7 +145,7 @@ Electron Builder manages the packaging and publishing workflow for DocForge. The 3. Review and update the Markdown documentation (README, manuals, release notes) so the written guidance reflects the final state of the build. 4. Sync the Markdown files under `docs/` with the copies at the project root. 5. Commit and push the changes so the release tag points at the finished documentation. -6. Create and push a matching version tag (for example, `git tag v0.6.8` followed by `git push origin v0.6.8`) to trigger the automated release pipeline. +6. Create and push a matching version tag (for example, `git tag v0.6.9` followed by `git push origin v0.6.9`) to trigger the automated release pipeline. 7. Monitor the "Release" workflow run and verify the published GitHub release lists the correct notes and includes the installers for every supported platform before announcing availability. ### Automated Release Workflow diff --git a/VERSION_LOG.md b/VERSION_LOG.md index ac4f732..46c9874 100644 --- a/VERSION_LOG.md +++ b/VERSION_LOG.md @@ -1,5 +1,15 @@ # Version Log +## v0.6.9 - The Release Prep Maintenance + +### 🐛 Fixes + +- Updated the release workflow fixtures to validate the `v0.6.9` tag and installers, keeping the automated publishing checks aligned with the shipped binaries. + +### 📝 Documentation + +- Refreshed the release preparation guides so every README and manual references the `v0.6.9` tagging flow and synchronized documentation updates. + ## Unreleased - The Document Export Primer ### ✨ New diff --git a/docs/README.md b/docs/README.md index cdf46c2..fc6286e 100644 --- a/docs/README.md +++ b/docs/README.md @@ -85,7 +85,7 @@ To create a new public build of DocForge: 3. Review the Markdown documentation (README, manuals, and release notes) so the written guidance matches the current workflow. 4. Sync the documentation copies under `docs/` (README, manuals, version log) with any updates made at the project root. 5. Commit the changes and push them to the default branch so the release tag points at the finalized documentation. -6. Create and push a tag that matches the new version (for example, `git tag v0.6.8` followed by `git push origin v0.6.8`) to trigger the automated release workflow. +6. Create and push a tag that matches the new version (for example, `git tag v0.6.9` followed by `git push origin v0.6.9`) to trigger the automated release workflow. 7. Monitor the "Release" workflow run, then confirm that the published GitHub release lists the correct notes and includes installers for every platform before announcing availability. ## Application Icon Workflow diff --git a/docs/TECHNICAL_MANUAL.md b/docs/TECHNICAL_MANUAL.md index 1ed8d29..0533869 100644 --- a/docs/TECHNICAL_MANUAL.md +++ b/docs/TECHNICAL_MANUAL.md @@ -145,7 +145,7 @@ Electron Builder manages the packaging and publishing workflow for DocForge. The 3. Review and update the Markdown documentation (README, manuals, release notes) so the written guidance reflects the final state of the build. 4. Sync the Markdown files under `docs/` with the copies at the project root. 5. Commit and push the changes so the release tag points at the finished documentation. -6. Create and push a matching version tag (for example, `git tag v0.6.8` followed by `git push origin v0.6.8`) to trigger the automated release pipeline. +6. Create and push a matching version tag (for example, `git tag v0.6.9` followed by `git push origin v0.6.9`) to trigger the automated release pipeline. 7. Monitor the "Release" workflow run and verify the published GitHub release lists the correct notes and includes the installers for every supported platform before announcing availability. ### Automated Release Workflow diff --git a/docs/VERSION_LOG.md b/docs/VERSION_LOG.md index ac4f732..46c9874 100644 --- a/docs/VERSION_LOG.md +++ b/docs/VERSION_LOG.md @@ -1,5 +1,15 @@ # Version Log +## v0.6.9 - The Release Prep Maintenance + +### 🐛 Fixes + +- Updated the release workflow fixtures to validate the `v0.6.9` tag and installers, keeping the automated publishing checks aligned with the shipped binaries. + +### 📝 Documentation + +- Refreshed the release preparation guides so every README and manual references the `v0.6.9` tagging flow and synchronized documentation updates. + ## Unreleased - The Document Export Primer ### ✨ New diff --git a/package-lock.json b/package-lock.json index 6afa0b1..72be387 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "docforge", - "version": "0.6.8", + "version": "0.6.9", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "docforge", - "version": "0.6.8", + "version": "0.6.9", "hasInstallScript": true, "license": "MIT", "dependencies": { diff --git a/package.json b/package.json index 8a68d68..84c09e7 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "docforge", - "version": "0.6.8", + "version": "0.6.9", "description": "An application to manage and refine documents.", "main": "dist/main.js", "scripts": { diff --git a/scripts/__tests__/release-workflow.test.mjs b/scripts/__tests__/release-workflow.test.mjs index 3c3c6e0..c4fb1d2 100644 --- a/scripts/__tests__/release-workflow.test.mjs +++ b/scripts/__tests__/release-workflow.test.mjs @@ -604,15 +604,15 @@ test('remote auto-update check fails when Windows release metadata is absent', a runRemoteCheck({ owner: 'beNative', repo: 'docforge', - tag: 'v0.6.8', + tag: 'v0.6.9', skipHttp: true, skipDownload: true, http: { fetchJson: async () => ({ assets: [ { - name: 'DocForge-Setup-0.6.8.exe', - browser_download_url: 'https://example.invalid/DocForge-Setup-0.6.8.exe', + name: 'DocForge-Setup-0.6.9.exe', + browser_download_url: 'https://example.invalid/DocForge-Setup-0.6.9.exe', }, ], }), @@ -647,7 +647,7 @@ test('remote auto-update check falls back to latest release when requested tag i const headUrls = []; const http = { fetchJson: async (url) => { - if (url.endsWith('/releases/tags/v0.6.8')) { + if (url.endsWith('/releases/tags/v0.6.9')) { const error = new Error('Not Found'); error.status = 404; throw error; @@ -689,7 +689,7 @@ test('remote auto-update check falls back to latest release when requested tag i runRemoteCheck({ owner: 'beNative', repo: 'docforge', - tag: 'v0.6.8', + tag: 'v0.6.9', skipHttp: false, skipDownload: true, http, @@ -704,24 +704,24 @@ test('remote auto-update check falls back to latest release when requested tag i test('auto-update analysis reports unreachable assets when GitHub returns 404', async () => { const metadataSource = YAML.stringify({ - version: '0.6.8', + version: '0.6.9', files: [ { - url: 'DocForge-Setup-0.6.8.exe', + url: 'DocForge-Setup-0.6.9.exe', sha512: 'placeholder', size: 100, }, ], - path: 'DocForge-Setup-0.6.8.exe', + path: 'DocForge-Setup-0.6.9.exe', sha512: 'placeholder', }); const assets = new Map([ [ - 'DocForge-Setup-0.6.8.exe', + 'DocForge-Setup-0.6.9.exe', { - name: 'DocForge-Setup-0.6.8.exe', - browser_download_url: 'https://example.invalid/DocForge-Setup-0.6.8.exe', + name: 'DocForge-Setup-0.6.9.exe', + browser_download_url: 'https://example.invalid/DocForge-Setup-0.6.9.exe', }, ], ]); @@ -731,7 +731,7 @@ test('auto-update analysis reports unreachable assets when GitHub returns 404', metadataSource, owner: 'beNative', repo: 'docforge', - tag: 'v0.6.8', + tag: 'v0.6.9', assets, skipHttp: false, skipDownload: true, @@ -741,7 +741,7 @@ test('auto-update analysis reports unreachable assets when GitHub returns 404', }, }); - assert(result.unreachable.some((entry) => entry.includes('DocForge-Setup-0.6.8.exe') && entry.includes('404 (Not Found)'))); + assert(result.unreachable.some((entry) => entry.includes('DocForge-Setup-0.6.9.exe') && entry.includes('404 (Not Found)'))); }); test('metadata updates compute digests for non-release assets referenced locally', async (t) => {