Skip to content

Fix the v2 privilege check, record metadata read failures, and analyze the catalog after publication - #4319

Merged
anth-volk merged 21 commits into
masterfrom
fix/v2-runtime-column-grants
Nov 17, 2026
Merged

anth-volk merged 21 commits into
masterfrom
fix/v2-runtime-column-grants

Conversation

@anth-volk

@anth-volk anth-volk commented Nov 16, 2026 •

Copy link
Copy Markdown
Collaborator

Fixes #4318

Summary

Every staging deploy since #4297 fails at the privilege check. The release run for 43473bb85 stopped in "Seed staging v2 database / Upgrade schema and seed v2 database", at scripts/reconcile_v2_privileges.py verify:

policyengine_v2_runtime holds UPDATE on the whole of user_type_changes, which overrides its declared columns

The manifest lets the runtime role update only dismissed_at on user_type_changes. But the Supabase projects' default privileges give policyengine_v2_runtime SELECT, INSERT, UPDATE and DELETE on every table the migration role creates. apply reported the whole-table UPDATE without revoking it, so verify failed. user_type_changes is the first table where the manifest limits the runtime role's UPDATE to named columns. The disposable test database has no default privileges, so CI didn't catch it.

Change

apply now revokes a privilege a role holds directly on a whole table when the manifest declares it for named columns only. It does this before granting, in the same transaction:

  • Planning: plan_reconciliation adds two fields. revocations holds the whole-table privileges to revoke. revoked_columns holds the undeclared column grants that PostgreSQL's REVOKE on a table also removes. The declared columns go back into grants, because the revoke removes them too.
  • Statements: revoke_statements writes one REVOKE per role and table, using the same identifier checks as the grants.
  • Job summary: a new "Revoked" table lists each revoke with the column grants it removed. It appears only when something is revoked.
  • Unchanged: every other undeclared privilege is still reported, not revoked; DELETE on user_type_changes stays. verify is unchanged, so it still fails when a role keeps the whole-table privilege another way: through a role it belongs to, or through a grant another role made, which the owner's REVOKE doesn't remove.
  • Docs: the privileges and privilege_reconciliation docstrings, the statement of rule api.v2.deployed-privileges-match (with docs/generated/rules.md regenerated) and the "Table privileges" section of the Alembic migrations skill document describe the revoke.

Deploy

  • Staging: the next release run's apply revokes the runtime role's whole-table UPDATE on user_type_changes and grants UPDATE (dismissed_at) again; verify then passes.

  • Production: its first upgrade to f519a77ba122 creates the table with the default privileges, and the same apply step revokes the whole-table UPDATE before verify runs.

  • Permission to revoke: the migration role owns every table. Grants that default privileges create, and grants a superuser makes, record the owner as grantor, so the owner's REVOKE removes them.

  • Environment variables: none added; the workflows are unchanged. The script still reads these:

    • V2_MIGRATION_DATABASE_URL: a GitHub Actions environment secret, set in each step's env: in seed-v2-database.yml, which push.yml calls with secrets: inherit;
    • DEPLOYMENT_ENVIRONMENT: the workflow input;
    • V2_SUPABASE_PROJECT_REF, V2_SUPABASE_ENVIRONMENT and PRODUCTION_V2_SUPABASE_PROJECT_REF: GitHub Actions variables, set in the job's env:.

    The failing staging run's log shows each of them set in the apply step.

Also: record why a v2 metadata read answered 503 or 500

The other staging failure after #4303: release run 43915927273 stopped at tests/integration/test_live_v2_metadata.py::test_live_v2_resources_use_the_deployed_policyengine_version[us]. Staging answered GET /v2/parameter-values?country_id=us&limit=1 with the generic 503 "V2 metadata catalog is unavailable" (2026-11-16 21:30:13 Azerbaijan time, UTC+4).

  • PostgreSQL logged no error.
  • The connection pooler logged the API disconnecting cleanly, mid-query, 7 ms after the 503.
  • So the driver raised inside the API, SQLAlchemy discarded the connection, and run_metadata_read turned the error into the generic 503 without recording it.

The query's 45-second runtime on staging was fixed separately, by refreshing table statistics.

run_metadata_read now records one runtime event at ERROR, v2_metadata_read_failed, for each generic 503 and each 500 ("V2 metadata query failed"). It goes through policyengine_api.fastapi_routes.v2.metadata.read_failure_support, and the runtime adds the request's ID, method and matched route. The event adds:

  • http.response.status_code;
  • error_type: the caught error's class, as module.QualifiedName;
  • failure_category: v2_metadata_catalog_unavailable for the 503, or v2_metadata_query_failed for the 500. The scheduled error-issue job (.github/scripts/telemetry_error_issues) groups an event by its route, error_type and failure_category, the keys the API's other events use, so 503s, 500s and different causes open separate issues;
  • error.cause_types: the classes of its __cause__ chain, outermost first;
  • database.sqlstate: the first SQLSTATE in the chain;
  • database.connection_invalidated: whether SQLAlchemy found the connection lost.

What it leaves out:

  • It records no error message. SQLAlchemy's and the driver's messages carry the statement and its parameters, and can carry hosts, addresses and credentials. The attributes are read by name, so the route layer imports neither SQLAlchemy nor a driver.
  • A pruned version, or a missing parameter tree or search file, already answers with its own message, and records nothing. One helper, _caller_message, decides both.
  • On the two routes that share one read of a whole catalog version, only the request that ran the failed read records it; requests that waited for it answer with a copy of its 503.
  • Recording never changes the response.
  • No retry on a lost connection, and no ANALYZE after catalog publication.

Tests: tests/unit/v2/test_metadata_read_failure_events.py serves each request through a runtime with the process runtime's settings that writes its records to a list, so the tests see the event exactly as written, request context included. For that, the route fixture takes an optional observability_runtime. The lost connection is psycopg's real AdminShutdown (SQLSTATE 57P01), wrapped by SQLAlchemy's DBAPIError.instance.

The tests before the change:

FAILED tests/unit/v2/test_metadata_read_failure_events.py::test_a_lost_connection_answers_the_same_503_and_records_its_cause
FAILED tests/unit/v2/test_metadata_read_failure_events.py::test_an_unexpected_failure_answers_the_same_500_and_records_its_cause
FAILED tests/unit/v2/test_metadata_read_failure_events.py::test_a_failure_without_a_database_cause_records_only_its_class
3 failed, 2 passed in 1.85s

The two that passed check behaviour the change must keep: a pruned version records nothing, and a failing runtime leaves the 503 unchanged.

Review round 1 found that the error-issue job couldn't group the event, because it had no error_type or failure_category. It also asked for the cases below to be covered. The updated tests, before that fix:

FAILED tests/unit/v2/test_metadata_read_failure_events.py::test_a_lost_connection_answers_the_same_503_and_records_its_cause
FAILED tests/unit/v2/test_metadata_read_failure_events.py::test_an_unexpected_failure_answers_the_same_500_and_records_its_cause
FAILED tests/unit/v2/test_metadata_read_failure_events.py::test_a_failure_without_a_database_cause_records_only_its_class[catalog-unavailable]
FAILED tests/unit/v2/test_metadata_read_failure_events.py::test_a_failure_without_a_database_cause_records_only_its_class[configuration]
FAILED tests/unit/v2/test_metadata_read_failure_events.py::test_a_cause_chain_that_loops_back_names_each_error_once
FAILED tests/unit/v2/test_metadata_read_failure_events.py::test_a_long_cause_chain_names_its_first_errors_only
6 failed, 5 passed in 2.92s

The new tests cover a configuration error, the parameter-tree and search-file answers, a failing runtime on the 500, and cause chains that loop or run long.

After it:

11 passed in 3.10s

Also: refresh the catalog tables' statistics after a publication

The cause of that 503's slow query. PostgreSQL's autovacuum analyzes a table again only after about a tenth of its rows have changed. parameters on staging holds about 1.25 million rows, because it keeps every published version, and each PolicyEngine.py release adds about 105,000. So after 6.17.1 was published on 2026-11-10, its rows never reached the statistics:

  • The bad plan: the planner estimated 1 parameter row for US 6.17.1 when there were 102,530. It chose to fetch and sort every parameter value of that version, so GET /v2/parameter-values?country_id=us&limit=1 took 43 to 47 seconds on every release from 2026-11-10 to 2026-11-16.
  • After a manual ANALYZE parameters on staging (2026-11-17 01:28:59 Azerbaijan time, UTC+4), the same query walks uq_parameters_model_version_name and takes 4.1 ms (UK: 4.9 ms).
  • Production can reach the same state after any release.

publish_catalog now runs one ANALYZE over datasets, parameter_nodes, parameter_tree_children, parameter_values, parameters, regions and variables (policyengine_api/data/v2/catalog/publication_statistics.py):

  • When: on every publication, once it has committed and pruning has run. It takes a few seconds and blocks no reads.
  • Why every run: a failed ANALYZE is then repeated by the next publication. If it ran only after a run that changed a version, a retry that changed nothing would leave the statistics stale.
  • Summary: the printed JSON lists the tables in the new catalog_tables_analyzed field.
  • A failed ANALYZE: it doesn't undo or fail the publication, just as a failed pruning doesn't. catalog_tables_analyzed is then empty, and the new catalog_statistics_failure field names the failure's class, never its message.
  • Privilege: ANALYZE needs the table's owner or MAINTAIN; PostgreSQL skips any other table with only a warning. PostgreSQL 17 has no narrower privilege, and MAINTAIN also allows VACUUM (FULL included), CLUSTER, REINDEX, REFRESH MATERIALIZED VIEW and LOCK TABLE on those tables, though publication runs only ANALYZE. The migration role owns these tables, and publication connects as policyengine_v2_catalog_writer. So the manifest now declares MAINTAIN (PostgreSQL 17; staging runs 17.6, and both Supabase projects report engine 17) for the catalog writer on the seven tables.
  • Order in the deploy: the seed job's apply step grants MAINTAIN and verify checks it, both before publication runs.
  • Failure: publication checks the privilege with has_table_privilege before it writes anything, and fails, naming the tables, when its role lacks it.

Out of scope: retrying on a lost connection.

Environment variables: none added. The workflow change only adds tests/integration/test_v2_catalog_statistics.py to an existing step of v2-integration-check.yml. That step's V2_MIGRATION_DATABASE_URL, V2_ALEMBIC_DISPOSABLE_TEST and DEPLOYMENT_ENVIRONMENT are literal job env: values for its own PostgreSQL service container. Publication still reads V2_DATA_WRITE_DATABASE_URL, a GitHub Actions environment secret set in its step's env: in seed-v2-database.yml.

Tests, before the change:

FAILED tests/unit/v2/test_privilege_manifest.py::test_the_catalog_writer_may_analyze_the_tables_publication_refreshes
FAILED tests/integration/test_v2_catalog_statistics.py::test_publishing_a_new_version_as_the_catalog_writer_analyzes_the_catalog
FAILED tests/integration/test_v2_catalog_statistics.py::test_republishing_an_unchanged_catalog_analyzes_nothing
FAILED tests/integration/test_v2_catalog_statistics.py::test_a_role_that_cannot_analyze_the_catalog_fails_before_writing
4 failed in 1.38s

Review round 1 found that a failed ANALYZE was never repeated, and that two existing unit tests pin the catalog writer's privileges and the evidence fields. The updated tests, before that fix:

FAILED tests/unit/v2/test_catalog_publication.py::test_completion_evidence_contains_only_reviewed_non_secret_fields
FAILED tests/integration/test_v2_catalog_statistics.py::test_republishing_an_unchanged_catalog_analyzes_it_again
FAILED tests/integration/test_v2_catalog_statistics.py::test_a_failed_analyze_is_recorded_and_the_publication_kept
3 failed, 4 passed in 1.54s

After it:

7 passed in 1.54s

What the PostgreSQL tests check:

  • The tests run on PostgreSQL 17 and publish as the catalog writer role.
  • After a new version, pg_stat_user_tables.last_analyze is newer than the publication's start for each of the seven tables.
  • An unchanged republication analyzes again.
  • A failed ANALYZE is recorded while the publication is kept.
  • A role holding every catalog-writer privilege except MAINTAIN fails before writing any version.

Also: the PolicyEngine bundle update to 6.20.0

The simulation API now serves PolicyEngine .py 6.20.0 (PolicyEngine/policyengine-sim-api#1076, deployed once PolicyEngine/policyengine-sim-api#1088 removed the checks that had stopped it). The required check "Ensure PolicyEngine bundle is the simulation API's latest" therefore fails on 6.17.1, and CI skips the test jobs that wait on it. This pull request merges the branch of the automated update #4315 unchanged: the pin in pyproject.toml and docker/Dockerfile, uv.lock and its changelog fragment, with policyengine 6.20.0, policyengine-core 3.33.3, policyengine-us 2.2.2 and policyengine-uk 2.174.1. Once this merges, #4315 (and its issue #4314) has nothing left to merge.

Every test this pull request adds or changes passes on 6.20.0, and the Hugging Face credential check still resolves the default UK dataset to microcosm_uk_2024_25.h5 at microcosm-uk-2024-25-national-20261107T020434Z-eeb6093e.

Testing

  • Reproduction:
    • Setup: a disposable PostgreSQL 17 database at master's v2 head (f519a77ba122). I gave policyengine_v2_runtime what the default privileges give on user_type_changes.
    • Before the fix: apply then verify failed as in staging.
    • With the fix: the first apply revoked the whole-table UPDATE and granted UPDATE (dismissed_at) again, a second apply changed nothing, and verify passed. The runtime role can update dismissed_at and no other column.
  • Tests: every added or changed test passes, run by node ID: 28 in all, 7 for the privileges, 12 for the failure event and 9 for the statistics. Each new test was seen failing first; the two other sections show their red and green output. test_apply_revokes_a_new_tables_whole_table_update_and_verify_passes starts from staging's state: whole-table privileges, the declared column grant and an undeclared one. test_column_and_whole_table_privileges_beyond_the_manifest_are_reported now uses an extra whole-table DELETE, because apply now revokes the whole-table UPDATE that test used.
  • Static checks: ruff, ruff format, lint-imports, python -m scripts.rules validate, python scripts/run_quality_guards.py and mypy all passed.
  • Reviews: the failure event and the statistics refresh had two rounds each. Each first round found one bug, fixed test-first: the error-issue job couldn't group the event, a failed ANALYZE was never repeated, and two pinned unit tests broke. Neither second round found a bug. The privilege fix had two rounds of review, neither of which found a bug. Their fixes are included:
    • the summary lists the removed column grants;
    • the PostgreSQL test starts from staging's state;
    • docstring and documentation wording.

🤖 Generated with Claude Code

github-actions Bot and others added 5 commits November 16, 2026 16:23
…ing)

A new table's default privileges give the runtime role UPDATE on the
whole table. Where the manifest declares UPDATE on named columns only, as
for user_type_changes, apply reports that privilege but never revokes it,
so verify fails every deploy. These tests expect apply to revoke it, grant
the declared columns again, and leave every other extra privilege.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The projects' default privileges give the runtime role UPDATE on every
new table, including user_type_changes, where the manifest allows it to
update only dismissed_at. apply reported that privilege without revoking
it, so verify failed every staging deploy after the invitations revision.

apply now revokes a whole-table privilege a role holds directly when the
manifest declares it for named columns only, then grants those columns
again in the same transaction, since PostgreSQL's REVOKE on a table also
removes the role's column grants of it. The job summary lists the revoke.
Every other undeclared privilege is still reported, not revoked, and
verify still fails if a role keeps the whole-table privilege another way.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The job summary now lists the undeclared column grants a revoke removes,
the PostgreSQL test starts from staging's state (whole-table privileges
plus a declared and an undeclared column grant), the planned-revoke test
uses a state that can occur, and the privileges module, rule statement and
skill document say which grants the revoke removes and that a grant
another role made survives it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@codecov

codecov Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 97.12794% with 33 lines in your changes missing coverage. Please review.
✅ Project coverage is 93.60%. Comparing base (d7042b2) to head (473b56c).
⚠️ Report is 57 commits behind head on master.

Files with missing lines Patch % Lines
policyengine_api/libs/postmark_email.py 91.09% 9 Missing and 4 partials ⚠️
...ngine_api/services/v2/user_invitations/services.py 96.00% 4 Missing and 1 partial ⚠️
policyengine_api/fastapi_routes/dependencies.py 60.00% 4 Missing ⚠️
policyengine_api/data/v2/privilege_plans.py 81.25% 0 Missing and 3 partials ⚠️
...ine_api/services/v2/user_invitations/validators.py 95.23% 2 Missing and 1 partial ⚠️
...licyengine_api/services/v2/user_emails/services.py 97.53% 2 Missing ⚠️
...gine_api/data/v2/catalog/publication_statistics.py 97.14% 0 Missing and 1 partial ⚠️
...api_routes/v2/admin_invitations/response_models.py 97.29% 0 Missing and 1 partial ⚠️
...s/v2/user_invitations/database_connectors/reads.py 94.44% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #4319      +/-   ##
==========================================
+ Coverage   93.47%   93.60%   +0.12%     
==========================================
  Files         369      389      +20     
  Lines       21455    22486    +1031     
  Branches     3400     3535     +135     
==========================================
+ Hits        20056    21048     +992     
- Misses        816      844      +28     
- Partials      583      594      +11     
Flag Coverage Δ
integration 57.00% <64.05%> (+0.38%) ⬆️
unit 91.22% <95.99%> (+0.18%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

anth-volk and others added 14 commits November 17, 2026 01:34
On 2026-11-16 staging answered GET /v2/parameter-values with the generic
503 "V2 metadata catalog is unavailable" after the database connection
was lost mid-query, and nothing recorded the error behind it. These tests
expect one runtime event per generic 503 or 500 with the route, the
caught error's class, its cause chain's classes, the SQLSTATE and
SQLAlchemy's lost-connection flag, and no error message.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The process's runtime writes to the stream it saved at start-up, which
pytest's output capture can't read, so the tests serve their requests
through a runtime configured the same way but writing to a list. The
route fixture takes that runtime as an optional argument.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
run_metadata_read turned a lost database connection into the generic
503 "V2 metadata catalog is unavailable", and any unexpected error into
the 500 "V2 metadata query failed", recording neither. Each such answer
now records one runtime event, v2_metadata_read_failed, at ERROR, with
the response status, the caught error's class, the classes of its cause
chain, the first SQLSTATE in the chain and SQLAlchemy's lost-connection
flag; the runtime adds the request's ID, method and route. It records no
error message, since SQLAlchemy's and the driver's carry the statement,
its parameters and connection details. A pruned version or a missing
parameter tree or search file still answers with its own message and
records nothing. Recording never changes the response.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The user asked for the metadata read failure event to go into this pull
request too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ling)

PostgreSQL re-collects a table's statistics only after about a tenth of
its rows change, and parameters keeps every published version, so one
release's rows never triggered it on staging: after 6.17.1 the planner
estimated 1 US parameter row instead of 102,530, and the parameter-values
list took 43-47 s. These tests expect publication, running as the catalog
writer, to ANALYZE the catalog tables after a run that adds a version,
to analyze nothing when nothing changed, and to fail before writing when
its role can't analyze them. The new test file joins the v2 integration
job.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PostgreSQL's autovacuum analyzes a table again only after about a tenth
of its rows change, and parameters keeps every published version, so on
staging the planner never saw 6.17.1's 102,530 US parameter rows and
GET /v2/parameter-values?country_id=us&limit=1 took 43-47 s on every
release from 2026-11-10 to 2026-11-16; after a manual ANALYZE it takes
4.1 ms.

A publication that publishes, restores or prunes a version now runs one
ANALYZE over datasets, parameter_nodes, parameter_tree_children,
parameter_values, parameters, regions and variables after it commits and
prunes, and lists them in the evidence's catalog_tables_analyzed. ANALYZE
needs the owner or MAINTAIN, and PostgreSQL skips any other table with
only a warning; the migration role owns the tables, so the manifest
grants the catalog writer MAINTAIN on these seven (PostgreSQL 17), and
publication fails before writing anything if its role lacks it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The scheduled error-issue job groups an event by its route and its
attributes.error_type and attributes.failure_category, and the failure
event had neither, so every 503 and 500 on a route would have merged
into one issue. The tests now expect error_type and a failure category
that tells a catalog outage from an unexpected failure. They also use
psycopg's real AdminShutdown wrapped as SQLAlchemy wraps it, keep the
process runtime's settings, and cover a configuration error, the
parameter tree and search file answers, the 500 with a failing runtime,
and looping and long cause chains.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The event now carries error_type and failure_category, the keys the
API's other events use and the scheduled error-issue job groups by, so
503s and 500s on a route, and different causes, stay apart. One helper,
_caller_message, now decides both which answers have their own message
and which record the event. The observability and v2 code-organization
guides describe the event and its module, including that requests
waiting on a shared whole-version read answer with a copy and record
nothing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A failed ANALYZE after the catalog committed failed the command, and the
retry, which changed nothing, analyzed nothing, leaving the statistics
stale. The tests now expect every publication to analyze, a failed
ANALYZE to be recorded by its class while the publication is kept, and
the evidence to carry both. The catalog writer's pinned privileges and
the evidence's pinned fields now include MAINTAIN and the new fields,
and the manifest test checks the grant against the module's table list.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A failed ANALYZE after the catalog committed failed the command and was
never repeated, because the retry changed nothing and so analyzed
nothing. Every publication now analyzes the catalog tables once it has
committed and pruned, which takes seconds and blocks no reads, and a
failure is returned rather than raised: the evidence lists no tables and
names the failure's class in catalog_statistics_failure, as a failed
pruning is reported, and the next publication analyzes again.

The privileges comment and the Stage 9 document now say that MAINTAIN
also allows VACUUM, CLUSTER, REINDEX, REFRESH MATERIALIZED VIEW and LOCK
TABLE, PostgreSQL 17 having no narrower privilege, and the evidence list
names the two new fields.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…iling)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
catalog_statistics_failure now names the class of the error the database
driver raised and its SQLSTATE, as a failed pruning is reported, since
SQLAlchemy's own class is the same for every database error, and the
command prints the failure to stderr while still succeeding. Two
descriptions still said the writer analyzes only the tables publication
grows; it analyzes seven tables after every publication.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… fix

The user asked for the statistics refresh to go into this pull request
too, in commits of its own.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@anth-volk anth-volk changed the title Revoke whole-table privileges the v2 manifest declares for named columns Fix the v2 privilege check, record metadata read failures, and analyze the catalog after publication Nov 16, 2026
Codecov reported changed lines no test ran. Locally, two of them were:
an ANALYZE failure that isn't a database error, named by its class
alone, and a cause chain that loops back to an error partway along.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The simulation API now serves PolicyEngine .py 6.20.0, and the check that
the Public API's bundle is the simulation API's latest fails on 6.17.1.
This brings in the automated update of #4315 unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@anth-volk
anth-volk marked this pull request as ready for review November 17, 2026 07:21
@anth-volk
anth-volk requested a review from a team as a code owner November 17, 2026 07:21
@anth-volk
anth-volk merged commit cb7df89 into master Nov 17, 2026
24 checks passed
@anth-volk
anth-volk deleted the fix/v2-runtime-column-grants branch November 17, 2026 07:21
anth-volk added a commit that referenced this pull request Nov 17, 2026
…anch

Both sides added test modules to the same v2 integration step; the step
now runs master's catalog statistics module and C1 · 28's six modules.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch was previously deployed

1 inactive deployment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

v2 deploys fail privilege verification: the runtime role holds UPDATE on all of user_type_changes

1 participant