Merge pull request #170 from beNative/codex/prepare-new-github-release-and-update-version

chore: prepare v0.6.8 release

Author: beNative

README.md

@@ -84,7 +84,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.7` followed by `git push origin v0.6.7`) to trigger the automated release workflow.
+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.
 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

TECHNICAL_MANUAL.md

@@ -128,7 +128,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.7` followed by `git push origin v0.6.7`) to trigger the automated release pipeline.
+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.
 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

VERSION_LOG.md

@@ -1,5 +1,28 @@
 # Version Log
 
+## v0.6.8 - The Publication Polish Update
+
+This maintenance release keeps the publication workflow accurate by bumping
+the version metadata, refreshing the Markdown guides, and aligning the release
+tests with the assets that will accompany the new tag.
+
+### 🛠 Improvements
+
+-   Bumped the application version to `v0.6.8` and refreshed the release
+    tagging examples so the publishing checklist references the current
+    commands.
+-   Re-reviewed every Markdown guide (README, manuals, version log) and synced
+    the copies in `docs/` to ensure the distributed documentation matches the
+    repository source.
+-   Summarized the release tasks in this log so the GitHub release body can be
+    prepared directly from the latest entry.
+
+### 🐛 Fixes
+
+-   Updated the release workflow test fixtures to expect `v0.6.8`
+    identifiers and artifact names, preventing mismatches once the new
+    installer set is published.
+
 ## v0.6.7 - The Release Readiness Confirmation
 
 This maintenance release double-checks the release process ahead of the next

docs/README.md

@@ -84,7 +84,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.7` followed by `git push origin v0.6.7`) to trigger the automated release workflow.
+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.
 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

docs/TECHNICAL_MANUAL.md

@@ -128,7 +128,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.7` followed by `git push origin v0.6.7`) to trigger the automated release pipeline.
+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.
 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

docs/VERSION_LOG.md

@@ -1,5 +1,28 @@
 # Version Log
 
+## v0.6.8 - The Publication Polish Update
+
+This maintenance release keeps the publication workflow accurate by bumping
+the version metadata, refreshing the Markdown guides, and aligning the release
+tests with the assets that will accompany the new tag.
+
+### 🛠 Improvements
+
+-   Bumped the application version to `v0.6.8` and refreshed the release
+    tagging examples so the publishing checklist references the current
+    commands.
+-   Re-reviewed every Markdown guide (README, manuals, version log) and synced
+    the copies in `docs/` to ensure the distributed documentation matches the
+    repository source.
+-   Summarized the release tasks in this log so the GitHub release body can be
+    prepared directly from the latest entry.
+
+### 🐛 Fixes
+
+-   Updated the release workflow test fixtures to expect `v0.6.8`
+    identifiers and artifact names, preventing mismatches once the new
+    installer set is published.
+
 ## v0.6.7 - The Release Readiness Confirmation
 
 This maintenance release double-checks the release process ahead of the next

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "docforge",
-  "version": "0.6.7",
+  "version": "0.6.8",
   "description": "An application to manage and refine documents.",
   "main": "dist/main.js",
   "scripts": {

package.json

@@ -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.7',
+        tag: 'v0.6.8',
         skipHttp: true,
         skipDownload: true,
         http: {
           fetchJson: async () => ({
             assets: [
               {
-                name: 'DocForge-Setup-0.6.7.exe',
-                browser_download_url: 'https://example.invalid/DocForge-Setup-0.6.7.exe',
+                name: 'DocForge-Setup-0.6.8.exe',
+                browser_download_url: 'https://example.invalid/DocForge-Setup-0.6.8.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.7')) {
+      if (url.endsWith('/releases/tags/v0.6.8')) {
         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.7',
+      tag: 'v0.6.8',
       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.7',
+    version: '0.6.8',
     files: [
       {
-        url: 'DocForge-Setup-0.6.7.exe',
+        url: 'DocForge-Setup-0.6.8.exe',
         sha512: 'placeholder',
         size: 100,
       },
     ],
-    path: 'DocForge-Setup-0.6.7.exe',
+    path: 'DocForge-Setup-0.6.8.exe',
     sha512: 'placeholder',
   });
 
   const assets = new Map([
     [
-      'DocForge-Setup-0.6.7.exe',
+      'DocForge-Setup-0.6.8.exe',
       {
-        name: 'DocForge-Setup-0.6.7.exe',
-        browser_download_url: 'https://example.invalid/DocForge-Setup-0.6.7.exe',
+        name: 'DocForge-Setup-0.6.8.exe',
+        browser_download_url: 'https://example.invalid/DocForge-Setup-0.6.8.exe',
       },
     ],
   ]);
@@ -731,7 +731,7 @@ test('auto-update analysis reports unreachable assets when GitHub returns 404',
     metadataSource,
     owner: 'beNative',
     repo: 'docforge',
-    tag: 'v0.6.7',
+    tag: 'v0.6.8',
     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.7.exe') && entry.includes('404 (Not Found)')));
+  assert(result.unreachable.some((entry) => entry.includes('DocForge-Setup-0.6.8.exe') && entry.includes('404 (Not Found)')));
 });
 
 test('metadata updates compute digests for non-release assets referenced locally', async (t) => {