done

[Benedict315]

Description

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🔧 Refactoring (no functional changes)
• ⚡ Performance improvement
• 🧪 Test addition or update

Related Issues

Closes #

Changes Made

Testing

Test Coverage

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed

Test Steps

Breaking Changes

Breaking Changes:

Migration Guide:

Screenshots/Demo

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published
• I have checked for breaking changes and documented them if applicable

Additional Notes

closes #792

[ogazboiz]

heads up: main's ci was broken (the Backend CI and Backend Docker Image CI jobs) until the fixes in #969 and #974 just landed, so the red backend/docker checks on this pr are almost certainly stale, they ran against the broken main. please rebase to re-test against the now-green main: git fetch origin && git rebase origin/main && git push --force-with-lease. once it's green i'll review and merge. (if a non-backend check like Frontend CI is still red after the rebase, that part is a real issue worth a look, since frontend ci was passing on main.)

[Benedict315]

heads up: main's ci was broken (the Backend CI and Backend Docker Image CI jobs) until the fixes in #969 and #974 just landed, so the red backend/docker checks on this pr are almost certainly stale, they ran against the broken main. please rebase to re-test against the now-green main: git fetch origin && git rebase origin/main && git push --force-with-lease. once it's green i'll review and merge. (if a non-backend check like Frontend CI is still red after the rebase, that part is a real issue worth a look, since frontend ci was passing on main.)

okay

[ogazboiz]

the deprecated-routes feature itself is coherent: adding the 410-Gone handlers for POST /streams and /events with the deprecated/migration body (main currently 404s via fallthrough, so this is a deliberate behavior change) and updating deprecated.test.ts to match. but a couple of unrelated ci changes need to come out before it can land:

1. ci.yml:98 removes the npm install @vitest/coverage-v8@2.1.9 --no-save line, but the next step runs vitest run --coverage, so dropping the explicit coverage-v8 install risks re-breaking the coverage job. please keep that install.
2. the Dockerfile and soroban-event-worker.ts changes are just blank-line / trailing-newline churn, unrelated to the feature, drop them to keep the diff focused.

keep just the 410-handler work (plus the ci.yml:145 --schema flag if you need it), drop the coverage-install removal and the churn, and it's good. also the title "done" isn't descriptive, name it after the deprecated-routes change.