Skip to content

docs: bring RELEASE.md up to date through v1.4.0 - #778

Merged
janbjorge merged 1 commit into
mainfrom
docs/release-notes-v1.4.0
Aug 31, 2026
Merged

docs: bring RELEASE.md up to date through v1.4.0#778
janbjorge merged 1 commit into
mainfrom
docs/release-notes-v1.4.0

Conversation

@janbjorge

@janbjorge janbjorge commented Aug 31, 2026

Copy link
Copy Markdown
Owner

No description provided.

RELEASE.md has covered only v1.0.0 since May, leaving five releases of
behavior and schema changes undocumented.

Restructure it as a running changelog, backfill v1.0.1 through v1.3.2
from the commit log, and open a v1.4.0 section for the pending work.

Drop release dates from the headings. The git tags already carry them,
and the date is the one field nobody can know before the tag exists, so
keeping it forces a rename at release time. Without it the file is
append-only.

The v1.4.0 entry leads with the capacity-slot schema change: dequeue
now requires the slot column and pgqueuer_picked_slot_idx, and
verify_structure raises RuntimeError when either is absent, so workers
started before pgq upgrade will not boot.
@janbjorge
janbjorge merged commit ce199ae into main Aug 31, 2026
22 checks passed
@janbjorge
janbjorge deleted the docs/release-notes-v1.4.0 branch August 31, 2026 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant