Render.yaml changes doesn't trigger build

1

We have noticed a bug with how Render handles changes in the render.yaml file to trigger builds.

The docs say in https:// render .com/docs/monorepo-support#can-i-ignore-the-renderyaml-file

Can I ignore the render.yaml file?
No, changes to render.yaml are always processed regardless of the patterns specified in buildFilter. Blueprint syncs are also unaffected by the buildFilter setting.

But in practice, we have examples where a change in render.yaml doesn’t trigger a build for the affected service. For instance, https:// github .com/mui/mui-private/pull/1122 has the following diff:

diff --git a/render.yaml b/render.yaml
index 212bee7a..a7e3d3ac 100644
--- a/render.yaml
+++ b/render.yaml
@@ -319,6 +319,8 @@ services:
    type: web
    name: mui-reverse-proxy
    buildFilter:
      paths:
        - apps/reverse-proxy/**
     domains:
       - llms.mui.com
     healthCheckPath: /health-check
+    envVars:
+      - fromGroup: AXIOM
   # MUI DataGrid API Key Value
   - name: mui-api-key-value
     type: keyvalue
@@ -414,3 +416,10 @@ envVarGroups:
     envVars:
       - key: MUI_DATAGRID_API_KEY
         sync: false
+  - name: AXIOM
+    envVars:
+      - key: AXIOM_DATASET_URL
+        value: https://api.axiom.co/v1/datasets/mui-mcp/ingest
+      - key: AXIOM_TOKEN
+        sync: false
+        previewValue: ''

but it never builds in https:// dashboard .render.com/blueprints. It’s as if buildFilter was taking over.

2

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.