flyway/11.3.0 package update

[octo-sts]

[octo-sts]

⚠️ EXPERIMENTAL

Please use 👍 or 👎 on this comment to indicate if you agree or disagree with the recommendation.

To provide more detailed feedback please comment on the recommendation prefixed with /ai-verify:

e.g. /ai-verify partially helpful but I also added bash to the build environment

Gen AI suggestions to solve the build error:

• Detected Error: "Could not transfer artifact org.flywaydb:flyway-database-ignite:pom:10.17.0 from/to flyway-community-db-support (https://maven.pkg.github.com/flyway/flyway-community-db-support): status code: 401, reason phrase: Unauthorized (401)"

• Error Category: Dependency Resolution/Authentication

• Failure Point: Maven dependency resolution during build, specifically when trying to fetch the flyway-database-ignite dependency

• Root Cause Analysis: The build is failing because it's trying to access a private GitHub package repository without proper authentication. Flyway has moved some database support packages to a separate repository that requires authentication.

• Suggested Fix:

1. Add -pl !flyway-database-ignite to the Maven command in the build pipeline to exclude the ignite module:

  - name: Install
    runs: |
      # Build flyway
      ./mvnw -B clean dependency:copy-dependencies package -e --file pom.xml -DskipTests -pl !flyway-database-mongodb,!flyway-database-ignite

• Explanation: By excluding the ignite module from the build, we avoid the need to authenticate against the private repository. The ignite module is not required for core Flyway functionality and is part of Flyway Teams edition.

• Additional Notes:

• This is a common issue with Flyway 11+ as some database support has been moved to separate repositories
• The exclusion won't affect core Flyway functionality
• Alternative approach would be to provide GitHub authentication, but that's not necessary for basic Flyway usage
• The changed command maintains compatibility with Flyway's open-source feature set

• References:

• Flyway Community vs Teams Edition: https://documentation.red-gate.com/fd/community-vs-teams-178727125.html
• Similar Issue: flyway desktop can't use AD-auth flyway/flyway#3844

[OddBloke]

The build is failing because we get a 401 when we attempt to fetch packages from maven.pkg.github.com. However, I think Maven is only trying to hit GitHub's (private?) package repository because not all of the 10.17.0 packages for flyway-community-db-support have been published to Maven Central, so it's falling back. I've filed flyway/flyway-community-db-support#77 upstream to report the problem.

[octo-sts]

superseded by #41271