# 26-Jul-2026 — Always set a walk album cover after saving photos [#312](https://github.com/nbarrett/ngx-ramblers/issues/312)

## [build 796](https://github.com/nbarrett/ngx-ramblers/actions/runs/30220344883) — [commit 1123e45](https://github.com/nbarrett/ngx-ramblers/commit/1123e455efac34585d138f48a08f8d9dd059e6a6)

_____

## What's new

When you create a walk photo album and save photos, a cover image is now selected reliably. Previously the cover step could be skipped if a temporary in-browser mark was lost (for example after a reload), leaving the album with photos but no cover selected.

## At a glance

- Saving photos in the create-album workflow always picks a cover when one is missing
- With several photos, AI still chooses the cover when available; otherwise the first photo is used
- The "needs a cover" mark survives a page reload in the same browser session

### **ci+release-notes**: tolerate history rewrites when generating notes ([#312](https://github.com/nbarrett/ngx-ramblers/issues/312))

## What's new

After a force-push, release notes no longer fail the main build because the previous GitHub SHA is not on the new history. The job falls back to the latest commits instead of aborting with an invalid git range.

## At a glance

- Release notes generation survives force-pushes and missing previous SHAs
- Main build no longer fails only on the release-notes step after a history rewrite