docs: BigQuery package settings added in 0.26.1

[EladBarkay]

Documents three BigQuery changes in dbt package 0.26.1 (CORE-1565). Each one goes on the page where an affected user would look:

• data-tests/dbt/on-run-end_hooks.mdx gets a new Long invocations on BigQuery section for the temp_table_expiration_hours var (dbt-data-reliability#1059).
• data-tests/anomaly-detection-tests/Anomaly-troubleshooting-guide.mdx gets a new accordion about anomaly tests that scan the whole table or fail on require_partition_filter. It covers fix_nanosecond_timing_values and bigquery_truncate_nanosecond_timestamps, in the order they must run (dbt-data-reliability#1077, issue [ELE-1434] Make DbtRunner install the dbt packages if needed. #1039).
• data-tests/dbt/package-models.mdx gets a new accordion under test_result_rows: elementary_test_results and test_result_rows are now partitioned on created_at. Existing tables need a manual rebuild, and a full refresh would delete history (dbt-data-reliability#1057).

Merge only after package 0.26.1 is published, since the pages refer to it.

🤖 Generated with Claude Code

[linear]

CORE-1565

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Essentials
• Run ID: eb0e3447-57a2-45ab-b6a3-bdbd5d26e570

---

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}

[GuyEshdat]

this may not be required if the data is already fixed for the last X days and the time range in of the report for that user is less than X, indicate it here

[EladBarkay]

Agreed. Step 1 is now "If needed", with a note that you can skip it when no rows with nanosecond values are within the time range your reports and alerts read (days_back): for example, if you upgraded to 0.26.1 longer ago than that, or never ran an earlier version with dbt Fusion / dbt Core 1.11. The warning now applies only to that case too. Fixed in 0fed0aa.