docs: bring RELEASE.md up to date through v1.4.0 - #778
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.