Renumber #15058 migration and move release notes to 3.1.x#15108
Merged
Conversation
PR #15058 was branched from an older base: its migration was numbered 0270 (depending on 0269) and its upgrade notes targeted 3.2.x. On dev this collided with the existing 0270_finding_visibility_perf_indexes / 0271_finding_perf_indexes migrations (two 0270 leaf nodes break the migration graph), and dev is 3.1.0-dev, not 3.2. - Rename 0270_reencrypt_tool_config_credentials_aes_gcm -> 0272 and depend on 0271_finding_perf_indexes, restoring a linear chain. - Update the migration-name references in dojo/utils.py (0270 -> 0272). - Merge the AES-256-GCM upgrade notes into 3.1.md (fixing the migration name and release-tag link) and delete 3.2.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
github-actions
Bot
added
New Migration
devGregA
approved these changes
Jun 30, 2026
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
3 participants
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.
Summary
The dev branch was broken by the premature merge of #15058, which was branched from an older base. This corrects the migration numbering and release-notes version to match dev (
3.1.0-dev).0270_reencrypt_tool_config_credentials_aes_gcmdepending on0269, but dev already has0270_finding_visibility_perf_indexesand0271_finding_perf_indexes— two0270leaf nodes break the migration graph. Renamed to0272_reencrypt_tool_config_credentials_aes_gcmand re-pointed its dependency to0271_finding_perf_indexes, restoring a linear chain (0269 → 0270 → 0271 → 0272).0270→0272references indojo/utils.py(REMOVAL TRACKING note + legacy read-path comment).3.1.0-dev, not3.2. Merged the "Tool Configuration credentials upgraded to AES-256-GCM" section into3.1.md(fixing the in-text migration name to0272and the release-tag link to3.1.0), updated the3.1.mdfrontmatter description, and deleted3.2.md.No changes to the encryption logic, requirements bumps, or tests.
🤖 Generated with Claude Code
[sc-13319]