docs(self-hosted): Add 26.5.1 as a hard stop for upgrades#17988
docs(self-hosted): Add 26.5.1 as a hard stop for upgrades#17988vgrozdanic wants to merge 1 commit into
Conversation
Add version 26.5.1 to the list of hard stops that users must upgrade through when upgrading their self-hosted Sentry installation. Co-Authored-By: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 40b162795f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - 23.11.0 | ||
| - 24.8.0 | ||
| - 25.5.1 | ||
| - 26.5.1 |
There was a problem hiding this comment.
Adding 26.5.1 to the Hard Stops list introduces a new upgrade requirement in develop-docs/, but the repo's AGENTS.md says that when requirements are added to an existing develop-docs/ file, the file must include the RFC 2119 Alert if it is missing and use bold uppercase requirement keywords. This page still has no such alert, so this requirements page is now out of compliance; add the standard Alert near the top of the file and adjust the requirement wording if needed.
Useful? React with 👍 / 👎.
2 participants
DESCRIBE YOUR PR
Adds version
26.5.1to the list of hard stops in the self-hosted upgrading documentation. Users who are upgrading their self-hosted Sentry installation must pass through this version to pick up significant database changes.I have started squashing migrations, so we need to set some date until which it's safe to squash all the migrations.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: