sql: chain 5.0.8→5.0.9->5.0.10→6.0.0

[mason-sharp]

Backport the 5.0.9 and 5.0.10 upgrade stubs from v5_STABLE and re-anchor the 6.0.0 upgrade script so the extension updates continuously: 5.0.7 → 5.0.8 → 5.0.9 → 5.0.10 → 6.0.0.

• Add sql/spock--5.0.8--5.0.9.sql and sql/spock--5.0.9--5.0.10.sql (version markers; no schema changes in either release).

• Rename sql/spock--5.0.8--6.0.0.sql → sql/spock--5.0.10--6.0.0.sql so the jump to 6.0.0 starts from the latest 5.0.x patch level.

• Add 5.0.9 and 5.0.10 sections to docs/spock_release_notes.md.

• 018_upgrade_schema_match: assert the upgrade node starts at 5.x (was pinned to 5.0.8) since v5_STABLE now builds as 5.0.10.

• Add release notes from the 5.0.x versions.

• Remove delta apply release note from 6.0.0

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR updates Spock 6.0.0 release notes for 5.0.9 and 5.0.10, adds or adjusts extension update SQL stubs for those versions, and generalizes the upgrade schema-match TAP test from a fixed 5.0.8 baseline to any 5.x baseline.

Changes

Spock version bump updates

Layer / File(s)	Summary
Release notes text docs/spock_release_notes.md	The carried-forward bug-fix range is extended to 5.0.10, one carried-forward bullet is removed, the 6.0.0 upgrade note references 5.0.10, and new 5.0.10 and 5.0.9 release sections are added.
Update SQL stubs sql/spock--5.0.8--5.0.9.sql, sql/spock--5.0.9--5.0.10.sql, sql/spock--5.0.10--6.0.0.sql	The update-script headers and guidance are aligned with the 5.0.9 and 5.0.10 version path, and the scripts state that those upgrades introduce no schema changes.
Upgrade schema-match test tests/tap/t/018_upgrade_schema_match.pl	The TAP test wording is generalized from 5.0.8 to 5.x, and the installed-extension version check accepts any 5.* version while still comparing the upgraded schema with a fresh 6.0.0 install.

Poem

I nibbled the notes by moonlit light,
And hopped through 5.x versions just right.
A 5.* trail left tidy and clear,
With schema and updates all in order here.
🐇

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly summarizes the main change: chaining the Spock upgrade path from 5.0.8 through 6.0.0.
Description check	✅ Passed	The description matches the changeset, covering the new upgrade stubs, release notes, renamed script, and test update.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch v508-600-path

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}