Stale News Feed Causes Confusion and Potentially Causes Debugging Rabbit Holes

## The Problem I Encountered

I recently rebuilt my ComfyUI Docker container from scratch for irrelevant reasons. Earlier I saw "ComfyUI v0.3.62 is released" (Updated October 1st) in the ComfyUI Manager notice board. However, my actual installation was running v0.3.68 (released November 5th).

**My assumption:** The Docker rebuild must have somehow downgraded my ComfyUI version.

I spent significant time investigating:
- Checking my Dockerfile for version pinning issues
- Upgrading ComfyUI manager using the `Update ComfuUI` button. It must have failed — I still see "ComfyUI v0.3.62 is released"

- ~~Examining git logs to understand what version was mounted~~
- ~~Comparing requirements.txt versions~~
- ~~Suspecting dependency mismatches~~
- Ask Claude if I lost my sanity, then after investigation let it write the first draft of this message, of which the top three items were completely fabricated by the creative Claude Code. Nice.

**The real issue:** The news wiki at [the news page](https://github.com/ltdrdata/ltdrdata.github.io/wiki/News) hasn't been updated since October 1st. The "v0.3.62" announcement was simply stale news. It was not an indication of my installed version.

## Why This Is Particularly Confusing

- **The notice board shows old news prominently at the top** - This looks like the "current state" rather than historical announcements. The actual version info is buried at the bottom. The correct version display (`v0.3.68-17-ge1d85e75`) appears below the news content, making it easy to miss.

- **No ComfyUI version flag exists** - Running `python main.py --version` doesn't work, forcing users to manually check `comfyui_version.py` or parse git logs to verify their version. This goes against my perception of standards, `--version` is as basic as `--help` IMO. I had to *find* the sub-standard version reporting file. I was in a terminal and I did not happen to list files and then also find this file in the 76 lines that would have been returned.

This sets up for a potential perfect storm of time-wasting debugging rabbit holes, especially for users in containerized environments who regularly rebuild images, or any other obscure setups. I value safety and running ComfyUI without sandboxing... oh man, ComfyUI without sandboxing... you better actually read the code of the nodes you install. It's a ticking time bomb. Or am I missing something?

## Root Cause: Manual Update Process

First of all, my incompotence of not knowing that at the bottom left of the ComfyUI interface, or whatever modification of it I am running, there is a question mark inside a circle that if clicked reveals your ComfyUI version. That's a know-how that I had-not.

But I must switch the blame, I cannot be the problem! The news feed is fetched from `https://github.com/ltdrdata/ltdrdata.github.io/wiki/News`, which requires manual updates. When updates lag (currently 6 weeks behind), **all ComfyUI Manager users see stale information**.

Since both ComfyUI-Manager and the news wiki are under your control (ltdrdata), this creates an unnecessary maintenance burden and single point of failure — need I mention a neglected maintenance burden. I even tried to open a PR with an updated list just to relief you of the maintenance burden at least until it's improved upon, but GitHub wiki pages are separate repositories and I have no permission to open a PR for the wiki.

## Suggested Solution
Fetch Dynamically from ComfyUI Releases. After all, the most recent news article is no more than a concatenation of change-lists.
Instead of maintaining a separate wiki, fetch release information directly from the official ComfyUI repository. This would always show the up-to-date version information and relief you of the burden of maintaining the news page that is just a compiled copy of the source.

Here is the markdown update that I wrote by book and quill at my candle that kept being blown out by the wind. Okay just kidding - I let Claude handle it. Moreover, I am no herdsman and I do not have any birds to pull feathers from. Regrettably I have to compose by keyboard. And don't get me started on the fact I have no idea who sells ink in jars!

```
**Keywords: v0.3.68**

---

ComfyUI v0.3.68 is released (https://github.com/comfyanonymous/ComfyUI/releases/tag/v0.3.68, https://github.com/comfyanonymous/ComfyUI/releases/tag/v0.3.67, https://github.com/comfyanonymous/ComfyUI/releases/tag/v0.3.66, https://github.com/comfyanonymous/ComfyUI/releases/tag/v0.3.65, https://github.com/comfyanonymous/ComfyUI/releases/tag/v0.3.64, https://github.com/comfyanonymous/ComfyUI/releases/tag/v0.3.63)

## v0.3.68

- Bump stable portable to cu130 python 3.13.9
- Speed up offloading using pinned memory with race condition fixes
- Add RAM Pressure cache mode for better resource management
- Small speed improvements to --async-offload
- Optimizations for fp8 torch.compile operations
- Multiple API node conversions to new client standards (Luma, Minimax, Pixverse, Ideogram, StabilityAI, Pika)
- Convert nodes_recraft.py to V3 schema and hypernetwork/OpenAI node conversions
- Remove comfy api key from queue api for improved security
- Add a ScaleROPE node (works on WAN and Lumina models)
- Support for 12-20 second durations in LTXV API nodes
- Race condition fixes in async-offload preventing corruption
- Cache signature hashing fixes for bytes data
- Torch compile regression fixes
- And more...

---

## v0.3.67

- Only disable cudnn on newer AMD GPUs to improve compatibility
- Add endpoint support for published subgraphs from custom nodes
- Integrated dependency-aware caching and resolved issues with --cache-none when using loops and lazy evaluation
- Implemented preliminary support for handling multi-dimensional latent configurations
- Upgraded network client to version 2 featuring async operations, cancellation support, and download capabilities
- Converted Tripo and Gemini API nodes to V3 schema, plus added LTXV API nodes
- Bumped portable dependencies to PyTorch cu130 with Python 3.13.9 support
- Added batch script option to run ComfyUI without API nodes
- Updated frontend to version 1.28.8
- Resolved Windows-specific retry issues and torch-directml usage warnings
- Minor README improvements and template updates (0.2.2 → 0.2.4)
- And more...

---

## v0.3.66

- Faster workflow cancelling implemented
- Chroma radiance speedup and batch size handling corrections
- PyTorch compiler disabled for cast_bias_weight function
- CUDA malloc turned off by default with --fast autotune
- Python 3.14 installation instructions added
- gfx942 GPU no longer supports fp8 operations
- PyTorch stable version updated to cu130
- CuDNN workaround for VAE memory issues on torch 2.9
- Veo3.1 model added to api-nodes
- TemporalScoreRescaling node introduced
- Dynamic pricing format fixed in api-nodes
- Deprecated API alert feature implemented
- Manual patches merging refactored with merge_nested_dicts
- Frontend bumped to version 1.28.7
- EasyCache apply_cache_diff batch slicing corrected
- Chroma radiance batch size >1 output issues resolved
- And more...

---

## v0.3.65

- Multiple node files converted to V3 schema (compositing, latent operations, SD3, Flux, upscaling, Hunyuan models)
- Better memory estimation for the SD/Flux VAE on AMD GPUs
- RDNA4 pytorch attention support added for ROCm 7.0+
- Fixed loading old stable diffusion ckpt files on newer numpy
- Audio node stereo/mono handling corrections
- Fixed fp8 scaled LoRA application
- VAE cache VRAM leak fixes
- Enum class support for Combo options
- Lazy formatting in logging
- Price extractor feature for API nodes
- Aspect ratio parameters for GeminiImage nodes
- mmaudio 16k VAE implemented
- Diffusion models now always set to eval() mode
- Documentation updated to version 0.3.0
- And more...

---

## v0.3.64

- Enhanced pylint rules for API nodes
- Support for multiline negative prompts in PixVerse API nodes
- Converted nodes_pika.py and nodes_kling.py to V3 schema format
- Implemented Gemma 3 as a text encoder option
- Fixed custom multipart parser in ReCraft-API node to properly return FormData
- Added Sora2 API node for video generation capabilities
- Temporary fix applied for LTXV custom nodes compatibility
- Bumped frontend version to 1.27.10
- Updated template to version 0.1.94
- And more...

---

## v0.3.63

- Bump frontend to 1.27.7
- Multiple V3 schema conversions for nodes (audio encoder, differential diffusion, morphology, torch compile)
- VAE tiled fallback VRAM leak resolution for both SD and WAN VAE
- Remove soundfile dependency. No more torchaudio load or save
- Turn on TORCH_ROCM_AOTRITON_ENABLE_EXPERIMENTAL by default for AMD ROCm
- Epsilon Scaling node for exposure bias correction
- Support for new Hunyuan VAE
- Add kling-2-5-turbo to txt2video and img2video nodes
- Enhanced linting with pylint for API nodes folder
- Various indentation and import fixes across API nodes
- And more...

---

Issue News:

Features/Updates News:
```

If the proposed solution ends up in a backlog, then this snippet could be placed at https://github.com/ltdrdata/ltdrdata.github.io/wiki/News for now.

Start by tracing the ComfyUI Manager notice board's use of the News wiki at ltdrdata.github.io/wiki/News, then review comfyui_version.py and the reported python main.py --version entry point. Done should prevent outdated release announcements from being presented as current and provide a reliable way to identify the installed ComfyUI version.

Written by the indexing model from the issue text.