Profiles 0.25 Changelog Beta

Version 0.25.7

15 June 2026

Bug Fixes

• Projects that use case_based_join optimization no longer fail with an ambiguous column name error when an input’s id select reuses an id-stitcher column under a non-main_id type; the var-table → id-stitcher join keys are now properly qualified.

Version 0.25.6

4 June 2026

Bug Fixes

• To avoid out-of-memory issues on BigQuery, var-table bundles for inputs with no identifier column now generate input_row_id via the native GENERATE_UUID() instead of an unpartitioned ROW_NUMBER() OVER() window.

Version 0.25.5

29 Apr 2026

Bug Fixes

• Fixed a bug where features with non-default time grains were not getting included in the feature view.

Version 0.25.3

16 Apr 2026

Bug Fixes

• Fixed a bug to prevent an occurance of empty entity var bundle.

Version 0.25.2

15 Apr 2026

Miscellaneous

• Suppressed unnecessary warning logs.

Version 0.25.1

31 March 2026
Schema version: 97

Release Schedule

What’s New

• Incremental features: You can compute features incrementally. See Incremental Features for more details.
• You can now materialize ID stitcher models as tables instead of views. Configure via materialization: output_type: table on your ID stitcher model for better downstream query performance.
• Dry-Run Mode: New --mock_material_run flag (used with --assume_all_inputs_exist) lets you simulate a full pb run without executing any SQL against the warehouse. This is useful for validating project definitions, debugging model graphs, and testing configurations without live warehouse access.
• You no longer need to write {{entity.Var("var_name")}} — you can now simply use {{entity.var_name}} with dot syntax to access entity vars, input vars, and columns in SQL templates.

Miscellaneous

• Better error messages for incomplete incremental yaml configuration
• BigQuery legacy SQL queries have been migrated to GoogleSQL (standard SQL)
• Python models are removed

Bug Fixes

• GRPC connection issues and file path issues encountered on Windows are now fixed

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.