You are viewing documentation for an older version.
Profiles 0.23.x Changelog
2 minute read
- Last modified: Aug 7, 2026
Version 0.23.3
2 Oct 2025
Bug Fixes
- Fixed an issue where enabling ID stitcher metadata resulted in a SQL error.
Version 0.23.2
18 Sep 2025
Bug Fixes
- Fixed an issue where referencing models in a case-insensitive manner caused errors.
- Resolved a regression affecting PyNative package registration.
Version 0.23.1
9 September 2025
Schema version: 92
Release Schedule
| Milestone | Date |
|---|---|
| CLI release | September 9, 2025 |
| Deployment to dev workspaces | September 10, 2025 |
| Deployment to production workspaces | September 15, 2025 |
What’s New
- Added metadata in ID stitcher internal mapping table — this metadata helps you understand how identifiers are connected and trace the lineage of your identity graph. To enable, toggle on
log_direct_edge_infoandlog_node_metadataflags under id stitcher model spec. An example is shown below:
models:
- name: user_id_stitcher
model_type: id_stitcher
model_spec:
entity_key: user
log_direct_edge_info: true
log_node_metadata: truepb show models --treeprints output in a tree format.- Added support for hooks on feature-views. An example is shown below:
entities:
- name: user
id_stitcher: models/test_id__
feature_views:
hooks:
pre_run: "CREATE OR REPLACE VIEW {{warehouse.NamedWhObject(name='x1', type='VIEW')}} AS (SELECT 1 as testCol);"
post_run: "CREATE OR REPLACE VIEW {{warehouse.NamedWhObject(name='x2', type='VIEW')}} AS (SELECT 1 as testCol);"- Removed ID collator as a model type.
- PB logs are now redirected to
stderr.pb show models --json > output.jsonoutput is a valid JSON file now.
Bug Fixes
- Fixed the bug wherein a non-converged ID graph (after maximum iterations) resulted in an error.
Known Issues
BigQuery
pb validate accesscommand 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/nullpb insertdoes not work for Redshift, Databricks, and BigQuery.- If you are referring a public package in the project and get the
ssh: handshake failederror, then you will have to manually remove the entire folder fromWhtGitCacheto make it work.