Skip to content
Changelog

Java, Rails and PHP

Choose Java with Spring Boot, Ruby on Rails or Laravel as your stack, connect the registries that hold their private packages, and Taiga plans, builds and tests in them.

The Languages and frameworks picker, captioned What your teams build in. Drives the approved technologies in your engineering policies. Its choices are React, React Native, Next.js, Angular, Node.js, NestJS, Python, .NET, Go, Rust, Java, Ruby on Rails, Laravel and Other.

A Java, Rails or PHP team could only answer Other when Taiga asked for its stack. Its architecture policy then said nothing about its language, and the agents had no conventions to follow in its code.

Java with Spring Boot, Ruby on Rails and Laravel are now stack choices. Choosing one writes its approved tools and versions into your architecture policy, and the coding agent follows each framework's conventions. It installs dependencies from the repository's own lockfiles and runs the tests the repository uses: Maven or Gradle, RSpec or Minitest, PHPUnit or Pest. A change to the PHP in a Laravel app is checked by its PHP tests, not by the JavaScript suite beside it.

Private packages come with them. Maven, RubyGems and Composer registries connect alongside npm, Python and Go, and AWS CodeArtifact now works in every ecosystem it serves without a stored secret: Taiga assumes a role you create and gets tokens that expire within the hour.

A Java estate no longer has to call itself Other to be built.

Languages and frameworks →

Every change, dated the day it shipped.

Dated the day they shipped, newest first.