Skip to content

Release v0.11.6 - #168

Merged
jonbaldie merged 1 commit into
mainfrom
chore/release-v0.11.6
Oct 11, 2026
Merged

jonbaldie merged 1 commit into
mainfrom
chore/release-v0.11.6

Conversation

@jonbaldie

Copy link
Copy Markdown
Owner

Summary

v0.11.5 → persistence fixes on main → v0.11.6

Patch release; empty release marker, matching prior releases. No additional code changes.

Evidence

  • Before: v0.11.5 at 8a73d0d; four unreleased commits through bef9aa5.
    After: identical tree to bef9aa5, prepared for v0.11.6.
  • Deno 2.7.6: frozen dependency install, production type check and compile passed; 345 local production tests passed, including real OS short-write/restart regressions.
  • npm run quality:production passed; messcript dependencies installed with npm ci in this workspace.
  • Compiled binary HTTP smoke passed: health, auth, invalid JSON/null/oversize rejection, typed FIFO, non-destructive HEAD, crash replay, graceful shutdown/restart replay.
  • Full test suite and both mutation jobs must pass in PR CI before merge. Local Stryker is not installed or lockfile-pinned; the existing CI supplies it without changing this workspace's dependencies.
  • No release/deployment workflow is documented. After CI and merge: tag the merge commit and publish a GitHub release. No deployment or binary assets are required by this fallback workflow.

Full Changelog: v0.11.5...v0.11.6

Merge Danger

Door: two-way (release marker only; fix rollbacks require a later release).

Blast Radius: persistence

Included fixes change failure handling on full/unwritable persistence storage; no log-format change.

@jonbaldie
jonbaldie merged commit 2a961f5 into main Oct 11, 2026
4 checks passed
@jonbaldie
jonbaldie deleted the chore/release-v0.11.6 branch October 11, 2026 19:57
@jonbaldie

Copy link
Copy Markdown
Owner Author

Published v0.11.6: https://github.com/jonbaldie/queue/releases/tag/v0.11.6. Remote annotated tag resolves to merge commit 2a961f5. All four checks passed on main (https://github.com/jonbaldie/queue/actions/runs/38170150090) and tag (https://github.com/jonbaldie/queue/actions/runs/38170153656), including both full mutation gates. No deployment step or release assets are required by the fallback workflow.

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