chore: update cloudflared to 2026.5.2, refactor versions to current.ts pattern#25
Merged
Conversation
- Rename v2026.5.0.ts to current.ts with stable export name 'current' - Update index.ts to import from current instead of v2026.5.0 - Remove v2026.5.0.ts (replaced by current.ts) - Update release notes to include routes flatten fix Going forward, version bumps without migrations edit current.ts in place.
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
1 participant
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.
Changes
feat/routes_info)current.tspattern per StartOS packaging docs — latest version always lives incurrent.tswith a stable export name; historical version files only kept when needed for migrationsChecklist
npm run checkpasses2026.5.2:0downmigration is a no-op (rollback is possible)