add-option-to-continue-on-script-error

Author: luisggc

.github/workflows/dev-pytest.yml

@@ -30,7 +30,7 @@ jobs:
       SNOWFLAKE_ACCOUNT: ${{ secrets.SCHEMACHANGE_SNOWFLAKE_ACCOUNT }}
       SNOWFLAKE_DATABASE: SCHEMACHANGE_DEMO
       SNOWFLAKE_WAREHOUSE: SCHEMACHANGE_DEMO_WH
-      SNOWFLAKE_ROLE: SCHEMACHANGE_DEMO-DEPLOY
+      SNOWFLAKE_ROLE: SCHEMACHANGE_DEMO-ADMIN
       MY_TARGET_SCHEMA: ${{ matrix.scenario-name }}_${{ github.run_number }}_${{ strategy.job-index }}
       SCENARIO_NAME: ${{ matrix.scenario-name }}
     steps:

.github/workflows/master-pytest.yml

@@ -31,7 +31,7 @@ jobs:
     env:
       SNOWFLAKE_ACCOUNT: ${{ secrets.SCHEMACHANGE_SNOWFLAKE_ACCOUNT }}
       SNOWFLAKE_USER: ${{ secrets.SCHEMACHANGE_SNOWFLAKE_USER }}
-      SNOWFLAKE_ROLE: SCHEMACHANGE_DEMO-DEPLOY
+      SNOWFLAKE_ROLE: SCHEMACHANGE_DEMO-ADMIN
       SNOWFLAKE_WAREHOUSE: SCHEMACHANGE_DEMO_WH
       SNOWFLAKE_DATABASE: SCHEMACHANGE_DEMO
       MY_TARGET_SCHEMA: ${{ matrix.scenario-name }}_${{ github.run_number }}_${{ strategy.job-index }}

CHANGELOG.md

@@ -3,11 +3,27 @@ All notable changes to this project will be documented in this file.
 
 *The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).*
 
-## [4.1.0] - 2025-03-18
+
+## [4.2.0] - 2025-08-06
 ### Added
-- Optional flags to continue deploying remaining scripts after an error, recording full error messages in the change history table and listing failed scripts at completion.
+- Optional flags to continue deploying remaining scripts after an error, recording full error messages in the change history table and listing failed scripts at completion. (#339 by @luisggc)
+- Automatically add missing `ERROR_MESSAGE` column to the change history table to capture full script errors (#339 by @luisggc)
+
+
+## [4.1.0] - 2025-08-05
+### Added
+- Added flag `--error-on-ignored-versioned-migration` to throw an error when versioned migrations are ignored due to being out of order (#287 by @zanebclark)
+- Added `py.typed` marker file for better MyPy type checking support (#332 by @fozcodes)
+
+### Changed
+- Updated Flyway documentation links to current Red Gate community documentation (#333 by @sfc-gh-adamle)
+
 ### Fixed
-- Automatically add missing `ERROR_MESSAGE` column to the change history table to capture full script errors
+- Fixed secret redaction functionality to properly handle configuration secrets (#312 by @zanebclark)
+
+### Deprecated
+- Deprecated the `--verbose` flag in favor of structured logging (#288 by @zanebclark)
+
 
 ## [4.0.1] - 2025-02-17
 ### Changed

README.md

@@ -186,6 +186,10 @@ JSON object formatted as a string.
 schemachange will replace any variable placeholders before running your change script code and will throw an error if it
 finds any variable placeholders that haven't been replaced.
 
+If a script contains jinja-style syntax that should not be processed by schemachange, add the comment
+`-- schemachange-no-jinja` anywhere in the file. When this marker is present, schemachange will skip jinja rendering for
+that script and execute it as-is.
+
 #### Secrets filtering
 
 While many CI/CD tools already have the capability to filter secrets, it is best that any tool also does not output
@@ -226,6 +230,10 @@ These files can be stored in the root-folder but schemachange also provides a se
 folder `--modules-folder`. This allows common logic to be stored outside of the main changes scripts.
 The [demo/citibike_demo_jinja](demo/citibike_demo_jinja) has a simple example that demonstrates this.
 
+schemachange uses Jinja's [`PrefixLoader`](https://jinja.palletsprojects.com/en/stable/api/#jinja2.PrefixLoader), so
+regardless of the `--modules-folder` that's used, the file paths (such as those passed to [`include`](https://jinja.palletsprojects.com/en/stable/templates/#include))
+should be prefixed with `modules/`.
+
 The Jinja auto-escaping feature is disabled in schemachange, this feature in Jinja is currently designed for where the
 output language is HTML/XML. So if you are using schemachange with untrusted inputs you will need to handle this within
 your change scripts.

demo/basics_demo/1_setup/A__setup.sql

@@ -1,9 +1,7 @@
 SET TARGET_SCHEMA_NAME = '{{ schema_name }}';
 SET TARGET_DB_NAME = '{{ database_name }}'; -- Name of database that will have the SCHEMACHANGE Schema for change tracking.
 -- Dependent Variables; Change the naming pattern if you want but not necessary
-SET ADMIN_ROLE = $TARGET_DB_NAME || '_ADMIN'; -- This role will own the database and schemas.
--- Including hyphen in the role to test for hyphenated role support
-SET DEPLOY_ROLE = '"' || $TARGET_DB_NAME || '-DEPLOY"'; -- This role will be granted privileges to create objects in any schema in the database
+SET ADMIN_ROLE = '"' || $TARGET_DB_NAME || '-ADMIN"'; -- This role will be granted privileges to create objects in any schema in the database
 SET WAREHOUSE_NAME = $TARGET_DB_NAME || '_WH';
 SET SCHEMACHANGE_NAMESPACE = $TARGET_DB_NAME || '.' || $TARGET_SCHEMA_NAME;
 SET SC_M = 'SC_M_' || $TARGET_SCHEMA_NAME;
@@ -28,10 +26,7 @@ GRANT DATABASE ROLE IDENTIFIER($SC_M) TO DATABASE ROLE IDENTIFIER($SC_R);
 GRANT DATABASE ROLE IDENTIFIER($SC_R) TO DATABASE ROLE IDENTIFIER($SC_W);
 GRANT DATABASE ROLE IDENTIFIER($SC_W) TO DATABASE ROLE IDENTIFIER($SC_C);
 
-CREATE SCHEMA IF NOT EXISTS IDENTIFIER($TARGET_SCHEMA_NAME) WITH MANAGED ACCESS;
--- USE SCHEMA INFORMATION_SCHEMA;
--- DROP SCHEMA IF EXISTS PUBLIC;
-GRANT OWNERSHIP ON SCHEMA IDENTIFIER($TARGET_SCHEMA_NAME) TO ROLE IDENTIFIER($DEPLOY_ROLE) REVOKE CURRENT GRANTS;
+CREATE TRANSIENT SCHEMA IF NOT EXISTS IDENTIFIER($TARGET_SCHEMA_NAME) WITH MANAGED ACCESS;
 
 USE SCHEMA IDENTIFIER($SCHEMACHANGE_NAMESPACE);
 -- SCHEMA

demo/basics_demo/3_teardown/A__teardown.sql

@@ -1,9 +1,7 @@
 SET TARGET_SCHEMA_NAME = '{{ schema_name }}';
 SET TARGET_DB_NAME = '{{ database_name }}'; -- Name of database that will have the SCHEMACHANGE Schema for change tracking.
 -- Dependent Variables; Change the naming pattern if you want but not necessary
-SET ADMIN_ROLE = $TARGET_DB_NAME || '_ADMIN'; -- This role will own the database and schemas.
--- Including hyphen in the role to test for hyphenated role support
-SET DEPLOY_ROLE = '"' || $TARGET_DB_NAME || '-DEPLOY"'; -- This role will be granted privileges to create objects in any schema in the database
+SET ADMIN_ROLE = '"' || $TARGET_DB_NAME || '-ADMIN"'; -- This role will be granted privileges to create objects in any schema in the database
 SET WAREHOUSE_NAME = $TARGET_DB_NAME || '_WH';
 SET SCHEMACHANGE_NAMESPACE = $TARGET_DB_NAME || '.' || $TARGET_SCHEMA_NAME;
 SET SC_M = 'SC_M_' || $TARGET_SCHEMA_NAME;

demo/citibike_demo/1_setup/A__setup.sql

@@ -1,9 +1,7 @@
 SET TARGET_SCHEMA_NAME = '{{ schema_name }}';
 SET TARGET_DB_NAME = '{{ database_name }}'; -- Name of database that will have the SCHEMACHANGE Schema for change tracking.
 -- Dependent Variables; Change the naming pattern if you want but not necessary
-SET ADMIN_ROLE = $TARGET_DB_NAME || '_ADMIN'; -- This role will own the database and schemas.
--- Including hyphen in the role to test for hyphenated role support
-SET DEPLOY_ROLE = '"' || $TARGET_DB_NAME || '-DEPLOY"'; -- This role will be granted privileges to create objects in any schema in the database
+SET ADMIN_ROLE = '"' || $TARGET_DB_NAME || '-ADMIN"'; -- This role will be granted privileges to create objects in any schema in the database
 SET WAREHOUSE_NAME = $TARGET_DB_NAME || '_WH';
 SET SCHEMACHANGE_NAMESPACE = $TARGET_DB_NAME || '.' || $TARGET_SCHEMA_NAME;
 SET SC_M = 'SC_M_' || $TARGET_SCHEMA_NAME;
@@ -28,10 +26,7 @@ GRANT DATABASE ROLE IDENTIFIER($SC_M) TO DATABASE ROLE IDENTIFIER($SC_R);
 GRANT DATABASE ROLE IDENTIFIER($SC_R) TO DATABASE ROLE IDENTIFIER($SC_W);
 GRANT DATABASE ROLE IDENTIFIER($SC_W) TO DATABASE ROLE IDENTIFIER($SC_C);
 
-CREATE SCHEMA IF NOT EXISTS IDENTIFIER($TARGET_SCHEMA_NAME) WITH MANAGED ACCESS;
--- USE SCHEMA INFORMATION_SCHEMA;
--- DROP SCHEMA IF EXISTS PUBLIC;
-GRANT OWNERSHIP ON SCHEMA IDENTIFIER($TARGET_SCHEMA_NAME) TO ROLE IDENTIFIER($DEPLOY_ROLE) REVOKE CURRENT GRANTS;
+CREATE TRANSIENT SCHEMA IF NOT EXISTS IDENTIFIER($TARGET_SCHEMA_NAME) WITH MANAGED ACCESS;
 
 USE SCHEMA IDENTIFIER($SCHEMACHANGE_NAMESPACE);
 -- SCHEMA

demo/citibike_demo/3_teardown/A__teardown.sql

@@ -1,9 +1,7 @@
 SET TARGET_SCHEMA_NAME = '{{ schema_name }}';
 SET TARGET_DB_NAME = '{{ database_name }}'; -- Name of database that will have the SCHEMACHANGE Schema for change tracking.
 -- Dependent Variables; Change the naming pattern if you want but not necessary
-SET ADMIN_ROLE = $TARGET_DB_NAME || '_ADMIN'; -- This role will own the database and schemas.
--- Including hyphen in the role to test for hyphenated role support
-SET DEPLOY_ROLE = '"' || $TARGET_DB_NAME || '-DEPLOY"'; -- This role will be granted privileges to create objects in any schema in the database
+SET ADMIN_ROLE = '"' || $TARGET_DB_NAME || '-ADMIN"'; -- This role will be granted privileges to create objects in any schema in the database
 SET WAREHOUSE_NAME = $TARGET_DB_NAME || '_WH';
 SET SCHEMACHANGE_NAMESPACE = $TARGET_DB_NAME || '.' || $TARGET_SCHEMA_NAME;
 SET SC_M = 'SC_M_' || $TARGET_SCHEMA_NAME;

demo/citibike_demo_jinja/1_setup/A__setup.sql

@@ -1,9 +1,7 @@
 SET TARGET_SCHEMA_NAME = '{{ schema_name }}';
 SET TARGET_DB_NAME = '{{ database_name }}'; -- Name of database that will have the SCHEMACHANGE Schema for change tracking.
 -- Dependent Variables; Change the naming pattern if you want but not necessary
-SET ADMIN_ROLE = $TARGET_DB_NAME || '_ADMIN'; -- This role will own the database and schemas.
--- Including hyphen in the role to test for hyphenated role support
-SET DEPLOY_ROLE = '"' || $TARGET_DB_NAME || '-DEPLOY"'; -- This role will be granted privileges to create objects in any schema in the database
+SET ADMIN_ROLE = '"' || $TARGET_DB_NAME || '-ADMIN"'; -- This role will be granted privileges to create objects in any schema in the database
 SET WAREHOUSE_NAME = $TARGET_DB_NAME || '_WH';
 SET SCHEMACHANGE_NAMESPACE = $TARGET_DB_NAME || '.' || $TARGET_SCHEMA_NAME;
 SET SC_M = 'SC_M_' || $TARGET_SCHEMA_NAME;
@@ -28,10 +26,7 @@ GRANT DATABASE ROLE IDENTIFIER($SC_M) TO DATABASE ROLE IDENTIFIER($SC_R);
 GRANT DATABASE ROLE IDENTIFIER($SC_R) TO DATABASE ROLE IDENTIFIER($SC_W);
 GRANT DATABASE ROLE IDENTIFIER($SC_W) TO DATABASE ROLE IDENTIFIER($SC_C);
 
-CREATE SCHEMA IF NOT EXISTS IDENTIFIER($TARGET_SCHEMA_NAME) WITH MANAGED ACCESS;
--- USE SCHEMA INFORMATION_SCHEMA;
--- DROP SCHEMA IF EXISTS PUBLIC;
-GRANT OWNERSHIP ON SCHEMA IDENTIFIER($TARGET_SCHEMA_NAME) TO ROLE IDENTIFIER($DEPLOY_ROLE) REVOKE CURRENT GRANTS;
+CREATE TRANSIENT SCHEMA IF NOT EXISTS IDENTIFIER($TARGET_SCHEMA_NAME) WITH MANAGED ACCESS;
 
 USE SCHEMA IDENTIFIER($SCHEMACHANGE_NAMESPACE);
 -- SCHEMA

demo/citibike_demo_jinja/3_teardown/A__teardown.sql

@@ -1,9 +1,7 @@
 SET TARGET_SCHEMA_NAME = '{{ schema_name }}';
 SET TARGET_DB_NAME = '{{ database_name }}'; -- Name of database that will have the SCHEMACHANGE Schema for change tracking.
 -- Dependent Variables; Change the naming pattern if you want but not necessary
-SET ADMIN_ROLE = $TARGET_DB_NAME || '_ADMIN'; -- This role will own the database and schemas.
--- Including hyphen in the role to test for hyphenated role support
-SET DEPLOY_ROLE = '"' || $TARGET_DB_NAME || '-DEPLOY"'; -- This role will be granted privileges to create objects in any schema in the database
+SET ADMIN_ROLE = '"' || $TARGET_DB_NAME || '-ADMIN"'; -- This role will be granted privileges to create objects in any schema in the database
 SET WAREHOUSE_NAME = $TARGET_DB_NAME || '_WH';
 SET SCHEMACHANGE_NAMESPACE = $TARGET_DB_NAME || '.' || $TARGET_SCHEMA_NAME;
 SET SC_M = 'SC_M_' || $TARGET_SCHEMA_NAME;