Version: Latest (0.25 — Beta)0.240.230.220.210.200.190.180.170.160.150.140.130.120.110.100.9.40.9.30.9.10.9.00.8.0

Profiles 0.25.x (Beta) Changelog Beta

Version 0.25.0b1 (Beta)

10 December 2025
Schema version: 96

Release Schedule

A major re-architecture is introduced in this beta release. The core engine has been rebuilt from the ground up to support a powerful new capability — accessing and instantiating any past version of any model in your project.

Why this matters: This foundational change is essential for enabling true incremental computation. By tracking model versions over time, Profiles Builder (PB) can now intelligently determine what needs to be recomputed, dramatically improving performance and reducing costs for large-scale projects.

🔒 Safety First:

As this is a beta release with significant architectural changes, you must explicitly opt-in to use it. Set allow_beta: true in your pb_project.yaml or use the CLI beta flag.

What’s New

• Building Incremental Features is now possible.
• Added explicit consent requirement for beta releases: Users must now opt-in to run PB commands with a beta release, either by passing a CLI argument (--allow_beta) or by setting allow_beta: true in your pb_project.yaml file.

Bug Fixes

• Fixed a nil pointer exception in some cases while loading the projects
• Fixed an issue with Redshift during runs, where internal table creation fails if it already exists

Miscellaneous

• Major internal rearchitecture of PB to enable incremental support
• Propensity model’s internal training and prediction table names changed
• Model names and paths have changed for cohort and feature views. However, there will be no change in frontier view names to avoid impact on downstream pipelines.
• Removed unnecessary warning logs while loading projects
• Shows the right error message that explains why a project failed instead of showing context cancelled as the message

Known Issues

BigQuery

• pb validate access command does not work for BigQuery.

Redshift

• If two different users create material objects on the same schema, RudderStack gives an error during cleanup when trying to drop views created by the other user, like user_var_table.
• Cross-database references can fail on Redshift for a few clusters.
• While creating activations, validation for Redshift does not work correctly in the RudderStack dashboard.

Other issues

• Linux users might see this warning for all command runs — you can ignore it:

WARN[0000]log.go:228 gosnowflake.(*defaultLogger).Warn DBUS_SESSION_BUS_ADDRESS envvar looks to be not set, this can lead to runaway dbus-daemon processes. 

To avoid this, set envvar DBUS_SESSION_BUS_ADDRESS=$XDG_RUNTIME_DIR/bus (if it exists) or DBUS_SESSION_BUS_ADDRESS=/dev/null

• pb insert does not work for Redshift, Databricks, and BigQuery.
• If you are referring a public package in the project and get the ssh: handshake failed error, then you will have to manually remove the entire folder from WhtGitCache to make it work.

Questions? Contact us by Email or on Slack