Skip to content

Release v1.7.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 25 Sep 15:34
v1.7.1
31eabaf
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Newly scaffolded projects now come with setup instructions that match what the templates actually generate. Every template was scaffolded, built, and run to check them. Projects you have already created are unaffected.

Changed

  • The README.md generated into every project lists the prerequisites the templates really need: the .NET 10 SDK (every .NET template targets net10.0), JDK 17 for the Kotlin and Java templates, Docker with the Compose plugin, and Node.js ^20.19.0 or >=22.12.0
  • The post-creation instructions and generated READMEs use docker compose instead of the standalone docker-compose command
  • The generated READMEs now show expected output, the Chronicle health check, how to stop without losing data, and a warning that the development containers publish their ports on every network interface with well-known credentials
  • The Kotlin and Java READMEs explain that the Cratis Gradle plugin and dependency float on latest.release, how Gradle caches that, and how to pin versions for reproducible builds
  • The template documentation's getting-started page is now a step-by-step tutorial that ends with a registered item. Each template page lists its options, how to run it, and troubleshooting

Fixed

  • The generated READMEs gave the wrong frontend port: the Vite dev server runs on http://localhost:9000, not 5173, and run.sh in the Kotlin and Java templates now prints the right port
  • The documentation pointed to dotnet new cratis-kotlin and dotnet new cratis-java, which do not exist. The command is dotnet new cratis --language Kotlin or --language Java, and Cratis.Templates already includes both
  • The documentation stated fixed versions for the Kotlin and Java templates (Arc 7.2.0 with Chronicle 4.0.0), but those templates resolve the latest Cratis release when they build
  • cratis new examples now include the required --language option
  • The TypeScript command example in the web template documentation now compiles against the generated proxy
  • The Aspire template README gave a fixed dashboard address; Aspire prints a dashboard link with a login token and a different port each run
  • Links in the generated READMEs that pointed to retired cratis.io/docs/... pages now point to the current Arc, Chronicle, and template documentation
  • The AI setup table listed the wrong profile for the Java template; it uses cratis/application/java
  • The generated READMEs and documentation now describe known problems in the templates:
    • With the Yarn 2+ default Plug'n'Play mode, yarn build fails. Add nodeLinker: node-modules to fix it
    • The default MongoDB variant of cratis-aspire stops at startup
    • Read-model queries fail in the PostgreSQL variant of cratis
    • The cratis-aspire SQL variants keep Cratis.Arc.EntityFrameworkCore unpinned
Assets 2
Loading