Skip to content

v4-migrator: Skip repeatable Flyway migrations - #6967

Merged
nscuro merged 1 commit into
DependencyTrack:mainfrom
nscuro:v4-migrator-skip-repeatable-migrations
Aug 12, 2026
Merged

nscuro merged 1 commit into
DependencyTrack:mainfrom
nscuro:v4-migrator-skip-repeatable-migrations

Conversation

@nscuro

@nscuro nscuro commented Aug 12, 2026

Copy link
Copy Markdown
Member

Description

v4-migrator: Skip repeatable Flyway migrations.

Repeatable migrations (e.g. component metrics computation) always targets the latest schema version, whereas v4-migrator targets a specific (older) schema version.

Currently, repeatable migrations targeting the latest schema are attempted to be executed against an older schema as part of v4-migrator's bootstrap command. They are however not required for the v4 migration, so this failure mode is entirely avoidable by simply not executing them here.

Addressed Issue

N/A

Additional Details

N/A

Checklist

  • I have read and understand the contributing guidelines
  • This PR fixes a defect, and I have provided tests to verify that the fix is effective
  • This PR implements an enhancement, and I have provided tests to verify that it works as intended
  • This PR introduces changes to the database model, and I have updated the migration changelog accordingly
  • This PR introduces new or alters existing behavior, and I have updated the documentation accordingly
  • PR is a substantial change (per the ADR criteria), and I have added an ADR under docs/adr/

@nscuro nscuro added this to the 5.1 milestone Aug 12, 2026
@nscuro nscuro added the enhancement New feature or request label Aug 12, 2026
@owasp-dt-bot

owasp-dt-bot commented Aug 12, 2026 •

Copy link
Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@codacy-production

codacy-production Bot commented Aug 12, 2026 •

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Coverage 100.00% diff coverage · 0.00% coverage variation

Metric Results
Coverage variation ✅ 0.00% coverage variation (-1.00%)
Diff coverage ✅ 100.00% diff coverage (70.00%)

View coverage diff in Codacy

Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (504f17b) 43999 38337 87.13%
Head commit (4809d6c) 43999 (+0) 38336 (-1) 87.13% (0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#6967) 3 3 100.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

Repeatable migrations (e.g. component metrics computation) always targets the latest schema version, whereas v4-migrator targets a specific (older) schema version.

Currently, repeatable migrations targeting the latest schema are attempted to be executed against an older schema as part of v4-migrator's `bootstrap` command. They are however not required for the v4 migration, so this failure mode is entirely avoidable by simply not executing them here.

Signed-off-by: nscuro <nscuro@protonmail.com>
@nscuro
nscuro force-pushed the v4-migrator-skip-repeatable-migrations branch from b3e0451 to 4809d6c Compare August 12, 2026 13:40
@nscuro
nscuro merged commit 4f758cc into DependencyTrack:main Aug 12, 2026
16 checks passed
@nscuro
nscuro deleted the v4-migrator-skip-repeatable-migrations branch August 12, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants