Skip to content

Migrate CI from Travis CI to GitHub Actions#145

Draft
RadikalJin wants to merge 1 commit into
mainfrom
chore/migrate-travis-to-github-actions
Draft

Migrate CI from Travis CI to GitHub Actions#145
RadikalJin wants to merge 1 commit into
mainfrom
chore/migrate-travis-to-github-actions

Conversation

@RadikalJin
Copy link
Copy Markdown
Member

Replace three outdated workflow files (build.yml, deploy.yml, pr-build.yml) and .travis.yml with a single consolidated .github/workflows/ci.yml that:

  • Uses actions/checkout@v4 and actions/setup-java@v4 (current best practice)
  • Upgrades from Java 17 to Java 21 to match the Travis CI configuration
  • Uses setup-java built-in Maven cache instead of a separate cache step
  • Restores GPG key import in the deploy job (was commented out in old deploy.yml)
  • Adds a repository owner guard on deploy to prevent forks from triggering releases
  • Triggers on push to main, all tag pushes, and pull_request to main

Replace three outdated workflow files (build.yml, deploy.yml, pr-build.yml)
and .travis.yml with a single consolidated .github/workflows/ci.yml that:

- Uses actions/checkout@v4 and actions/setup-java@v4 (current best practice)
- Upgrades from Java 17 to Java 21 to match the Travis CI configuration
- Uses setup-java built-in Maven cache instead of a separate cache step
- Restores GPG key import in the deploy job (was commented out in old deploy.yml)
- Adds a repository owner guard on deploy to prevent forks from triggering releases
- Triggers on push to main, all tag pushes, and pull_request to main

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant